Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Modstep Circuit Templates
Looking through the ModStep Manual, I can't find any info on a file format etc., to create a ModStep template to upload. Does anyone know if this is possible?
The factory Synth Template for the Circuit, for example, has this mapping:
Keyboard Octave in ModStep is mapped to CC13 with a Range of 0-127 (I think all the Circuit parameters are mapped as such w/in ModStep).
However, in Circuit documentation - Keyboard Octave should have a default value of CC 64 with +/- 4 Octaves up/down. I'm wondering if this is programmed in, or if the Octave Changes are occurring only when the Modstep CC value traverses CC's 60-68?
Generally, this leads me to ask - can templates be created outside ModStep with additional parameter values?
I would like, for example, to create a mapping for the Mod Matrix of Circuit, which uses NRPN Values - doesn't seem this is currently possible?
Given this doesn't seem likely possible w/in Modstep - could anyone provide pointer to use an external utility to create a viable mapping for the Mod Matrix of the Circuit to be used/value-adjusted in Modstep? I have tools like MidiFlow/TouchOSC/Lemur/MidiDesigner Pro/Sidecar - but I'd rather stay confined to Modstep, rather than using an external interface.
So - feature request would be User-Created/Uploaded Templates that can act on Values other than/in addition to CC's. Other features like one-to-many, many-to-one mappings would also be useful for bringing together unique workflows.
Comments
9 months on, wondering if you got this set up.
It's an interesting topic.
I found this post on reddit detailing a similar scenario with Midiflow as solution...
https://www.reddit.com/r/synthesizers/comments/5zezf1/mod_step_nrpn_korg_electribe/
Well I did write to the devs asking if us users could create templates like the stock ones - no dice there. But then the iOS Circuit app went into development - I was lucky to get to beta that and try to pester as many features as possible. So it's got IAA Midi - and was even an AuV3 in the beta. Unfortunately, Modstep's AB3 Midi didn't get ironed out until after Circuit MidiSynth was out of beta - and as well AuV3 format. I should add - it was an early beta state so the GUI rendering was wacky - but if enough sales come along it may get polished off and released (currently unlikely). The good news is the app still sends/receives Midi and I think it's even got IAA Midi in the background (though I can't confirm this). The automation and copy/paste features the app has for the Mod Matrix fill the gap I wrote about above, though I haven't actually had a chance to set up the app alongside Modstep/AB3 and see what fun to have.
Modstep is one of a small handful of apps that baffle, and keep my interest - a wellspring of creativity... 1 thing is broke, 1 thing I'm doing wrong, 1 thing I didn't know about (the secret handshake). Course, I also have to turn my back now and again to stability... but then, pure sunshine makes only a desert...
I've released tons of templates on the forum. Months before your post here:- https://forum.audiob.us/discussion/13332/modstep-midi-cc-templates-new-moog-model-15-template-every-single-knob
Even released tutorials as to how to make your own templates:- https://forum.audiob.us/discussion/17006/modstep-tutorial-template-editor-bonus-automation-tips
A google search would have given you these results. Regarding exporting I just use ifunbox to export the files using my desktop. It's not ideal but it works. Proper export is expected once the new engine is out to public.
Regarding stability modstep never crashes at all when used for midi only. Most of us hardcore users host everything in AUM. The combination of the two is still one of the best daw alternatives on IOS.
I don't have any of the apps you created templates for. Did you create those templates with an external editor? And did any of them involve NRPN mappings?
I asked the devs (noted in my above Q) to create templates "outside" of Modstep and with NRPN values. I know how to make a CC template the manual way, and the stock Circuit Modstep templates already contain mappings of Circuit's available CC's for the synths and drums.
Like the following (yours - but I'd make them in a text editor, rather than typing in-app, so you can just swap out values/descriptor)- but w/ NRPN, not just CC's. I didn't read the reddit link you provided, but I'm guessing they are using CC's in the same way, and with MF to trigger an NRPN value or something when that CC is sent, which isn't what I requested, and wouldn't cover much of the Mod Matrix values w/out overlapping.
{
"version": 1,
"mapping": {
"vcf0_freq_k": [34, 0],
"vcf0_range_k": [35, 0],
"vcf0_regen_k": [36, 0],
"vco0_semi_k": [41, 0],
"vco0_range_k": [42, 0],
"vco1_semi_k": [43, 0],
"vco1_range_k": [44, 0],
"vco2_semi_k": [47, 0],
"vco2_range_k": [48, 0],
"vco2_width_k": [49, 0],
@gonekrazy3000 you reminded me that I was working on this last June: https://www.facebook.com/modstepapp/posts/1738953979695121
I still think it would be nice to have external template creation available (and beyond CC's), for me this one is solved via the iOS MidiSynth. Thx for those links - I'd actually saved the Moog templates previously, but I only have ever paid over 19.99 for Auria, and only have 3-4 19.99 apps - so they continue on my "hold" list.
I think the model 15 was down to 10$ last sale.
I have a few more templates (Laplace, Mersenne, iPulsaret, Xynthasizr, Ripplemaker), and more that I might get around to uploading (Lorentz, Patterning, GlitchBreaks, Fieldscaper), as well as a bunch for which I only have the ModStep side, so I haven't bothered uploading (Holderness FX, Elastic Drums).
I don't. I've looked at the .mtt files and I can see the CCs and their assigned names, but there are a bunch of other numbers in there and I haven't spent the time trying to figure out what they are.
In addition to the CC naming assignments, a template also includes:
-CC assignments to XY pads and their range limits
-Pad assignments
-Chord assignments
-Overview text
It can be rather complex, so I don't think they would want to expose how the list is structured as it would be easy to mess up.
It would have been nice if this was XML or even just a simple list, but that's not the case. Maybe I'll take another look and see if I can figure out what those extra numbers are....
That said, I would love a simple way to input CC naming: Instead of having to add a CC number and then assign a name, it would be much quicker if the template editor opened a window with 128 fields like a spreadsheet. You would then just enter the name next the number you wanted. Much, much quicker to build out a new template. Empty fields wouldn’t show up in the palette.
And this would be much easier if they used the standard iOS keyboard instead of their custom one since in the custom one:
-Capital letters are not shown
-Two finger cursor moves are not supported (and their text boxes don't support dragging, copy/paste, etc)
-Bluetooth keyboards are not supported
Unfortunately ModStep doesn't do NRPN (or RPN). But as shown, MIDIFlow can do the conversion.
ModStep also lacks 14 bit controls expect for Pitchbend and the built-in Modulation Wheel (that is an important thing to understand if you make an assignment for CC33 and use the built-in ModWheel. I recommend creating a custom CC1 control and using that rather than use the ModWheel unless you really need 14bits).
Most frustrating to me is that ModStep doesn't do Aftertouch - you'll need something like MIDIFlow to change Aftertouch to a CC value.
While you can use MIDIFlow to adapt, it would be great if you could do this in ModStep directly.
Ideally you could create an "input template" that corresponds to your external controller hardware, then assign whatever synth controls you want to those controls. When you record, it records the converted CCs of the assigned parameter, not the actual control the hardware is putting out.
I would suggest asking the developers again. While they might not open this to external editing, a simple table view in the app should be relatively easy to implement.
Adding NRPNs and 14 bit controls might be a bigger ask however (but I'm hoping for channel pressure!)
Right - sometimes you can rename a parameter via a text editor, then just save again. I do this with the Amazing Noises apps (which have really complete properties for all those LFO's and changing colors of any the knobs).
the .mtt etc files are just .plist (property list) files, which are basically plain text preset (app state?) information. I agree usually no need for using them beyond saving etc.
Agree with all this - I check each update hoping I can use my keyboard. And on the other side, unless I'm mistaken, you can't copy/paste NRPN or SysEx data into MidiFlow - which makes those kinds of mappings grueling.
Yes, this would be great - pretty much what I requested was a 'template editor/creator'
I wish the area you draw in the automation was bigger, or maybe fluxpad as an Au for that type of automation drawing.