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.
Comments
@OscarSouth : did you make sure to load modstep first in your setup?
Yeah, I've been told to do this a bunch of times and also given this advice out myself.
Obviously Audiobus must be started first, so I'm loading that. After that, if I load modstep from the Audiobus preset, the audio won't route correctly. I discovered that if I load modstep from it's app icon and THEN go back into Audiobus, select the preset, load AUM and other apps (in this case I'm just using AUM, Thumbjam and Modstep) and activate AUM's preset, then I've got a chance of it linking up correctly.
I've got no idea how it managed to un-route itself this time, the previous times today were all on a crash, but there's been no obvious trigger event this time.
On the plus side, modstep1.1's workflow is fantastic! Definitely the most intuitive and 'musical' piano roll editor that I've ever worked with. In between battling this issue have been enjoying working on some interesting music.
If it's of any use, the connection with Audiobus Remote Switching functionality wasn't effected the last time. Only on crashes. The crashes all occurred on 'dropping' a preset onto whatever the designated drop area is.
Have been persevering and taking note of fine details of what's happening.
I've noticed that it's usually impossible to get it routed again after failing until I've carried out a full system power off/on.
It's also not consistent whether modstep 1 or 2 routing will break. Last 2 times it was the synth (modstep 1) and this present time, the sampler (modstep 2).
We fixed a small issue that could lead to exactly that problem (crash when dropping a preset on either Sampler or Synth) in the latest build, should be available as a beta in 1-2 days!
Still no closer to finding that unrouting issue though
I'm not having any trouble finding it AT ALL!
Thank you for giving your attention to this matter.
I'm going to PM you my email, please get in touch and get the info off me that you to track this thing down yourself.
I honestly hope in an idealistic way that it's something on my end because that means that this problem would be easily and quickly solvable for me, but considering the lengths I've gont to to try and remedy it, I'm doubtful. As of right now the synth and sampler (both of which are tools that I love and would rather use over any third party midi apps) are completely unusable to me. The timesink of rebooting my entire system 2-3 times an hour to use internal audio from modstep is obscene and unsustainable, obviously un-viable for performance situations.
It's a 'little' frustrating.. so let me help you however I can!
With no hint of any reasoning as to why or how, the previous method that was working 1 in 3 times (ish) to load modstep with correctly functioning audio doesn't seem to work any more.
I'm baffled and confused. I just can't think of any reason why the audio from this app wouldn't go directly through Audiobus's output and be handled normally, in the same way that any other app would.