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
Are you talking about https://audiob.us/bugs?
I couldn't find it there yet.
And I noticed 2 other things while reading that page:
White on white doesn't work for the headlines, they're unreadable.
Also it looks like there are no known issues from iOS 9 onwards.
Another annoyance is that all iconnect midi ports are labelled as ICON when they are slot loaded...so unable to see what is what....
Yeah, that's on our to-do list to change. I guess we'll have to
No, the thread with the known issues of Audiobus 3. This is most likely not an iOS bug.
1) That site suffers from not being re-designed after the Audiobus 3 relaunch. We'll have to change that.
2) Yeah, sadly Apple also didn't do anything about those bugs so we didn't feel it was useful to update the site anymore. There aren't too many new issues though. The iConnectivity thing is not an iOS bug but most likely something that we can fix on our end, as mentioned above.
Okay, may the force be with you!
Hmmm - I played with Tonestack in AB3 through my ICA4 all yesterday and have it hooked up and working right now. What's the issue?
All the apps mentioned refuse to load in AB3. They produce an error with a hint how to fix it (by bringing the app to the foreground and then quitting it).
Are you sure ToneStack was playing through AB3? And would you mind testing some of the other apps if you have them?
I haven't had any apps refuse to load in AB3, and I'm always hooked to one of my 2 ICA4+ units.
So far, ToneStack, FluxFX, ApeSoft all working fine. Will test PositiveGrid apps shortly.
I have had to reset the input leading to these apps a time or two. Haven't determined that's either an AB3 or ICA4 specific issue, yet, though.
I'll get back when I do some additional testing.
That's very strange. I'm kind of jealous now. Would you mind sharing screenshots of your configuration? And which firmware is on the ICA? And what's the iDevice?
Just a suggestion: reboot your device and see if that changes things.
Amazing how often showing these uppity little iOS devices just WHO can turn off WHO brings 'em back in line
Unfortunately not. And it's consistent on iPhone SE, iPad Pro 12.9" and iPad mini 4.
And there's no problem with AB2 or AUM with these apps and the ICA.
My firmware version is 1.1.0. Maybe I should update it to 1.1.1?
Having issues with my ICA4 and AB3 as well now, yesterday wasn't this bad but today i can't even load apps into AB3...Tap to fix message everytime even after rebooting
Both Tonestack and BiasFX working at the same time through the ICA4+. iPad4, latest version of IOS. V 1.1.0 ICA4 firmware.
Hmmm
So what happens when you tap to fix? Are you simply not able to get it working at all, or do you just have to go through this fix message every time?
It tells me to bring the app to the foreground and to quit it. Then it keeps trying to launch it but it never actually loads into the AB slot. So that's it, every time...
I've seen that with a couple of apps, but I've always been able to get them to load. Usually had to get rid of the app in AB3, load the app manually, quit it, then try to reload in AB3. But not sure I am seeing the problem consistently with those apps. Just assumed they weren't fully compliant.
But I'm always connected to my ICA4, and haven't noticed this to be specific to the hardware. So, do these apps load fine when not connected to the ICA4 in AB3?
Only things I'd like to see in AB3 in regards to the ICA4 is the ability to select any of the 4 ICA outputs, and a better ability to make ICA midi port names more legible in the Midi connections area.
Yes, they launched fine without the ICA.
I have just tested the same apps with a Novation audiohub. they crash with it too. so the issue isn't restricted to the iconnectivity interfaces. and i can definitely confirm they used to work fine in Audiobus2 since i actually had gigs with the Audiohub. something broke between the move from Audiobus 2 -> Audiobus 3.
@Sebastian. any idea what it could be ? will test with my Native Instruments Traktor Z1 when i get time. but so far Iconnectivity ICA4+ and Novation Audiohub (which is a Focusrite chip inside) have both failed to work. works fine with the audio interfaces unplugged. Ipad Air2 running IOS 10.3.
OK. did a full ipad reboot. MidiSTEPS and MidiLFO's still fail with the Novation Audiohub but Tonestack and Amplitube now work. Here's where it gets wierd. Unpluged the Audiohub and plugged the Ica4+ back. suddenly Tonestack and Amplitube still work. rebooted ipad and they still work. it seems the only thing that doesn't in my case now Is MidiLFO's and MidiSTEPS. the audio apps seem to work with no issue. @Sebastian i can safely say i have no idea whats going on anymore lol. even Addictive Pro as an IAA used to fail before and its working perfect now. some sort of cache maybe ? that mantains even after multiple reboots ?
Ok. hooked up traktor Z1. Midisteps and MidiLFO's still fail. Amplitube,Tonestack and few other apps i have tested work fine. but a new wrinkle. AUM refuses to stay hooked up to AB3. it seems like the only way AB3 works 100% reliably is when no external interface is plugged in at all. so far 3 different interfaces all facing a problem in some fashion or the other. i can understand this is a problem with most new tech so i'm not that miffed about it. I just hope the Audiobus team manages to track down these bugs and squashes them soon
@Sebastian. i noticed a developer mode in settings. is there a way i could maybe send you some logs to help you find out whats wrong ?
The developer mode is not related to audio interfaces. We've tested Audiobus 3 with a few external audio interfaces and they work, it's just that the iConnectivity audio interfaces take over the audio session, which is probably the reason for the issues with Audiobus 3. We're going to have a look at this but it's going to take a few weeks (just ordered an ICA4+, then we'll have to figure out what the issue is, then we're going to have to test it, then upload it... you get the idea).
In the mean time I wold recommend focusrite interfaces or stuff like the Komplete Audio 6 from Native Instruments. Use it with a new Camera Connection Kit that has an additional lightning input to power the whole setup.
@Sebastian. i've tested with 3 different interfaces. A Native Instruments Kontrol Z1, A Novation Audiohub (which has a focusrite chip inside) and an Iconnectivity ICA4+. MidiSTEPS And MidiLFO's fail on all 3. they only work when audiobus3 isn't connected to an interface. so it doesn't seem like its anything to do with Iconnectivity at all. regarding the other apps that fail. it seems a few reboots make them work on all 3 interfaces. so so far it seems only those 2 midifilter apps refuse to work. everything else works after a few reboots. I am actually using the new camera connectionkit + lightening adapter with my ICA4+ so maybe that might be the reason why i'm not experience the audio app failure that @Munibeast is experiencing.
whoops. double post by accident. please ignore.
@Munibeast have you tried connecting the Ica4+ using the Apple CCk3 ? it seems like all the audio related apps work fine on my end. i broke my original cable so haven't used it in a while. Midisteps and MidiLfo's don't work with any of my interfaces so its nothing to do with the Ica4+. Tonestack and Amplitube work fine on my end with Audiobus's buffer at 256 samples and making sure the ipad is restarted first.
@Carnbot could you change the thread title ? A lot of testing seems to indicate that midisteps and midilfos have nothing to do with iconnectivity interfaces. they just refuse to work in general with any audio interface connected. everything else works as long as you restart the ipad and set latency to 256 atleast.
I've changed the title.
Ok. But I also wanted the thread to be about other issues and workflows in the use of AB3 and the iconnect for midi and audio. So I guess we'll need another thread.