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.

Kymatica AUM and Audiobus

I beg pardon as I'm very new to creating and performing using IOS apps. I am attempting to use Kymatica AUM and/or Audiobus to determine the best possible way to use my synth apps, as well as others, live. I've been able to have some success dabbling in both Audiobus and AUM but my issues are with having the ability for total recall. AUM pulls my saved presets but a) there doesn't appear to be a way to have the synth apps auto load - I'm having to load them each time, and b) my adjustments and settings for each app are't being recalled. As I understand it there is something called state saving and though that seems to be partially the case in audiobus, Audiobus doesn't seem to allow me the synth layering capabilities that AUM does - or at the very least, I'm too unaware to know how to make that happen. Any assistance is greatly appreciated.

Comments

  • Load apps with Audiobus for state saving (and Audiobus remote) and route the Audiobus outs into AUM channels for mixing. Done!

  • That's what I was kind of imagining from what I've read, but that means while performing live, you would have to be loading different things into Audiobus and AUM as well correct?

  • Oh never mind, I see now! Yes, that is easy! Whew. Took a while looking for documentation that wasn't very explanatory, so thank you forum and thank you Oscar!

  • No worries. I would recommend saving your AUM template then clearing it before saving all states in Audiobus. Then when loading apps, boot up AUM's template last after loading everything else

  • Perfect! Thanks for the tip!

  • Hey Oscar, any ideas as to why when I stack certain apps onto others in audiobus, such as say Vogel CMI, they show up in AUM under Audiobus Source, but don't show up in the MIDI Route area?

  • Not sure. Make sure you scroll all the way over though and also that those apps aren't hiding their own midi ports inside their internal settings. I actually set up midi in the various apps own individual ins/outs myself, because they automatically reconnect on losing connection that way.

  • Thank you. I'll look into that. The thing I believe is bothering me most of all is not being able to find answers to my questions through the manufacturers themselves or just by surfing the net unless I find individual users to ask. I need to be able to have one setup in Audiobus, have that associated with one setup in AUM and that be that for an evening. What's happening when I start by loading my saved preset in Audiobus is that when launching one app, it causes another to close. For example, this pretty much always happens using iGrand, if I launch it, it causes Propellerhead Thor and iTuttle to close. At the same time, if I go to re-launch those, iGrand closes. I'm not seeing any rhyme or reason to that. I just need a setup I can count on without things closing themselves. My other issues I've always had with Thor is that no matter what MIDI channel I assign for it, it ends up receiving on all MIDI channels quite often.

  • Keep persevering. When you get your setup working well, iOS is stable and a joy to work on. What other platform let's you build your own modular DAW to your exact personal requirements?

  • @buddyhinkley said:
    What's happening when I start by loading my saved preset in Audiobus is that when launching one app, it causes another to close. For example, this pretty much always happens using iGrand, if I launch it, it causes Propellerhead Thor and iTuttle to close. At the same time, if I go to re-launch those, iGrand closes. I'm not seeing any rhyme or reason to that. I just need a setup I can count on without things closing themselves. My other issues I've always had with Thor is that no matter what MIDI channel I assign for it, it ends up receiving on all MIDI channels quite often.

    I'm pretty sure that's due to your iPad running out of memory. iOS will shut down apps in the background if it runs out of resources. There is no controlling how that happens, when, and to what apps. I'm guessing iGrand takes up a lot of memory. Unfortunately, you're just running up against the limitations of the platform.

    You might want to try closing apps that you don't need at the time yourself so that you're in control of the situation, not iOS. Another option is to use more than one iOS device, and do the MIDI sequencing over network or Bluetooth MIDI from something like ModStep.

    You don't mention what device you're using, but there is a huge difference between the older and newer devices. My Air 2 is able to do more than I ever expected of the platform.

  • Ah I see. Wasn't thinking along those lines. Mine is an Air 1 and I've paid a lot of attention to physical storage space but not necessarily to the operating memory. I may just have to get a little creative. The only thing I don't understand is it can happen pretty early on in the Audiobus building process - example would be adding iGrand on one node, and then 3 nodes down the line, it goes down.

  • Also, be sure to clear out any background "ghost" apps that sometimes get left around due to iOS not always closing down IAA apps properly. I do this after every session. Close all apps, then hold down the power button until the power off slider shows, but don't slide it. Now hold down the Home button until you're returned to the main screen. It takes less than 30 seconds, and will save you many headaches.

  • Thanks so much! I'll be sure and try that!

  • @buddyhinkley said:
    Ah I see. Wasn't thinking along those lines. Mine is an Air 1 and I've paid a lot of attention to physical storage space but not necessarily to the operating memory. I may just have to get a little creative. The only thing I don't understand is it can happen pretty early on in the Audiobus building process - example would be adding iGrand on one node, and then 3 nodes down the line, it goes down.

    iGrand probably takes a lot of memory. Sample based instruments have to load a lot of audio files into memory at once in order to be able to play them back without glitches and latency. The cost of accuracy is many samples, thus lots of memory suck.

    If you can get away with a "good enough" piano solution that takes less memory, that may allow you to have more things open at once. Others may be able to provide recommendations.

  • It's interesting that I just did that for the first time, and thus far haven't had any issues when building a setup in Audiobus. Hmm. Maybe that was a larger deal than I thought.

  • But finding a piano app that's relatively small and has the ability to select MIDI channels, and is also compatible with Audiobus, seems a bit challenging.

  • For small, look at Apps with multiple instrument types. Like, say, a SoundFont player like Bismark. Serviceable piano patches.

Sign In or Register to comment.