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
Maybe SonoBus. I never tried it for that, but it seems like it could work.
I just installed the beta and tried recording some GarageBand live loops into Loopy Pro, and since I was a glutton for punishment, did it from my iPhone. Had to reboot after install, configure GarageBand to run in the background, and use the 127.0.0.1 loopback address. The external IP shown in the Transmitter didn’t work. And then as you said, mute the monitoring in Loopy Pro. And then it just worked!
Hi, this Is very interesting, we are waiting for official release!
You can use Neon as an Effects insert to capture a GB instrument to a file.
Using Wireless Audio as an AUM transmitter, and a Loopy Pro Receiver with loopback worked first time for me. Very simple. Great way to capture IAA content into Loopy Pro.
I've tried that -- but ran into some weirdness. It appears that some DAWs will silence any track with a MIDI instrument at the head, if the DAW isn't in "play" mode, and there's no MIDI coming in. I think this is a CPU-saving optimization; why process audio from a track you know should be silent? I'll keep poking to see if I can find a way around it, but so far, no luck.
Very cool! Host to host audio without IAA. Perhaps multiple streams would be possible when running on the same device? Maybe use different network ports for each.
Also @SecretBaseDesign says it won't work if the devices are running different sample rates, but that should be solvable with sample rate conversion?
The recording app was my "Apollo Remote Recorder" -- which is the foundation of the new app. It was set up to allow you to record by tapping a button on a web page (that's the web page you're seeing at :8675), and then when the recording was done, it would automatically upload to your Mac, and you could drag it into Logic, or whatever. The audio was streamed so that you could monitor, but the recording was done on iOS -- so no glitches or drop-outs. It was an IAA host, but with all the hassle of configuring things with IAA, I don't know that anyone other than me ever really used it.
I killed off Apollo Remote Recorder, and moved the streaming part into Sidecar -- but I don't know that anyone used the streaming part there either. I've still got "Apollo Sound Injector" available for the Mac -- it will connect to the Transmit AUv3. There's Bonjour support, so the Mac can find the transmitter without configuration. For reasons I don't understand right now, the Receiver does not get access to Bonjour, so you have to type the IP address (and we've got the grief we're going through now with getting the network working). On an iOS-to-Mac connection, you're better off going with the wired connection that's been built into recent versions of MacOS, so Sound Injector is pretty much dead technology.
With AUv3, things are a LOT easier than with IAA. I'll add in auto-connect features to both, and as long as the IP address of the transmitter doesn't change, you'll only need to set it once. With less pain-in-the-butt factor, folks may actually use it.
Yup -- I may add that in; focusing on single stream right now, to see if there's an audience for it. If the connections are all within the same device, it should be easy to have many high-speed low-latency connections.
The sample rate conversion adds a little bit of latency, some CPU overhead, and a bit of audio quality degradation. I might add this in the future, so that people don't have to think about it.
Did you enable both Incoming and Outgoing Connections in the App Sandbox section of Signing & Capabilities?
@SecretBaseDesign
Some time in the past I've implemented an iOS component for controlling external lights with audio. To discover my Hue lights bridge, I've enabled Bonjour in my info.plist as follows:
That wasn't enough to make it work as at some point for security reasons Apple started requiring developers to ask for permission to use Multicast Networking in their apps, I think that is to prevent apps from spying on local networks.
I've asked for permission on 20/11/2020 and was notified on 11/12/2020 via email that I had been approved.
After that it worked well.
I've got IAA, Multipath, and Access WiFi Information in the entitlements. Is there another one to add (custom network protocol, maybe? Network extension?).
@SecretBaseDesign : +1 for support of multiple streams particularly on same device
+Gus
This is prolly a dumb question but can you create a virtual wireless network on iOS? I’m often away from my wifi router. Just thinking that i can use my phone as a hot spot for my iPad.
I think I did this with my iphone for Ableton Link once... (?)
On an iOS-to-Mac connection, you're better off going with the wired connection that's been built into recent versions of MacOS, so Sound Injector is pretty much dead technology.
Except that iDAM is only one way for audio (iOS to Mac). Also, you can't use iDAM and an audio interface on iOS at the same time. Transmit and Receive plugins for MacOS would be useful.
(Personally I find it better just to export audio and airdrop between Mac and iOS, but many people look for ways to do this kind of streaming.)
I like monitoring iPad audio in Tonal Balance Control on desktop so it would be handy for that. (But I don't have a mack and this is unlikely to get a vst I imagine)
I've used something similar to this when traveling. It's tiny weighs almost nothing: https://smile.amazon.com/microuter-N300-Pre-Installed-Repeater-Extender-Ethernet/dp/B07ZQ4VJM7/.
The actual model I have doesn't appear to be available any more, but this seems similar.
Making some headway. It looks like I can get Bonjour working for the plug-in, but it's going to require some manual crypto signing of stuff. Apple has a page on this, and there are two ways to do it (both really long, annoying, and error prone). I'm guessing not many developers do this, so they're not putting much effort into making it easy.
Supporting multiple channels should be easy; I'll probably have a new beta in a couple of days, and that'll let everyone route all sorts of stuff as long as it stays within a single device. Between devices, across the radio waves -- additional traffic may not flow as smoothly.
After I get things sorted on iOS, I'll probably make Mac AUv3 versions as well. Shouldn't be too hard to port, and while I really think wired connections to the Mac are better, folks can do wireless too, I suppose.
@Wim -- are you still having trouble with inter-device connections? If so, can you point Safari (on the same device as the Transmit plug-in) to 127.0.0.1:8675, and let me know what the web server says? The current build should report all the network interfaces, and I'm guessing that Transmit is showing the wrong IP address (and an alternate one should work).
Except that wired (iDAM) can only go iOS to Mac, not the other direction, and wired isn't an option if you want to use an audio interface on the iOS device.
Inter device connections are working fine for me so far. I'll try a little harder to break things today.
I'm reasonably sure you're showing the right IP address. As I mentioned before, the IP addresses shown always match what I see in my router.
I'm off to buy a 2nd USB ethernet adapter to see if this will work over ethernet. I see no reason why it wouldn't, and that would be awesome. I would never trust to wifi in a live situation.
I still have trouble connecting from my ipad, even when the transmitter and the receiver are on the same device
@cuscolima in the Receive app, can you try 127.0.0.1?
This is the "local machine" IP address, and should get you through. Hopefully, I'll get this figured out, so that it just works for everyone. There's likely some sort of security apparatus popping up in iOS, causing this to not go so smoothly....
@cuscolima - are you sure you have the latest beta version? Did you get the popup asking for network permissions on both devices? Have you tried rebooting the devices? Does "WirelessAudio" show up in the under iOS Settings > Privacy > Local Network, and is the toggle enabled, on both devices?
Local Network permissions seem to be required even if on the local device.
Getting the web page doesn't validate that Local Network permission is granted - because the client is Safari, which of course has them.
This is great. So easy to get set up and going.
Earlier I reported a painless setup sending from AUM to Loopy Pro on the same device using the loopback address.
I’m trying a similar setup to send from GarageBand to Loopy Pro, with the Transmit AU inserted as an effect on a Drummer. The audio gets to Loopy Pro, but it is choppy. I’m not sure if this might be a buffer mismatch.
Any suggestions?
Humm. I didn't have any problem with choppy audio in that setup. But it was on an empty project with no other apps or FX running.
Possibly a sample rate mismatch -- there's no conversion in the current app, so one side may be getting the wrong number of samples per second. I don't think GB has a way to fiddle with the sample rate, but Loopy Pro does. I'd suggest testing LP with either 44.1 or 48k, to see if that fixes it.
If the audio is going over WiFi -- could be network traffic. Try bumping the buffering in the Receiver up to 5, to see if that lessens the problem.
It works but of course only if receiver and transmitter are on the same device.
Yes, no, yes, yes
FWIW, currently, Loopy Pro works best at the native hardware sample rate. On a lot of devices capable of 44.1k (like my iPad 6), the hardware is really set up for 48k and so it may sound choppy at 44.1k but has no problems at 48k.