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.
GarageBand—optimising performance message
Merry Christmas.
Why do we now get ‘optimising performance’ message in GB.
This happens when using many tracks...it stops the playback..looks like a mix down saving process on screen..and makes the file size suddenly a few times larger!
We never used to have this.
Thanks.
Comments
There’s a few things on google about this but i never found out what it was actually doing. One of the reasons (amongst others) that makes the GB workflow too slow for some people.
@IOSSOS this message has been around for a while. I used to encounter it a lot (a year or two ago), which just motivated me to go and purchase one of the other DAWs. I have an iPad Pro 9.7 - 2016 model with a dual core processor. It just started to do it a lot when I started getting more detailed in what I was doing and if I remember there was an iOS update involved somewhere too. So, maybe you're starting to hit the performance edge of what GarageBand is comfortable with on the iPad you're using? That would be my speculation. Either way, I found that this was happening with too much regularity and was just annoying me way too much and I haven't really spent much time back there since. I hope this gives you some insight. and....a very Merry Christmas to you...
GarageBand has always done this.
It’s basically freezing the tracks to audio to free up cpu at the expense of disk space.
Could be that a plug in is being a bit of a cpu hog. The way GB does this means you are not in control. It usually works well but if you have a cpu heavy plug in that GB had frozen and then you make alterations to that track, it will need to freeze other tracks before it can unfreeze it for editing or there wouldn’t be enough cpu overhead left. That might mean lots of other tracks get frozen.
f you don’t edit the tracks the at have been frozen, you might not even notice that it’s happened. It’s not possible to choose which tracks to freeze or unfreeze. It’s an automated version of Logic’s freeze feature.
I must admit I haven’t seen that message for a long while though. It happened all the time on my iPad Air 2 (which never worked with auv3s very well for me at all in almost any host other than GarageBand.)
Well I added GeoShred and that’s what started it this time.
Eventually the file size should get smaller again..
Currently gone from around 40 mb to well over 200 mb.
GB just has so many good things..drums guitars so simply good..but also annoying limitations..
Another thing is recording in two tracks together..audio and midi...but then not being able to disarm one track when you just need to record in only one track....many times the red record cannot disable.
Great points BCKeys.
Does it help using AUM with feeding apps such as romplers into these iOS DAWs?
Gadget is stable because it uses only its own built in instruments. No AU business.
You can use Cubasis or GB with no AUs and they will be rock stable too and allow to add many more tracks without crackling.
Yes stable without AUs...
Does AUM reduce the load when using AUs through it into Cubasis and GB?
Let me have a try now.
Thanks.
Yes.. I need to use AUM for stability...
But recording into Cubasis 2....the IAA connection went dead with AUM after recording even short section.
Reload Cubasis fine...but why...?!
Anyway no CPU problems at all as expected...
ROMplers are not generally CPU hogs though some chew up memory. Which ones are you finding to be such? (Digital D1 is a bit of CPU guzzler.)
Will agree with @BCKeys technique. It seems like the only time I’ve run into the message is when using really CPU hungry plugs (Model D, Model 15 come to mind). Whenever using just audio I never seem to have this issue. I recall loading up nearly 1000mb of stems for a remix on a 2018 iPad and it worked flawlessly, even after adding one or two more low CPU AUs and some various AUv3 fx.
It IS time consuming since there’s no proper freeze function (really LOVE how you end up with a billion copies of the same effin track :eyeroll:) but it’s my go to for a lot of different tasks, even if it is missing important things (like a mix bus arrggghh).
Thanks for points above.
Sticking with Cubasis 2 and AUM for the moment....no spike in Cubasis CPU.
Yes GB ...despite‘ optimising performance’ messages, is pretty solid.
And then I have BM3.
With all these I’m covered for the moment.