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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

AUM and MIDI sequencers - any experts in the house?

So after seeing all the buzz about AUM I took advantage of the Easter sale and went for it. It's really great but I'm struggling a bit with the MIDI side of things. I have both ModStep and Genome but can't seem to get either of them to send notes to apps loaded into AUM. What's the best way to set this up? I'm just looking for an instrument per MIDI channel but getting kind of lost with all the possible out destinations. I also feel I might have rushed into Modstep as I'm not really into clip launching, but rather arranging (Cubasis style).

Many thanks in advance for any help!

Comments

  • In AUM's settings there's a MIDI router. Have you tried that?

  • Yeah I've looked at it and I can see how it works in theory but I just can't get it going. So say in something like Genome, I have all my patterns playing on their own tracks. Would I just set Genome's MIDI out destination to AUM (or Network Session or whatever) and then in AUM send that one source to every instrument and just make sure that they're set to receive only on a single channel? Or would I be better off using AUM as a mixer only, and manually setting the outputs of each MIDI track to each app? If/when I figure this out I might do a step by step or something because I'm totally scrambled right now haha.

  • Yeah I'm in the same boat. Best thing to do is put it on paper. Like four boxes. One box is AUM and the others your other midi apps. Now decide who sends and who receives. That will help you determine how to set the input and outputs. In my case I had AUM control she my drum machine starts and stops. So AUM is my master app, then Rock drum Machine my Slave app. So take it like that one step at a time. So I set up AUM to send midi clock to RDM. Set up RDM to receive Midi in the same midi port that AUM is sending out. Very important.
    Hope this helps a bit. I'm still learning too.

  • @chimp_spanner said:
    Would I just set Genome's MIDI out destination to AUM (or Network Session or whatever) and then in AUM send that one source to every instrument and just make sure that they're set to receive only on a single channel? Or would I be better off using AUM as a mixer only, and manually setting the outputs of each MIDI track to each app?

    I don't think there's a best here. Either way works, so long as it works!

    If you're comfortable doing Genome->synth app's virtual ports directly, go for it. If you save a preset in AUM or a state in AudioBus, you'll still be able to load them all at once when you go back to the project.

    If you go the via AUM route you can set filters on each IAA/AU instrument within AUM to sort out which channel goes to what. Point Genome at AUM's Virtual Input. Set up the instrument channels in AUM. Tap the little 3 line hamburger menu icon next to the app's icon. Select AUM's Virtual Port as the MIDI input. Below that, you'll see a channel filter—just set that to whatever you have that instrument's track set to in Genome.
    http://kymatica.com/aum/help.html#toc66

  • One thing about Aum's midi router. Sometimes an external midi source is only seen as coming from Aum destinations. You can select multiple inputs so maybe select Genome/ Modstep AND Aum destinations in the Midi router to be sure.

  • Watch out for double connections!
    If you configure A to send directly to B, and A also sends on its own virtual source port, and you then route that A port to B in AUMs matrix - you got two connections between the same things, often leading to all kinds of trouble.

  • Great advise. :)

    @j_liljedahl said:
    Watch out for double connections!
    If you configure A to send directly to B, and A also sends on its own virtual source port, and you then route that A port to B in AUMs matrix - you got two connections between the same things, often leading to all kinds of trouble.

  • I forgot about midiflow, gonna get that app.

  • I have been just sending midi from modstep direct to the IAAs in aum,

  • wish midi activity was apparent at each port. troubleshooting midi on iOS has always been a strain.

  • Wish I could just simply start recording in AUM by midi clock (e.g. with midi clock output from Noatikl or Fugue Machine).

Sign In or Register to comment.