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.
Comments
So weird
Is it the same if you have a midi channel in selected in ED? (In your screenshot you have ED set for Omni in)
The only other difference I noticed in our set up is in Modstep I have ED selected in the settings page as a midi source (in the sources boxes)....that may be the thing, ima try your way. I usually don't touch those boxes and leave them as whatever modstep defaults to.
I'm not sending midi from ed to modstep so I turned them off, just to prevent any possible issues.
Yes it is the same if I select a midi channel, it works as expected, have to send from modstep on whichever channel is selected in ed.
Ok, I just got notified of new update for ed, released on 18 Dec....installed it and now I see the behaviour that @monzo is describing, seems that update has changed something.
Nope, I was wrong working again now after restarting both apps, the control movement I was seeing was due to automation recorded in ed
Yep, de-selected ED as a source in Modstep and set Modstep as a source in ED, works just fine.
Here's one for you: deselect ED altogether in the midi boxes in Modstep (not a source or destination of any type), and set "no port/IAA midi" for note and clock in ED. This also works nicely... I think that midi routing as such is actually taken care of by IAA altogether, though the other routings seem to work as well.
Yes..for sure when loaded as an IAA it should be using IAA for midi and not anything else.
They are working not so great. You can not Save your own presets and They not Save the state in project. So you are allowed to use only factory presets
I just tried it with latest version of ED and I'm getting same behavior as MonzoPro. Are you using latest version of ED, @Littlewoodg?
Just had a thought about something I should let you in on...when I am using IAA's that allow it i send midi to them via their virtual ports instead of IAA....this means if/when I want to host it in AUM or Cubasis the midi routing in Modstep is already set up. And I can switch host back and forth quite easily.....do the same with AUv3 if they allow it.
I am indeed, in fact I deleted and redownloaded the app, just to be sure I wasn't testing with the beta. My set up is as shown in the two screen shots to @AndyPlankton: using IAA, using C1-F-1 for note data, chromatic scale, Air 2, iOS 10.2...its running in the bg as I write this. The switch in ED for "same controller for all instruments" can be on or off from what I'm testing, no difference.
One thing to note, the dials seem to jump as the sequence plays because the instrument displayed in ED as a sequence plays changes with the note triggered in Modstep. In other words when C1 is hit by Modsteps sequencer, ED displays the C1 dial settings instantly then changes instantly when E1 is triggered and shows the E1 instruments settings and back and forth...
EDIT: weirdly now the display isn't jumping between drums, which is better for tweaking automations....
Yes. After I restarted the apps and checked the midi routing it all worked fine again, not sure what happened with the update, perhaps it reset some midi routing, I wasn't paying enough attention to remember if I had to change anything back to what the screenshots show.
One thought, is ed remembering some sort of midi learn ? It is a clean install for me with little or no messing, just the midi routing for modstep.
Gremlins - fresh reinstall mysteriously sorts out so many things.
Forgot Link enabled. Must be disabled ,to see IAA panel. Thanks
The issue must be ED on my end because I can't get C1 to trigger a sample when I load ED as IAA in AUM.
Does it fix the ModStep triggering issue?
Fresh reinstall made ED display stop flipping between drums as they triggered, ED display went back to staying on selected drum so I could program automation on the fly...the actual triggering of notes by Modstep was already working. Mind you this was a fresh reinstall of ED. You may want to try fresh reinstall of Modstep, it may be retaining cc programming somehow.
@lukesleepwalker - in my tests and the screenshots I'm using ED as IAA in Modstep directly, no AUM involved.
That's not, good, I'll wait until that's fixed then.
I just got two samples triggering right around C2. The rest still don't play. This is why I give up on Modstep. Too much fiddling, not enough music making.
Sorry, state saving works
I think it's Elastic Drums.
I think so too and not fair to blame Modstep therefore. But it is often the case that I run into this sort of thing when working with Modstep at the center of a workflow.
I find anything involving midi on iOS like this.
Yes, here's hoping AB3 helps!