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.
How do YOU use the iconnectaudio4+ Audio Patch Bay and Mixer?
How much have those of you with iconnectsomestuffwithaudio4+'s delved into the rather frightening Audio Patch Bay and possibilities with the Audio Mixer? They certainly left all the options available.
It's taken an effort to wrap my head around what is going on, it is kind of like a digital mixer, in that any input, including 4 channels of digital audio from each of the ios or pc/mac things plugged into USB, can be sent to any output, or, any channel on the internal mixer. You can design the internal routing. And then there is the mixer, it is kind of a "matrix mixer" of sorts, with shared inputs, but different mixes of those inputs, for each output.
The default setup is pretty sensible, thank the lord you didn't have to start from scratch, but I was wondering what kind of scenarios the iOS musicians here have concocted with theirs?
Some scenarios I can think of right away:
Simple, but having the mic/line inputs go into the Audio Mixer, for zero latency monitoring. Essential for recording live instruments and vocals. Would also be handy for doing dry/wet effects mixing, if you want zero latency on the dry. Like for using the ipad as a looping pedal. This scenario would, i believe, require replacing both USB ports 3rd and 4th channels into the Audio Mixer with the mic/line ins.
A small refinement to the above, if you usually only have one or two things to plug in at a time, is having the dry available on just mic/line 1 & 2. That way you plug into 1 or 2 when you want to hear the dry signal, or 3 or 4 when you don't want to hear the dry, like, if you are pluggin in a guitar, and want to use an amp sim, you don't want to hear a plinky, clean guitar mixed in with your virtual mega stack.
Using analog line outputs 3+4 for a subwoofer, and picking and choosing which signals go to the subwoofer. Like in bigger PA setups, you'll use an aux send on the board, to send certain channels to the sub (probably bass and kick drum, and backing tracks).
For a live performance, and using the iCA4+ as a submixer, splitting up outputs 3 and 4 to be independent mono mixes in the Audio Mixer, and using them to make two monitor mixes for on stage, while sending the stereo sound out 1&2 to the front of house.
Comments
I'm one of those wierdos that literally patches the Audio Patch bay as i'm working on the track.
like literally changing the wiring all the time. i keep the Ica4+ at 44100 24bit so have a ton of busses between the Ipad and Pc. i basically rewire and record then rewire and record onto another layer till i have a ton of audio clips.
e.g:- ruismaker drums => seperate ableton layers. certain ruismaker recordings into mobius lab one at a time to get even more recordings. so on and so forth.
shure that's tempting... but in fact you'd quickly get better results when you start from a blank table and route every single path (you need) manually a couple of times.
This makes you think about the logic behind it and builds up an intuitive understanding of the matrix.
I found it quite painful , similiar to RME Totalmix (early version), as I'm used to a system that does this job graphically (like in Modular synths).
But that's just what it takes, so I bit the bullet and slowly improved.
Atm my setup isn't too complex, but keeping things lean helps to avoid errors.
In a DAW context it's important to have an understanding of signal and monitor path.
A 'wrong' setup (like duplicate monitor paths) may sound quite good, but the final mix will suck most likely.
No need to follow this advice, it's just a hint.
There is a learning curve with any similiarly complex scenario - and in fact it seems to frequently shriek away people, according to what's asked on iConnectivity's forum.
But I expect them to polish the surface sooner or later - it's not really finished.
Gain setting and metering is a total mystery to me...