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 midi routing with AUs (iSem) and midiSTEPs/Fugue Machine
Hi. So I think this is something that became possible in the latest Aum update but I've been researching and experimenting and I still don't know how to configure it. I'm trying to run multiple instances of iSem in Aum and have different midi data sent to each instance. The problem is when trying to have Fugue Machine or MidiSTEPs provide data for multiple instances of iSem, it doesn't seem like there is a way to separate the midi channels in Aum. I'm stuck which all the midi data from my sequencers going into each instance of Aum I route it to, instead of data from just one of the sequencers channels. Any ideas?
Comments
Once you have loaded isem instance in AUM, select the three horizontal bars that appear to the left of the iSem input, you can then select which channel you want it to use.
Do this by de-selecting those channels you do not wish to receive on.
I know about that. Unless I'm missing something, that doesn't work for this situation. It doesn't give you a channel option so iSem just plays the midi data from every channel of the sequencer.
When you are sending the midi from fugue are you able to send it on a particular channel, e.g channel 1 for playhead 1, channel 2 for playhead 2 etc ?
If so then you should be able to set 4 instances in AUM using the above method to make each instance only listen on 1 channel,
That is how the channel filtering in AUM is supposed to work, I don't have MidiSteps or fugue machine so i cannot test this for you unfortunately.
But when I load isem in AUM and I press the three horizontal lines I get option to turn of channels, they are just below the All Notes Off button. labelled Channel Filter ???
aaaaaahaaaaaa. thank you, you helped me figure it out. I hadn't installed the update yet! maybe I should delete this thread.
hehehe.......Doh! Glad you're sorted
And in each channel in AUM you can specify which range in the keyboard iSEM will receive notes. Pretty awesome!
Conceptually I understand this but having a hard time making it happen in real life. With Fugue Machine, iSem keeps wanting to play all the midi data even though I'm specifying a channel.
When y'all are using FM or MidiSTEPs, do you choose their midi out option or Aum as the destination? Does that matter?
I set both FM and Aum to Fugue Machine Midi Out. This is working for me with 4 au instances of ISem in Aum all on different midi channels. The midi filter option in Aum works by Deselecting all channels not desired in each instance.
Setting FM to 'Aum' And Aum to 'Aum Destination'
also works.
It definitely can matter, depending on how you have it set up. It's really easy, almost intuitive, to set up double MIDI connections (which doubles events) on iOS by pointing apps at each other more than once (even though it doesn't seem that way when looking at the config screens). @sebastian and fam are aiming to sort this mess out in AB3.
For now:
a. Tap the 'iSEM @ ChX' name on the right side of the grid
b. At the very bottom, below the 16 channels, tap "None" to turn everything off
c. Tap the channel number you want that instance to listen to
d. Rinse and repeat
You can also do the whole foreach part within the main AUM main screen by tapping the three bars next to each iSEM icon.
Alternative: Don't point FM/midiSTEPS at anything. Within AUM, replace "AUM Destination" in step 3 above with whichever app you're using. For whatever reason, I've found that pointing at apps at the destination app's virtual port to work more consistently so I generally do that but either should work. You just don't want to do both.
Great tutorial!