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.
Is it me, or is it Auria?
Can someone explain why this happens: I open Audiobus, choose Auria as the destination, choose any input app (iGrand in my example), and instead of one track opening I have two new tracks created in Auria. This happens on new blank projects or existing ones. I’m hoping I have a setting wrong. Any help or advice would be much appreciated.
Comments
I couldn’t reproduce it. But then I tried adding a mono track first, followed by doing what you said, and it opened up two tracks. I think it’s taking the default from the last track you added. Try adding a stereo track (you can delete it right afterward), then see what happens when you repeat what you did.
Ask myself that question most days
Thanks, I tried it with no change. I always use stereo tracks whenever I can, no idea why. In my test example I opened a new project in Auria with zero tracks, then connected an app thru AB. No interface in this test, although it does the same thing on my iTrack dock. Never happens on any other DAW.
Beats me then. Thats the only way I can reproduce it.
Looks like a straightforward bug - best thing to do would be to report it on the Auria forum. In the meantime you can use IAA to record instead of AB.
Straightforward? It doesn’t happen to me. Does it to you? Unless it’s readily reproducible it’s not straightforward.
Yes I tested it before posting.
I’m not happy that it’s happening, but I’m glad I’m not the only case. I’ve already posted it on the Auria forum. Thanks you very much to @wim and @richardyot for digging in to it.
Does it also happen with Audiobus 2?
Yes it happens consistently for me with both Audiobus recipes.
It’s not happening in my case right now, but it used to happen almost consistently in previous versions of Auria/Audiobus...