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
The cubasis way
+1, render to a new track with option to keep midi track, please
Cubasis way please
I have no experience of either but the cubasis way sounds good
Cubasis way please!
Luckily you all have the same opinion!
I think it's actually the most easy to implement. I can block all touch events on the frozen track's mixer channel and track lane (done) and draw the frozen clips in a greyish color (done). I'll leave the other necessary parts for tomorrow.
Sounds good
May I suggest to add "Open in.." in the context menu of a frozen track or audio track?
That's somewhat harder than one would think since clips aren't audio files until they are rendered (or un-edited/altered). Of course doable.
@dwrae when using soundfonts, how does AEM decide what the default vibrato rate for the mod wheel is? Using the mod wheel on some soundfonts produces a very fast vibrato, others are slower. Can I specify it myself?
It’s still useful to be able to process the audio from a frozen track, it’s just changes to the midi data you should block.
I’m wondering if maybe the cubasis way might be a bit messy. If we freeze the midi track and it creates a new audio track that can then be edited as audio, then the two tracks will be out of sync (in terms of changes, not time). This isn’t ‘freezing’ I don’t think. Freezing should be a temporary thing to save cpu.
It would however be good to have a ‘render to new audio track’ option on a midi track, but that’s a whole different thing. The two shouldn’t be mixed in my opinion.
If you’re able to do this, I’d like to change my vote to the Auria way
Although you should be able to change volume etc on a frozen track if that’s what you mean @TheOriginalPaulB ?
Yeah, I meant mixing, panning and effects processing.
In that case I agree with you
there is some confusion around the terminology- freeze to reduce cpu, vs render (which has the same effect but yields a audiotrack to play with.)
Auria has both. It freezes, without producing an audio file, and it also renders, but the render function Auria calls “bounce”, and it makes the midi track go away, (because it’s “bounce in place”) some DAW on desktop offer the option to bounce in place or bounce to new track, but I haven’t seen that on iOS
Given my workflow, a render or bounce function is something I do many times in every project. The freeze function has much less utility for me.
When rendering I like to keep the original midi track along with the new audio
Yeah it should keep the midi track as it’s easy to just delete it if you don’t want it
MTS has a cool slant on this: you just copy a midi file from an instrument track and paste it into an audio track. It renders (or “prints” another term I picked up here on the forum) the instruments and effects, and leaves the midi track intact.
It also does the reverse: you can copy an audio track into a midi track and it will “render” the audio to midi and you can assign it a new instrument....
I can’t get my head round how the reverse thing works but that sounds incredibly useful!
But that's just 'Render track to audio file' in AEM and importing the resulting file.
The thing is with Cubasis freeze leaving the audio free, it makes it easier to chop and rearrange the audio of apps like Model 15 (that use up resources quick), but still get back to the original midi if needed later.
You could do that with the render to audio track option though. Freezing should be separate functionality.
Not being argumentative, but why do you think it needs to be seperate for when I use it as described?
I may be misunderstanding but it seems it’d be better to be able to toggle freeze on and off quickly to save cpu, then if you want to render to audio and slice that audio up you can do that too, with or without freezing.
As I say, I haven’t even used cubasis so I might be completely barking up the wrong tree
Yeah, I can see what you are saying. It’s probably just a habit I’ve got into as I then select all the audio cuts and move them to a new track. Maybe I’m a bit back to front as I’m never sure when I’m going to mess with the audio. Also I often find myself splitting audio tracks to use differing fx too.
Yes, I probably work in convoluted ways lol
Y> @dwrae said:
Yep. And it’s sweet. Use it all the time in AEM.
The only thing I like about what Cubasis calls freeze, that I would add to AEM, is to have the resulting rendered audio added directly to the current project without having import to current project as a separate function: it’s good to have it stored in the files, but I’m always doing the render for the current project, so a one step render to current project without an additional step to import it would be very convenient (often it’s additional steps to find the render: when I’ve been browsing in other files it takes more file diving taps to get back to current project files)
So to amend my previous vote: A freeze like Auria that simply freezes the midi track and zeroes out cpu usage for that track (without actually creating an audio track) could be a useful separate function. It’s not a priority feature for me personally but seems like it’s important for plenty of other users.
And it would be nice for the render function to place the new audio file automatically into current project
A good freezing feature is Ableton Live's one: you can freeze/unfreeze any track and you can permanently render it as audio too to apply some audio edition.. You can even make copy of frozen track before audio rendering, and put frozen backup(s) in a group for archive inside song when you need to work on original again..
I think the GUI for rendering audio should show "Render to a Stem" and have a check box default "Add Stem to Project" and a checkbox for "Save Stem to File". Defaults on/off could be set in settings. Most people now call audio conversions Stems vs tracks, frozen, etc. Them just mute the midi so I can mute the audio stem and unmute the midi and edit or extend that track.
This way I can make audio snapshots at any point in a project and have them for editing as Stems too.
I think using "Freeze" without contributing added value makes AEMS fell like a knock-off and you can hit the ball back for them to up their game.
But you can already do everything you describe by rendering a track to audio then importing it again.
Freezing is different - it’s for saving cpu.
The majority of people do not know what a stem is. There are lots of non-native English users as well, so I think using the word 'stem' is not a good idea. The checkbox is though.
As a non-English person, I have completely no idea what you meant by that sentence!
I speak English...not sure what it meant either
Why not Logic Pro X’s way if possible, @dwrae?
Bounce track in place with FX ** - replaces the original track with a rendered track
**Bounce track in place without FX - replaces the original track with a rendered track but keeps the FX available
Bounce to another track with FX - mutes the original track and creates a rendered track
Bounce to another track without FX - same as above, but keeping the GX available
Freeze - just freezes the track, Auria-style, easily reversible, for saving CPU resources
Now that would a, ahem, game changer,