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.
iPad AudioBus to iConnect 4 and a second audio interface
Hello. If you've read some of my other threads you know I've been slowly buying new hardware. I want to run everything directly into my computer for mixing. I've already got a iConnect 4 with a connected iPad Air 2 through AudioBus.
Can I buy an audio interface from a different company than iConnectivity? There's a Focusrite for a $100 less. Would I be able to run audio from the second interface to my iPad? Thanks.
Comments
Nope. IOS doesn't let you combine Audio interfaces. Just 1 set of inputs and 1 set of outputs.
Maybe with studiomux?
@mkell424 I'm a bit confused. If you already have an iconnectaudio4 why not just use it to route audio between PC and iPad ? Why a second interface at all ?
in my understanding it's about a 2nd interface for the PC.
The iCA4+ also routes virtual channels from the PC environment to IOS apps, not just the hardware inputs.
On Mac I'd be rather confident with an aggregated device.
In Windows you can fake something similiar with Asio4All, but it's not predictable in a general sense.
Basically chances increase if both audio-interfaces feature the same USB chipset.
cheers, Tom
I own an ica4+ so I already knew that. Thing is though if you use asio4all the latency jumps up quite a bit. The lowest I have gotten it to with 2 interfaces connected at the same time was 12 ms. Lower than that has made it unstable. While using just the ica4+ I got it down to 3. Adding a second device just ruins what makes the ica4+ special. And heaven forbid you unplug one of the interfaces by accident. It's an instant BSOD....
good to know in advance...
But 12 ms isn't that bad at all - latency only matters while recording critical things live.
My DAW for 'post-processing' runs on a 2048 buffer base and it's no problem - everything is precisely in sync, just starts 2048 samples 'later'.
I can comprehend the wish to add more external sources this way, because the iCA4+ has a limited number of inputs .
(imho they'd rather extend the 4+ with Adat than to release that stripped down 2+)
cheers, Tom
Agreed - 12ms is not too bad at all for live - I normally run an aggregate of 5 devices on a Mac with 13ms
20ms is about the threshold of general acceptability. 15ms-20ms is noticeable by some, not by all. Fewer notice 10ms-15ms. Above 20ms and it can be a distraction, sounding like an actual delay. 10ms-15ms is usually fine - although experiments seem to indicate that some will notice.... "something" in that range. It also seems to vary somewhat depending on what instrument you are using: voice vs. guitar (or other stringed instrument - violin, etc.) vs. synth / piano / etc. where voice and guitar seem to fare worse and latency becomes more noticeable.
Anything below 10ms is usually just fine. I'd be happy with 12ms.
Problem for me is I notice anything above 12ms. You gotta remember that every time you add effect vsts to a track it adds a few ms latency in ableton. So if you already start with 12 Ms latency 2-3 effects later and you will definitely notice the delay. Meanwhile starting with something super low even a ton of effects and you will still not notice a delay.
Understood. And it doesn't affect everyone (cause the same level of uncomfortability) the same way. Others adapt differently. Sure, there's a point where everyone will find it difficult!
So I understand it is possible to run more than one brand with the iConnect 4+ but the iPad but no audio from the second device to the iPad?
Not sure what you're asking. More than one brand... of audio interface? If so, no, you can only run one audio interface to the iPad at a time no matter the brand. No aggregation. Is that what you're asking about?
If you mean, to a Mac? Then, yes, you can aggregate across most brands without any hassle.
If you mean, to a PC running Windoze? Then, with limitations you can achieve some degree of aggregation with ASIO4ALL.
Unfortunately, owing to the way that certain drivers interact on Windoze, if your interface has more than 8 audio channels, you will possibly only see the first 8 as part of an aggregate via ASIO4ALL. E.g. if you have a 16 channel and a 4 channel and you aggregate you'll end up with 12 channels. (8+4 instead!
) Yes, it's dumb! 
I have exactly this problem with my Windoze rig. I have a 16 channel interface. I cannot aggregate anything else with it sensibly, so I don't run my iC devices into the Windoze rig or I'd lose my other analog audio. That's a Windoze issue, not an iC issue. In a Mac studio however, I have 28 channels in and out via 5 aggregated interfaces and I lose no channels from any device.
On a PC, If you have say, a 6 channel + an 8 channel, you'll probably end up with 14 channels via ASIO4ALL.
If I misunderstood your Q, apologies
I think "64" in AUM is equivalent of approx 2ms. It's okay for synths to be at 128 most of times, but for voice and guitar, it's really noticeable above 128, but get crackles and instability at 64...
I know that's nothing to do with this thread, just to discuss
Thanks. I was wonder because I wanted to have Auria Pro record more than 4 external input audio channels. I'm looking to add a box, not get a new 8 channel device.
Ah, then no. You can aggregate on the Mac but not on iOS. Though, if the signals are starting in your computer, the ica4 has virtual channels you can use in addition to the 4 analog inputs. I've never tried it from the computer though.
So if I understand, it might be possible to run the second audio interface into the audio iConect 4 virtual inputs and then on to the iPad?
not exactly, syrupcore meant a software synth/sample on the PC which would be easily routed to one of the virtual channels.
If you want the input of another external interface to show up in IOS, you first have to convince Windows that the iCA and the 'other' interface are 1 unit.
(which works well on Mac as 'aggregated', but only to an unpredictable degree under Windows with Asio4All)
Additionally you need some host application to assign the path.
(at least I never noticed any matrix functionality in Asio4All)
cheers, Tom
Yes, it's possible @mkell424. I route hardware synths and guitar and the like from other audio interfaces via a DAW into iPads for processing.
However, if I was going to do that as a permanent setup I'd probably either consider use Jack, or use an aggregated device in the DAW and then route the audio out from channel strips to the other inputs and just start the DAW for that purpose with a template or the like. It's a lot of trouble to go to though to use the iPad to do the recording when you've already got a DAW there in the Mac/PC
OTOH, in S1 I use the Pipeline Stereo tool regularly to route audio out from a track to an iPad via the iCM2+ or 4+ and back again to use it as an external FX processor, but there's no reason not to just send it there, e.g. to Auria Pro, with no return by the same kind of method, or via a bus that's routed to it as an output from the DAW, etc. etc.
Thanks.