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 note input......?
Brand new to modstep, I've had it about twelve hours, most of which I've been asleep cuz I grabbed it last minute of the Cyber Monday price...
It's pretty fast to figure most the basics out if anyone is wondering, but I am stumped about something..
I put notes in the piano roll and created a simple sequence with sunrizer to get started....
My plan was to do that, then improvise with sunrizer using the modstep internal keyboard until I came up with something I liked, then to record in the midi data live once I figured out my melody...
The problem...
As I was improving, without the record button enabled, modstep recorded / added my improv to the piano roll...., Now it's there and I don't want it cuz it was just some free style warm up...
The question....
Can you jam on the keyboard inside modstep without it recording the midi data ???
Comments
Of course. Just don't arm the track (the "A" at the bottom of the channel). I usually have the reverse problem — I accidentally stumble on something that doesn't suck and then...damn!
One trick I learned early is that when you create a scene, long-press on it and extend it to 16 bars (the maximum). Gives you plenty of room to jam on. Then it's easy enough to delete specific bars, rearrange them and add more bars for further jamming.
@ExAsperis99 yoooo! Excellent! Wow I totally just missed that 😂 thank you for that 🙏
And ya haha now I'll have that same problem and wish I had arm enabled when I create the best sequence of my life 😂
I compiled a handful of modstep tutorials from Mr Haq Ataq himself here:
See full set here on YouTube
And how many times can I leave the "EDIT" button enabled only to find i've done something stupid!!!!!
Rad ima go thru these
Haha ya man I'm hoping to get in the habit of not doing that
Kinda funny to read that now. In the first days of Modstep I've suggested to the dev to do away with the edit button completely because there are several (imho better and faster) alternatives, but it was the way he thought it had to be and I somewhat accepted it - another example of different people favoring different workflows/different apps.
Is there an Undo command hidden somewhere?
I don't know how to tell you this....
https://media.giphy.com/media/3o6Zt0hNCfak3QCqsw/giphy.gif
Ooooo that smarts!
As a wise guitarist once said, “There is no undoing of the chords you play...just the learning to play from your heart...”
I've noticed that mod step isn't saving the state of my synths, for example I had Magellan going on a session, saved the preset and then saved the Modstep session, started a new Modstep session with Magellan, used a different patch, then went back to my original session and it just loaded up the current patch... That really blows 😐 so I guess you have to route everything thru AUM into Modstep to save states?? I was hoping to avoid this
The best approach I can recommend is to host ALL plugins in AUM**, and only use Modstep for sending midi to AUM. It’s very stable this way, and just inviting problems (IMO) to host apps inside Modstep.
Besides ... Modstep has no busses, no panning, no etc. And it’s easier to do things like swap out instruments and FX, and to route one pattern to multiple synths in AUM / AB3.
(** actually AudioBus for me by preference)
Yep...I do what @wim said. It allows for more flexible routing of Sends and fx as well...AUM is a workhorse for this type of workflow....
Good option.
Other options
Modstep saves all the AU3 format plugins for me fine internally.
Other stand-alones that take program changes. E.g. I use Virsyn AudioLayer that way just because I usually use the same couple sample sets. Had done some others that way where I wanted to keep something on one track and save cpu.
Ok, i see what your mean..
Create the clips in Modstep as usual... But the audio will be coming from AUM...or Ab3...
Then you can still launch clips and jam like normal.... My mind was lost for a second 😂😂😂😂
To much blantons tonight
Thanks guys
@echoopera @wim
I haven't tried it yet cuz it's hard to get the cc values of the synths, but if the synth is open in AUM, can I still record automation in Modstep and sent it along side the midi note information ?
So proud. The bird has definitely flown from his nest.
@Multicellular hmmm ima try it again, maybe it is just my iaa that didn't save, I was using Magellan... Its iaa but I did have an instance of kaspar au I'm Modstep and when I went to my project it was open to the init patch, but maybe I did something wonky, will test again
If Kaspar was the AU version, then check again. The preset would normally say default, but the settings of all the knobs should all be the same as they where when you saved the project. AU state saving preserves the parameter settings, but not the preset name.
Yeah - i am like @reasOne new with this one.
Thats a way i was tinkering along yesterday night. I am at work now, so no play atm.
Will i be able to use the modulation options inside modstep for e.g. in AUM attached plugins? i guess not, right?
The modulation options were a big thing why i initially wanted modstep ... but the "not savin parameters and LFO assigned automation inside auv3's" inside modstept just bugged me last night.
Short info available?
Kind regards.
Yes.
@wim
I guess its the same answer for me then? hoping
Sure you can. Automation is just midi cc values, and midi cc values can be assigned to control AUv3 parameters in AUM.
I don’t understand what you mean by that. AUv3’s save their state when the project is saved. It may not look that way if you’re just looking at the preset name, but the setting of every knob, etc should be as it was when you last saved the project, in every host.
Sorry, I don’t understand enough what you mean to respond.
That is what i hoped - gonna try tonight. Thanks!
I hosted an apeSoft filter (iDensity) yesterday inside modstep and modulated a parameter with the LFO (dry/wet value) option inside iDensity. Each time i reloaded the modstep project the LFO was gone and nothing modulated.
Do i have to save a plugin-preset every time for this to work? It seems that modstep is only storing the information which auv3 plugins belong to the project but not what settings are made inside the plugins.
I hope i am wrong.
We’re you using the IAA or the AUv3 version of iDensity? If AU and it didn’t save the state, then that’s a bug. I don’t have iDensity, so I can’t check. If IAA then that’s to be expected, and yes, you would need to save and reload a preset every time.
Also, did you explicitly save the project in Modstep?
Personally, I don’t rely on ModStep for hosting apps. It’s never been as reliable as AudioBus and AUM in that area for me. So there could be AUv3 state saving issues I’m not aware of.
Thanks man!! @wim
Good luck!
Auv3 - checked multiple times.
State did not save - also checked multiple times.
Sure thing. Saved and made several "Save As" as i could not believe it is not storing these presets.
Ok. Maybe i should rethink hosting options before i get to deep into it.
Will try the way with hosting in AUM and just using modstep for triggering.
Thanks @wim !
@MrBlaschke I was hoping to use Modstep similarly to how gadget is set up , looks like it'll take a little more effort, but at least it's possible with non gadget synths