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.
Demonstration of a usecase (experimental)
Hi, I've been brewing up a multi-usecase, like modstep controlling the midi side of things, my cheapo keyboard with a few controller knobs, a few apps, thumbjam, animoog, auria's lyra piano, the fabfilter one, all inside aum audiowise, a little aufx flavor, some timeless2, turnado on the whole mix. Fugue machine juggling the counterpoint, all automated and ready to record in modstep, with panning. But I 'only' have a mini2, and the components kept fluctuating throughout the making procedure, sigh.
Can anyone of you confirm the whole shebang in action, please (:
Here are the protocols:
Audiobus preset 'usecase': http://preset.audiob.us/iyO5FAStvZU1NUN
https://www.dropbox.com/s/qgy8w0q1m84r4cs/usecaseAuria.zip?dl=0
https://www.dropbox.com/s/3dbovrgjzxjncxz/UsecaseAum.aumproj?dl=0
https://www.dropbox.com/s/oftrnjxptz3hs35/usecasemodstep.mss?dl=0
p.s. the first track in modstep contains aum port1, just to flipback ( and control timeless2 in Auria, and midi out should be 'modstep' (to auria), track3 goes to thumbjam, it's confusing the connections on reload (bug), but hey ...)
Thanks (;
Comments
I would avoid to put Auria at the start of the process to keep some resources free.
Midi connections a bit awkward: many times I found my self struggling at midi connecting because I was sending midi out to the sound module and the sound module listening to the midi output of the note generator. The correct way instead is this: if I route midi out to instrument in ports then the instrument should listen to its internal in port; if I do the other way around with the intrument listening to the sequencer out I should route the sequencer to its internal out. This is particularly true with exclusive midi in/out, aka you can't set them to multiple ports.
Your setup has exceedingly over my sovereignty!
I even can not figure out what the going-on from photos. My friend!
I have never done with Fugue inside the chain unless you want the internal Fugue sound with.
Why Modstep and Auria in one AB input?
I chicken out now.
I think the setup should be as simple as possible. And understand the stability of how each part working, then grouping.
I don't have time now, @crzycrs . Do you want me to set up my way and upload all the photos for everybody?
I can do it later today. Maybe 5 hours late.
This might be doable. It definitely looks like one of my monster ableton chains lol. Don't own auria so I cannot test it myself. Although having fugemachine and modstep inside audiobus confuses me. I'd rather just have them outside both aum and audiobus and just load the appropriate preset which I name the same as my aum and audiobus project.
Hi, @crzycrs , left timeless2, I have almost done my setup.
I will show every possible photos in this thread for you! Need time to eat dinner.
Sires, thx, molto bene. Please, take it easy on that, I'm a bit occupied (ask @rhcball, depressed as defense mechanism for not knowing enough about compression & needing a rest after just having built a paper robot together with my lovely step-daughter.)
There is much to say about the task at hand, but it's too exhausting.
Added and deleted many variations while preparing. Will chime in later when being restored over 10%.
@crzycrs ,
I have the setup completed. It is very perfect in my opinion.
Everything according to your specifications. The photos also according to the order for setting them.
So this is a good chance for real practice for everyone here.
Cheers
It sounds nice from your specs. Btw, Modstep track5 for turnado modulation for all 4 instrument on AUM. All presets can be saved on Audiobus sate saving. And should not do IAA fx on AUM. Except you want AU presets. When inserting apps on AB, you need follow input, fx, output order. End.
Only when you need midi clips recording, arming the Modstep A button.
Very efficient setup. I can say.
@crzycrs , I have almost forgot to say how to recording Fugue playhead by AUM!
There is also Auria bacground setting page for your browsing.
See nothing in the backdround for this setup.
@crzycrs,
When recording on AUM mixer, you need a port on Modstep. However, our setup has Turnado on Port 1, so you now should drag Port2 on Modstep.
Then on AUM the final puzzle is bring the Port2 of Modstep to input of AUM and ouput port2 of Modstep to AUM output.
Then press the CHAN6 speaker recording button, then upper red recorder button, then press CHAN7 Modstep playbutton to begin.
When finishing, press the upper red button first then CHAN7 stop btn to stop, finally stop the speaker btn.
Such complex thing if for.....
Lastly, your tempo matched audio file ready in AudioShare from whatever you can do with midi modulation and live/midi data fugue play.
@zarv , here is goodie!
I have given you guys no one try to show on this planet although it is not that difficult. Yes, my best shot.
Final picture
Conclusion,
This lesson demo a real practice for all apps together ...
Everything driving by Modstep including midi recording,
Everything (presets) saving in Audiobus and AUM,
Everything mixing on AUM including play/stop/recording (Ableton Link) audio file.
Please, don't link Fugue Machine in this setup.
I'm curious. whats the reason for disabling link on Fugue ? i haven't really used it with link on myself. just wondering. does it cause some problem with the midi ?
If you enabling Fugue, you can not let Modstep drive its tempo. Therefore, you can not command the start and stop to record midi notes back to Modstep. There is no other options for this.
Everything (apps) can be linked except midi sequencer app when work with Modstep. Don't tell me Midi Link Sync, if. Just show me? Anyone? I will be glad be taught.
Cheers
oh ok. that makes sense. way i work is i actually have modstep sending midi to actual ableton. and in that i just record into endless clips. so for me it not starting same time as sequencer doesn't matter. as long as link keeps it at the start of a phrase i just change the start point to where it is. but i understand your reason. awesome tutorial
Thankyou once again, @Kaikoo2. Still loading batteries, having some real-life absurdities going (always).
However, I´d like to speak about some thoughts that occured to me lately, and specifically browsing thru this thread. One important notification before: I´m definitely no pro and welcome opposing and correcting opinions, and have been `´corrected´ already by Kaikoo´s take on the case.
Either the timeless2 in Auria, which I like to tweak kaoss-pad stylee, (not by the keyboard,
midi in
stays empty on the first track). Thus, I created random cc´s, named them x and y and assigned them with ´midi-learn`. In Auria, on an empty miditrack, the input is ´modstep´ again, the specific channel, and output goes to ´plug-in: ff timeless2´.Or the Aufx', which I wanted to control with the keyboard´s knobs. 'Midi-in' coming from the keyboard, 'midi-out' again virtual 'modstep' - now in Aum all that´s left to do is tapping ´modstep virtual´ in the midi routing and choosing an individual midi channel (corresponding to the modstep track). Plus to tick midi input = modstep in aufx, and select the channel and the fitting cc for any parameter (either by midi-learn, or by defining.)
@gonekrazy3000 and Kaikoo: Why Fugue Machine and Modstep in the audiobus
chain? And why a modstep track with an aum port `doing nothing´? Simply for (my personal) convenience, as they appear in the ab sidebar for switching back and forth. Plus the biggest advantage: ab global start/stop. Period. (I just deleted the modstep or fugue tracks that were created in aum - Kaikoo in the last step added a modstep port ´connected to itself´ for that, if I´m not wrong.)
The question that arose in other threads since aum´s release: what are
ports
for? Here someone else with more capabilities to explain, @wim: ´The best and most stable approach I've found is to load all my input apps into AudioBus. I load AUM as an input as well so it can be my AU host. If I'm using ModStep or another app for sequencing I load as an input too. Next, I add AUM as an output as well. This gives me all the input apps in AudioBus as audio inputs. FX go in AUM, either on their individual channels, the master, or any send buses I decide to create. If I want to get serious about mixing I Auria Pro for AUM in the output slot. I find this provides stability, state saving, consistent app switching, and a better working "Start All" button.´And that´s what you can see adapted here, Auria´s instruments go out through the Subchannels into Aum, and with an Aum port, audio comes into auria to be effected there (with fx on a bus and aux). This would also apply to studiomux or musicIO, if I´m not mistaken.
Please keep at Kaikoo´s wonderous path, congrats to those who made it to this point, (Tl;dr.)
And be careful with the zombies.
Tl; did read and killed a couple of zombies just for fun.
Just a little add on this matter: if you are going to route multiple sound modules into AUM via AB you won't need to have separate AB pipelines to have separate inputs into AUM unless you put some app in the FX slot. In other words: sources in AB are loaded in parallel so, as long as you don't load anything in the Fx slot which is a serial bottleneck, you can have as many inputs as your device can handle outputting to AUM(and probably to Auria aswell but I didn't bothered to test) into separate channels. Probably it will be slightly lighter on cpu, but I'm just assuming, but it will for sure be beneficial to your workflow: one tap less every instrument you load, a more compact overview in AB and shorter loading times.
^ yep