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.
Freezing tracks to audio in AUM 1.4 (kinda)
With AUM 1.4 update it became possible to free cpu power by bypassing the node.
So… we could record an instrument to audio (using any AUv3 audio looper or even internal AUMs recorder) and then bypass it.
Similar to freezing in other DAWs.
BIG advantage is that we can go back to bypassed instruments at any time for editing, re-recording and stuff.
In this session I had 8 Moog model Ds on 512 samples buffer using old basic iPad 5 2017. Pay attention to dsp load in AUM, it was in 30% zone with Moogs bypassed. Nice)
Thank you @j_liljedahl , you are the boss!
Comments
Now imagine if AUM also had 'Buffer Nodes' where the buffer-size could be set between 1-16 bars that could be either one-shot or loop similarly to the already existing file-player node?
Recordings would go straight into AudioShare and if overdub is enabled a new file/copy would be created on each loop as long as overdub is enabled and once overdub is disabled the latest buffer would keep on playing.
There would be no need for time-stretch as the way AUM just changes speed would be one of the charms of the 'Buffer Node' and adjusting tempo would create some interesting effects when overdubbing
The 'Buffer Node' could also keep track of all recordings in the current session and the file could be switched on the fly.
A toggle for 'tape-direction' could also create some interesting possibilities when overdubbing...
Maybe @j_liljedahl already has something similar cooking, we never know but considering AUM can already record and has a file-player all the needed functions are already there...
Cheers!
@Samu neat idea! As you said, all the needed functions are already there)
Something along those lines is on the roadmap, but I call it Track nodes. It’s simply a node that combines recorder and file player.
Nice!
I'm slowly adjusting to recording audio in AUM (in a step to replace the recorder in AudioShare as it doesn't support AUv3s) but most of the time I forget that I need to tap 'pause' to instantly stop recording as tapping rec waits for the next bar.
Is there a way to temporarily 'disable' the bar sync for starting & stopping recording? If there is I've not found that one yet.
For 'sampling duties' it could be nice with an option to allow the transport to wait for a midi note input (or wait for incoming audio) before starting to record. Think arming a track for recording, tap rec and then play the onscreen or midi keyboard to grab the audio. My current work-around for this is to use a sequencer such as Aton 2 to trigger the notes...
I can already see plenty of use-cases for the 'Track Nodes' by the basic description alone
😎
nice to see this on the roadmap
I could see this feature being implemented into Neons recording options: ‘trigger by midi note’. Maybe expand on it by automatically creating slice markers when you trigger another note (and append to the recording if it’s been stopped). Checking into it again, the Auto-Sampler feature seems real close 😭
No, but as you said there are two ways to stop recording: tap record again to wait for the next sync quantum, or tap pause to stop recording immediately.
>
Yeah, just have to remember to tap pause instead of rec to stop the recording when using it as a 'field recorder'.
I've noticed sometimes if the recordings is short (<1-2s?) no file is created but for now I'll just keep it going for a bit longer as there is no indication if a file is created or not.
This does feel like a bug as it's highly repeatable. ie. start recording and within 1s tap 'pause' to stop the recording and no file is created. Keep recording going to >1s and a file is created.
Anyways, no biggie, I just need to 'cool down'
Cheers!
I can't reproduce this here. Are you sure the recording had started before you hit Pause? If the transport is already running, it will wait until next sync quantum before starting recording. Same thing if it's currently connected to an Ableton Link session.
I'm quite sure I hit record before tapping pause...
Here's a short video example, internal mic & screen recording.
https://www.dropbox.com/s/ibxrt2buoyrcudl/aum.mp4?dl=0
Most of the time the 'missing file' happens when I continue from a 'paused state' and stop before the 'bar' has finished.
This 'thing' does not happen if I rewind between the takes.
An optional 'pause/stop & rewind' option could also be handy in these cases?
My conclusion is that AUM only creates the new file at the beginning of each bar and not 'mid bar' which kinda makes sense.
Cheers!
Right, that could very well be the case. I think it's rare that someone would want to start recording mid bar.
True, but a 'field recorder' has no 'bars'
As long as I remember to 'rewind' between takes things work as expected...
...so an optional 'auto-rewind rewind on pause/stop' could work here?
Another way would be an option to disable sync and create the file the moment rec is tapped and start recording when there's input (ie. a plug-in starts to output data and/or a threshold is reached or the transport is started).
If the transport is already running and sync is disabled rec would create the file and start recording the moment it's tapped and stopped when tapped again while transport keeps on rolling.
AudioShare works like a charm for these kind of field-recording duties when disabling the open recording.
I can just keep the phone in my hand, tap to start and tap to stop the recording and each take creates a new file but with no AUv3 support it's getting less use for every day that goes by.
(A nice improvement to AudioShare would be to be able to batch-process or record sounds thru a chain of AUv3s?).
Being able to fully replicate the AudioShare recording flow would be a big win for AUM and there's quite a lot of overlap already.
AUM already does synced recordings perfectly (apart from when using TB Barricade which has some kind of weird variable over-sampling that can sometimes mess things ups (ie. the beginning transient of a loop is at the end of the file and would need to be scrolled on X-Axis. Think it's called 'Slip' in Blocs Wave).
Definitely no need to add any of the above but even more tips will be rolling in when things head in the right direction
Cheers!
I just checked and yes, starting recording always waits for the sync quantum, so if you're already at time 0 it will start immediately, otherwise it will wait until the next sync quantum (default 1 bar).
I think an option to auto-rewind on pause would possibly confuse things. I try to keep options to a minimum. You just need to remember to rewind before recording
However I could consider adding a Sync Recording on/off option.
One thing missing is a warning before saving when some auv3 crashed.
I lost my songs a few times with loopy and koala used as auv3,
Sometimes koala or loopy crash and I saved the project without noticing those nodes have crashed, then I’ve lost all the samples recorded in those plugins.
A warning when some nodes have before saving will be welcome.
Dunno if I’m the only one in this case.
Not sure what it has to do with this thread
But yes, that's a great idea. Will note it down for the future.