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.
AUM + Modstep
I'm thinking about trying out a live setup when I get home of AUM + Modstep + iSpark + IAA synths + some AU instances of iSem. Pretty psyched just thinking about it.
How would you load the IAA instruments? Both as Generators in AUM and Instruments in Modstep?
How would you sequence the AU instances of iSem? Just midi tracks in Modstep? Anyone tried a setup like this yet?
Comments
I would reccomend to not scatter things around: use modstep as midi sequencer(and of course like a audio gen for its instruments, if you use them) and AUM as a mixer/app loader. BTW you won't be able to run IAA instruments in two separate instances(like one in AUM and one in modstep).
I loaded cyclop as a IAA in AUM and routed the midi from modstep to cyclop, effected by apefilter, all link, no issues, pretty cool setup!
I have yet to try with several IAA/midi channels, step by step
Ok I got to play with this for a while. Modstep has a certain built in frustration level, that usually has me giving up on it before I get any real music done. This time, I got iSpark + SampleTank + iMini + one channel of AU iSem going, but I couldn't figure out how to route more than one track of AU iSem midi from Modstep to AUM.
I don't see any way to specify a midi output in Modstep that directs the midi to different instances of iSem running in AUM. Is there a way to do this?
It should be done selecting the midi channel to which each iSem instance is listening to, but actually couldn't find em in AUM, it seems like it is always in Omni mode.
I was wondering this too.
You can send on different midi channels from modstep but I can't see how you can select different midi channel sources in AUM for different AUM channels?
It seems like you can't currently, any plans to add this @j_liljedahl ?
When I tried this the iSEM appeared with a "@ch4" on the end of it (as it was loaded in slot 4 in AUM). When I selected the AUM input on modstep ch4 played it. Didn't try more than one instance but maybe they will show up with different numbers??
Those aren't midi channels but AUM audio ones
it would be nice to be able to send to AUM on a specified channel and that would make it possible to address multiple au instrument instances
I'm both sorry and glad to read this. Modstep continues to confound me beyond plink+plunk. And it's hard for me to tell what's my doing and what's buggy.
Thank you
I agree.
If Modstep is involved, all bets off for me in finding it productive or the least bit enjoyable.
Hope it will change.
Either the programming or the information on how things just work at a basic 101 level of functionality.
I would have thought that each AU instance can be controlled by a different MIDI channel. Im going to confirm this now. Kind of essential I would have thought!
I've got ModStep working fine with multiple IAA's loaded into AUM but yes same thing with iSem as AU, no way of selecting which channel to receive on.
Back to the OP I am loading IAA's into AUM as a synth rack and sequencing from ModStep.
Using iMini and iM1 I still get the same issues I have always had with stuck notes and crackling audio, but with force closing from multitasking and the reload function in AUM it is quicker to resolve these when they happen.
It's not AUM that listens in omni, it's iSEM, and it seems to not have any option for selecting which channel it listens to.
I'll certainly consider adding a channel filter in AUM, since I guess that even if iSEM is fixed this will come up as a problem with other apps/AU's too.
Odd. In AUM iSem has no midi channel selection. BUT in multi track studio it does
Perhaps MTS has a channel filter like @j_liljedahl is thinking of adding ? Is the midi channel selection selected from within the iSEM interface ? Does it have the connection panel like you get when running standalone ?
Yes I think that's because MTS is assigning the AU to a specific midi channel, you can't do that from within the iSEM AU controls.
Where it says Ch1 at the top of the iSem box in the picture above there's a drop down menu 1 to 16.
What is the point of loading multiple instances of an AU into AUM if there is no way to sequence each instance? Am I missing something?
No you are not, there is no point if you cannot sequence them
CORRECTION, There is a point if you are not playing audio from them all at the same time. You can switch which one is playing using mute in AUM.
^^
@j_liljedahl
I think there may another issue here, I've not tried it as I only have iSem as an AU, but, If I load iSem as an AU and an.other AU how do I sequence each of those ? As the MIDI Inputs of the AU's are not exposed to Modstep, I have to send the MIDI from ModStep to AUM as a single destination. So the same issue as above does not just affect multiple instances of the same AU but more than 1 AU fullstop ?
Having the channel filter on each would help, but there would be a limit of 16 AU's total.
Yeah, this is actually a problem that slipped by. I'll certainly add channel selection (filter) for both AU and IAA in the next update! Sorry for the confusion, I wrongly believed it would be standard for AUs to provide this themselves.
For more than 16, I can add more AUM virtual endpoints!
Well it does make an easy way to layer sounds for playing.
Just as an additional point related to the midi matrix in AUM. The matrix seems to be device/app centric and doesnt take into account that some devices/apps sent midi on multiple channels. For example BeatStep Pro. It might be that the filter you are talking about would solve this but I just want to add my 5c
FWIW - some meanderings that may be helpful to others...
First I used MODSTEP to trigger Animoog which was loaded into a channel in AUM. I have a simple AUM preset with just one channel and an effects bus. I set MODSTEP to send to AUM (Port 1). Getting Animoog to hear MIDI from MODSTEP simply involved ticking 'AUM' Destination as a MIDI input in AUM channel 1.
Next, in this same AUM preset, I swapped out Animoog for isem (IAA version). isem wasn't hearing MIDI from MODSTEP at first so I went into AUM's MIDI matrix and connected 'AUM' destination with Arturia iSEM. So I think the MIDI signal chain here is MODSTEP==> AUM==> isem. Worked like a charm.
MODSTEP and AUM is a beautiful combination IMO.
Thank you Jonatan for such a beautiful, useful tool. IMO, in a very useful way, AUM brings order to ios music chaos.
+1
Yes that is iseful. I was having to use MidiFlow to connect ModStep but using the 'AUM Destination' it connects directly. Btw now Im upgraded to 9 I can use MidiFlow as a sidebar. How cool.
100% agree AUM is a stellar app
I use Midiflow to channel to each iSEM instance in AUM (had 4 running at once).
EDIT - Sorry @Richtowns , just repeated you there. Great minds eh?
So, how do you set this up?
https://forum.audiob.us/discussion/12383/channel-selection-in-aum-with-midiflow