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
so far it doesn't seem like the Iconnect interface has any problem specific to it. doing extensive testing with multiple audio interfaces currently. if for some reason something doesn't work regardless what audio interface you're using a simple restart of both the interface and the Ipad seems to fix it.
@Sebastian, I noticed a strange behaviour that may shed another light on this matter (AB3 with iCA4+) (AUDIO page)
That makes any sense?
I don't own bias fx but both amplitube and tonestack are working perfectly here. do this. shut off the interface and restart the ipad. see if it works then. I'm quite curious if it does. also. what are settings of the ICA4+ ? i'm running it at 44100 Hz 24bit with no issues.
Yes that's true and I think the problems lie with Audiobus as there are bound to be some early bugs. But I'm also interested in the way people will be using AB3 and ica4 and their workflows live and in the studio etc
But can always discuss that elsewhere and maybe that should include other multi iOS device interfaces.
Did a quick test of BIAS FX and worked ok here.
So that's 2 people with the Ica4+ having no issues with tonestack etc. A restart should fix everything I'm certain at this point.
Only other factor might be that the bitrate is different from what we're using. Atleast in my case 44100hz 24bit works fine.
It is very strange though that initially using AB3 even multiple reboots of iPad weren't helping when using with the iCA4 I tried rebooting many times and also rebooted the iCA4. Since then it seems a lot better for most apps so far (except ArtKerns apps).
Having a problem with iWavestation in AB3. Probably we need an app compatibility thread with a list.
this is a question i'm curious about. with your earlier tests had you rebooted the interface itself ? like switching it off and on in the mains ? the ArtKerns apps currently dont work with any interface i've tested so its probably an issue with the apps themselves. even loading them into a midi slot can cause other apps to be dicey. just ignore using them at all if you're using any audio interface. hosting them in AUM for multiouts or standalone with Ableton LINK for midi only works for now. iWavestation was working in my tests earlier. have stepped out of my home so will have to test some hrs later when i have access to my Ica4+ again.
@gonekrazy3000 said:
IWavstestion starts working now, so it's sporadic for me.
Yes I even tried two different iCA4s.
So an advantage of an ICA4 with AB3 is you can get around the restrictions of not being able to choose any midi port as a sender. I'm hoping that someone will make an AB3 midi router app at some point which can do this on one ipad eventually because otherwise some midi apps will never have access. Hopefully midflow will allow us access.
I've just set up Modstep on one ipad sending to my other ipad and can use that in AB3 for now.
on the flipside iwavestation is the only Korg app that lists in AB3 at all as a midi reciever. hopefully once they upgrade all their apps to AB3 compatibility this will be solved
I think that's because it's the only one which is an IAA instrument (as far as I know). Think AB3 is supposed to pick up all the apps which support IAA instrument as a receiver.
Just had a quick test with my ICA4+. Fired it up and tried both Bias FX and AUFX:Space. Both initially launched, then crashed after a few seconds, and AB3 showed 'Tap to Fix' then got stuck on 'Launching...' after swiping out the app and trying relaunch.
Checked ICA4+ audio settings and saw that it was on 48kHz, 24-bit, so I changed it to 44.1, 24-bit. Committed changes and Reset ICA4+. Back to AB3 and everything works fine now: Bias FX, AUFX:Space, VirSyn AudioReverb, Flection... noodled on my bass for 15 minutes with no issues. Never rebooted iPad.
iPad Air 2, iOS 10.3.2(beta)
This confirms my theory that it was sample-rate that is the issue. good to hear 44.1 24bit works
will have to see if 48 and 96 cause issues on my other interfaces when i get time.
Hmmm, mine is set to 16 bit. I'll try 24 bit and report back. Just for the record once more: rebooting iDevices and ICA and being on 44.1kHz 16 bit the problem is as I stated earlier, basically nothing works at all. That's with the USB to lightning cables that came with the ICA. I only have one CCK to try with it but if that's the problem it would mean I couldn't use two iDevices together, which is the whole point of the ICA.
And I don't appreciate the premature title change, @Sebastian.
FYI Mine was always set at 44KHz 24bit, initial problems but now having less problems.
Changed to 24bit, 44.1KHz but still not working. Using CCK instead of iConnectivity cable changed nothing here either. So please don't assume the problem has been solved for everyone, when some people say it works for them.
I'm using a Focusrite Scarlett 18i8 and I am getting the same problems. The only way I can get AB3 to run is to unplug the iPad from the unit, load AB3 and apps and then plug the 18i8 back in. Then it works okay.
Well it's odd, just had a problem loading a midflow transposer, wouldn't load, unattached to the iCA4 and it loads ok, reattached and continues to work. Now reloading it works ok icA4. So bit of strange behaviour with AB3.
@Munibeast I'm using the cables that came with the ICA4+, not a CCK. Perhaps there is some deeper setting that differs between our configurations. I noticed when configuring ICA that there's a frame latency setting just above the sample rate, which I believe I have set to 3. Didn't change it from whatever the default was. There was another interface setting in that same group, but I don't have it in front of me now that I'm at work. AB3 is set to 256 frames latency. Perhaps with enough detail here, we can find the pattern of what works vs. what doesn't.
When you're saying 'same behavior' you mean with the midiLFO/midiSTEPs apps or without?
I'm still having few to zero problems with AB3 and either of my ICA4's. For the record, my devices are set to the following:
ICA4+
Formware: 1.1.0
Audio Ports: 3
Audio Frames to Buffer: 2
Sync Factor Value: 2
Setup: 44.1k 16bit (have also tested 44.1/24bit)
Clock Select: USB Port 2 Clock
AB3
V: 3.01
Latencies Tested: 512, 256, 128
iOS Device
iPad Mini 4
iOS v: 10.3
I've tested the following FX apps without issue - they opened fine, save with a preset, and after completely closing AB3 and all apps, the all open fine again when restoring the preset and work fine on my ICA4+ interface.
ToneStack
BiasFX
AUFX - all
Echo Pad
Fiddlecator
ApeSoft - all
Obviously, there's got to be some difference between the people having so many problems and what I'm doing. Maybe others can post specific device info above.
@Sebastian - is there any additional information you would like to see?
The reason why I've updated the thread name was that apparently most of the issues stem from using midiSTEPs and midiLFOs in combination with audio interfaces, which is a bug that I have confirmed with the developer of those apps.
Just to confirm: When you're saying that you're having zero issues and listing your apps... you're not using midiLFOs and midiSTEPs, right?
iConnectivity will not be able to follow the link that I sent them for this discussion unless it is changed back to what it was originally.
Thanks to some of the suggestions I was able to get some success by launching ToneStack without the ICA4+ and then adding the interface. After quitting both AB3 and ToneStack and restarting AB3 and ToneStack this time with ICA4+ it seems to work. So I'll do more testing and see if it will keep remembering this.
@Sebastian said:
I hadn't, though I just tested MidiLFO and am definitely having the Tap to Fix problem with that particular app. Can't get it to load no matter what, so far.
Okay, it sometimes works with the ICA connected now, about 50/50 I think. The only reliable way for me is to launch ToneStack (or most other apps) into AB3 before connecting to the ICA4+.
@Sebastian - I was finally able to get MidiLFOs working 'without' being connected to the ICA4. I saved a preset with only MidiLFOs, exited both AB3 and MidiLFOs, reconnected the ICA4, and reloaded the preset. Doesn't appear to work when connected.
It might be good to have someone try this with just a normal iConnectMidi (No Audio), to see if this causes a similar issue.
midilfos is broken with all audio interfaces. its not specific to the Ica4+ unless you mean you got it to work somehow ?
AmpliTube doesn't make any sound in AB3 with ICA4+.
Another weird thing is I get just 1 channel in the mixer although I have 2 lines going.