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.
Audiobus and Apollo remote
![[Deleted User]](https://secure.gravatar.com/avatar/8247d768a08e747278700d7476462017/?default=https%3A%2F%2Fvanillicon.com%2Fd39064a14c34cb4f62e49e97e919757e_200.png&rating=g&size=200)
@SecretBaseDesign and @Sebastian
I would like to play with soundprism electro to a synth in auria and had a bluetooth cnctn going with apollo from iphone to ipad.
Sidenote: I have two iphones, older and more recent, weirdly enough only trying to connect via apollo, soundprism electro and a synth of your preference left me wondering about the priorities of phones in connecting each other. Is it somehow restricted as to the order of initialisation?
Congrats on the release, party 
Thank you
(;
Comments
Hi -- SoundPrism Pro works fine with Apollo MIDI over Bluetooth -- I have never had any problems with it. I don't have Electro, though. To my knowledge, there should not be any interference between Apollo, Apple's MIDI over Bluetooth, or the Audiobus Remote iBeacon connections. Everything should work as expected (let me know if it doesn't!).
If you're talking about Apollo Remote Recorder and Apollo Sound Injector -- both of those had been running older Audiobus libraries. I updated both using the latest AB libraries (2.2, which came out yesterday), and have submitted them to Apple -- new versions of these should be available some time next week, assuming Apple doesn't gripe.
What doesn't work is: I can't connect from one iphone(a) to another(b) using sp and x, it's like random, either one or the other?
Ok, lets take apollo and thumbjam, on iphone, to midi out (with midibridge) to ipad: firo(Input) and auria(output) in audiobus.
On apollo it's a for ipad, b for iphone.
The sidenote explained:
Between two iphones:
On one iphone, the audiobus chain, thumbjam the input. No matter what the output. Audioshare for example.
On the other, ab remote.
What's happening is,
if you by chance happen to change your mind, with audiobus, you have to start the apps anew (either or on both devices) to reestablish a connection. (Error message)
Too much for me to explain, sorry. Greetings (:
You rule.
Oooh.... Ok, there may be something going on here. Audiobus just started using iBeacon, in order to connect to Audiobus Remote, which is a BTLE session, so that might actually be doing something. It could very well make a difference which endpoint you choose for Apollo (one end is a host, the other end a peripheral -- and that impacts a bit on how the code works, and how it interacts with iOS).
I'll look into this, and see if I can see something going on. Apple has been hacking their Bluetooth code with pretty much every iOS and OS X update; for the most part, it's been stable, but I have seen some glitches (Yosemite had a lot of trouble at the start).
Dang. This could be a headache.
(Semi-related note -- Audiobus Remote only supports iOS 8.3 and newer? @Sebastian -- any reason for this? iBeacon was added to iOS 7, if I recall correctly).