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
Ah, right, thanks!
(edited: sorry, this post doesn't belong here...)
finally! this new update of audiobus sdk and sugarbytes' apps totally fix my problem using my RME audio interface.
i'm so happy. thanks guys for the well done work.
The most important thing IAA adds that Audiobus lacked is the potential for clock sync. Loopy clock sync works in BeatMaker2. Very cool!!!
@boone51 Here is the iOS8 AudioBus 2.1 compatible list :~}
http://audiob.us/ios8/
Ah, that's awesome. Thanks @philowerx
Just had a question pop onto my head.. @philowerx alluded to it earlier.
If you use Loopy as the host in Audiobus with the new SDK, and the input app also supports the new sdk (and IAA), what IS the clock sync method used by Loopy? I've been told to disable midi clock sync when using an app as IAA. Is that what we should do in Loopy in this case? Really hoping @Michael might weigh in on this one.
For real, though. Bump. I feel like this is a pretty important question. I have tried playing with it with abeat Machine and a "few other apps" and the sync isn't there. Seems like a BFD.
OK, sorry to hammer this thread, but just thought I'd add more of my findings on the topic. I was finally able to get Drum Machine to use midi clock sync when loaded in Loopy. Not sure what the problem was yesterday, but I couldn't get it to work. But the question is unchanged. What's the method of clock sync used in Loopy when used in conjunction with another IAA app that's been updated with the new SDK for AB? I was (and I doubt I'm alone) very much looking forward to the perfect sync IAA provides, but on the surface it doesn't look like that's the case.
The answer is: when connected in the input slot with Audiobus 2.1 (IAA under the hood), Loopy will currently sync to the output app's clock if it's provided via IAA's sync method. If Loopy's in the output slot, it'll provide clock to IAA inputs. However, as we haven't yet tackled the sync issue on iOS, none of that is guaranteed, as it depends entirely on what the other apps support. So, I'm afraid there's no simple answer just yet - it depends.
Thanks for the feedback @Michael. I'm still a little confused though. I get everything you're saying about IAA and both apps needing to be on 2.1. But...I would have thought that your implementation of the SDK would have "fixed" the clock mess via the incorporation of IAA. "it depends entirely on what the other apps support" ...seems like that's the whole point of the SDK, right? Implement the SDK and now we know what your app supports. No? I'm just very ignorant here, so excuse me. I'm VERY interested in the topic though, so thanks for humoring me a little.
You're partly right there - that's definitely the purpose of having an SDK to do this stuff, but our SDK doesn't handle sync yet, so we can't guarantee a consistent experience with syncing. It's that consistency which isn't fixed - yes, some apps do work fine, but it's inconsistent; there isn't a nice list of apps that are guaranteed to work nicely together with sync yet, so mileage will always vary. We consider that a real problem with the platform right now.
A month old..,but,one of the better lists
http://ipadmusiced.files.wordpress.com/2013/10/inter-app-audio-loran2014-07-16.pdf
Thanks @Michael. And thanks @commonstookie for that great link. I'm a little surprised that the SDK didn't incorporate the sync stuff given that issues visibility since day one of AudioBus 1, but I get that there's probably a lot of ground to cover. I appreciate the honest feedback about the current state of the state. Thanks again.