You were great young man. my children got it and you were straight to the point. Most of the other people doing these videos and explaining are a bunch of talking heads. Good Job! I've been a teacher and professor for some 45 plus years and have produced with some of the biggest names in the business. Keep up the good work.
Great comment. When I’m working in pro tools I/O is one of the first things I look for! Another thing is when you’re finished making an instrumental, it’s good to export the mix and record vocals in another session to reduce CPU strain as well!
Here is how I fixed mine permanently I went to Best Buy got a 3 TB external SSD drive then opened my LOGIC folder and got all my music files out and copied them to the new SSD drive now make sure you open your files from the new SSD drive and not the existing Hd on your computer go ahead and continue working in logic that error message will never show up again
On a mid 2012 Macbook this stuff unfortunately only works as a band-aid. Freezing/bouncing instrument tracks and moving project files/sound libraries to external hard drives are not permanent fixes. Once you have about 10 to 20 instrument channels, you're putting your Macbook through intense work.
I feel that! Had a MacBook I used to use as my main production computer that ran into these issues. I’d definitely recommend looking into the Mac Mini with the intel processor as I think you can get a really good bang for your buck. You can still get either an i7 or i9 with 32 to 64GB of RAM which will hold up for very large sessions! Just need to make sure you’ve got a monitor and keyboard/mouse😅 Let me know how it goes man!
As good as Logic is i can't use it. I have never had this problem with any other Daw. The rest of it is amazing but if you can't get the audio engine right what's the point!!
I'm considering Cubase or Ableton. But I am so nervous about having learn a new DAW. I've been using Logic and Garageband since 2017, but over the past 2 years Logic has been screwing up my workflow. Random crashes and glitches every day even when I bounce all of my midi instruments to audio.
Actually bro, I leave the original track while bouncing instead of muting it.......and thus it causes me CPU overload. I think muting the track as u did will save my ass.......Thanks man:)
Why does my MacBook air with M1 chip gives this message 'system overload of audio engine'' in Logic Pro x ?? On system monitor app, cpu usage seems very very low however Logic Pro audio engine sucks.
What specs does your computer have? I can’t really pin point exactly what it is in your instance, but often times computers with specs that don’t meet the requirements for music production, regardless of how much storage you have, don’t have enough processing power to run larger sessions. Hope this helps! Let me know what kind of specs you’ve got on your computer!
It could be a combination of the way you’re mixing or the amount of instrument/FX plug ins you’re using. I know for me a plug in that I use a lot that uses up CPU is Serum. A good tip would be to limit the use of FX to busses so you don’t have to use multiple different plug ins to many tracks. Also be aware how many plug ins you’re using to layer. The more instrument plug ins, the more CPU strain on your computer. Also, computer models and specs could also play a role too. Let me know if this helped!
I've done all of these things and I'm still having this problem. I increased my I/O buffer size to 1024 and set the Process Buffer Range to large. I went in and changed the KHZ to 48, turned off (forced quit) all applications in the background and I'm still having issues. I don't want to bounce my tracks in place because I don't want to commit yet; I may still want to edit. I heard freezing the tracks might help? It's essentially the same thing as bouncing the tracks except not quite a commitment. Have you done this before?
Yes freezing tracks is a good alternative if you don’t want to commit to bouncing a track! Also, something that could be using up lots of CPU could be the amount of plugins that are being used. For example, CPU usage would rise if you were to have multiple different Reverb plugins on multiple different channels. If you haven’t already, try setting up aux tracks and use busses to utilize reverb, delay, etc. (basically any effect plug ins) on multiple channels without having to use multiple different effect plug ins. I used to make this mistake a lot and now I run into system overload a lot less. Let me know if this helps and if not I can try and figure it out!
Hey did you ever fix your issue? Nothing works for me. Even with all tracks “frozen”, the second I hit play the CPU meter spikes to 100% and the CPU Overload message pops up. Losing my mind over here.
Hi. I have the playback issues on a particular Mac that I have reset to Factory. Then reloaded my students work but I continue to get the Overload message again and again. Which means I hear a second or two before the message returns. I had to give up playing the students work. I have also followed instructions from Logic (pop up) telling me to adjust the multithreading. Still continuous stopping of logic tracks. Any further ideas. I have very little open that is draining the memory! Any ideas?? Thank you.
So my first thing Id want to look at is the specs on the computer opening the project. If you’ve got a computer with weaker processing power, that could be the issue. I’d also check and make sure everything is up to date on the computer. (Operating system and Logic Pro Version) Lastly try checking with the student to see if the project itself has a lot of plug ins, automation, etc. as the session could just be demanding a lot of processing power.
Done all of that , still serious issues. Froze all tracks too, still no joy, beginning to think the sneaky update apple done without my consent has ridiculously slowed down my iMac , never had this issue before the update
This is why I'm slowly moving back to Windows PC. Macs have become enormously deceptive and unreliable over the past 5 years. It's ironic how I switched to Macs in late 2011 for video editing/audio production and was amazed how fluid the workflow was.
Make sure all other applications are closed and restart your computer. If that doesn’t work, make sure your computer is up to date and also ensure your I/O buffer size is set higher if it’s around 128 or so
Hey there! Unfortunately, only bouncing in place can be done out of the tips I gave in the video. Because garageband is an introductory DAW, a lot of features are disabled. This means you cannot change I/O buffer size or sample rate. Hope this helps!
You were great young man. my children got it and you were straight to the point. Most of the other people doing these videos and explaining are a bunch of talking heads. Good Job! I've been a teacher and professor for some 45 plus years and have produced with some of the biggest names in the business. Keep up the good work.
Thank you so much! This really means a lot 🙏🏽
The bounce in place one i didn't think about, I'll look to consider that more going forward. Good tips, man.
Thank you! Have fun producing more music!
Also the freeze button at header components when you press right click on any track, a bit annoying but helpful. Great video man
Thank you dude this helped me I didn’t realize my multiple midi tracks were overloading the program
Of course! Glad the video helped!
Wow this actually helped!! Especially the bouncing of Midi sections. Thanks my man
No problem! Glad I could help!
PR en la casaaa 🇵🇷
🇵🇷🙌🏼
Thanks for the info bro! You're the best! :)
No problem! Happy it helped you out!
If anyone is going through this I just figured out something and that is that you might have too many input devices in your computer ✌🏾
I Suggest making your beat first then just recording with one input device and if that don’t work free up some space ✌🏾
Great comment. When I’m working in pro tools I/O is one of the first things I look for! Another thing is when you’re finished making an instrumental, it’s good to export the mix and record vocals in another session to reduce CPU strain as well!
Here is how I fixed mine permanently I went to Best Buy got a 3 TB external SSD drive then opened my LOGIC folder and got all my music files out and copied them to the new SSD drive now make sure you open your files from the new SSD drive and not the existing Hd on your computer go ahead and continue working in logic that error message will never show up again
On a mid 2012 Macbook this stuff unfortunately only works as a band-aid. Freezing/bouncing instrument tracks and moving project files/sound libraries to external hard drives are not permanent fixes. Once you have about 10 to 20 instrument channels, you're putting your Macbook through intense work.
That’s 100% true! That’s why it’s important to make sure you’ve got a computer that can handle music production!
@isantiago I'm working on that. So far I have to bounce in place or freeze all of my melody tracks in order to run a decent beat production session.
I feel that! Had a MacBook I used to use as my main production computer that ran into these issues. I’d definitely recommend looking into the Mac Mini with the intel processor as I think you can get a really good bang for your buck. You can still get either an i7 or i9 with 32 to 64GB of RAM which will hold up for very large sessions! Just need to make sure you’ve got a monitor and keyboard/mouse😅 Let me know how it goes man!
@isantiago Sadly I might have to eventually give up music. My girl is prego and gotta save money for that. I only make music at night.
As good as Logic is i can't use it. I have never had this problem with any other Daw. The rest of it is amazing but if you can't get the audio engine right what's the point!!
Funny you say this cause Protools is worse for me
I'm considering Cubase or Ableton. But I am so nervous about having learn a new DAW. I've been using Logic and Garageband since 2017, but over the past 2 years Logic has been screwing up my workflow. Random crashes and glitches every day even when I bounce all of my midi instruments to audio.
the last of the tips it's the best one in my opinion
Your saving our current mix and we appreciate you lol
Happy to hear that! Glad the vid helped🙌🏼
Actually bro, I leave the original track while bouncing instead of muting it.......and thus it causes me CPU overload. I think muting the track as u did will save my ass.......Thanks man:)
Of course! Glad I could help!
thanks brother
Thanks so very much!! Immediately fixed the problem
You’re welcome! Glad the video helped!
Super helpful. Greatly appreciated!
Of course! Glad I could help out!
Why does my MacBook air with M1 chip gives this message 'system overload of audio engine'' in Logic Pro x ?? On system monitor app, cpu usage seems very very low however Logic Pro audio engine sucks.
Very cool video and explain very wall . thank you for your info
תודה רבה ...עזרת לי הרבה בטיפים שנתת ....
Thank you 🙏🏽💯
I simply opened a plugin and get the message .. Apple need to address these issues, I never have any problems with Reaper.
👍🏻 Yes, I found it helpful!
And what if you’ve already done these tricks and you have enough storage on your computer but it’s still dong this?
What specs does your computer have? I can’t really pin point exactly what it is in your instance, but often times computers with specs that don’t meet the requirements for music production, regardless of how much storage you have, don’t have enough processing power to run larger sessions. Hope this helps! Let me know what kind of specs you’ve got on your computer!
I have splice opened and brave because I do use that
thank you for this vid
No problem! Glad it helped!
Thank you!
You’re welcome!
Thanks 🙏
Big helpful
Thx nice info 👍
Literally none of this helped it still says system overload every 5 seconds!!!!
It could be a combination of the way you’re mixing or the amount of instrument/FX plug ins you’re using. I know for me a plug in that I use a lot that uses up CPU is Serum. A good tip would be to limit the use of FX to busses so you don’t have to use multiple different plug ins to many tracks. Also be aware how many plug ins you’re using to layer. The more instrument plug ins, the more CPU strain on your computer. Also, computer models and specs could also play a role too. Let me know if this helped!
@@isantiago_ does this work with vocals? It sux because i kinda need my plug ins lol
Lock your tracks to freeze the data
thanks!
Thanks:)
I've done all of these things and I'm still having this problem. I increased my I/O buffer size to 1024 and set the Process Buffer Range to large. I went in and changed the KHZ to 48, turned off (forced quit) all applications in the background and I'm still having issues. I don't want to bounce my tracks in place because I don't want to commit yet; I may still want to edit. I heard freezing the tracks might help? It's essentially the same thing as bouncing the tracks except not quite a commitment. Have you done this before?
Yes freezing tracks is a good alternative if you don’t want to commit to bouncing a track! Also, something that could be using up lots of CPU could be the amount of plugins that are being used. For example, CPU usage would rise if you were to have multiple different Reverb plugins on multiple different channels. If you haven’t already, try setting up aux tracks and use busses to utilize reverb, delay, etc. (basically any effect plug ins) on multiple channels without having to use multiple different effect plug ins. I used to make this mistake a lot and now I run into system overload a lot less. Let me know if this helps and if not I can try and figure it out!
Hey did you ever fix your issue? Nothing works for me. Even with all tracks “frozen”, the second I hit play the CPU meter spikes to 100% and the CPU Overload message pops up. Losing my mind over here.
Thanks!
You’re welcome!
But it can't work 😢bro mine is stealing
Good job bro
Thank you!
thank yoy
Hi. I have the playback issues on a particular Mac that I have reset to Factory. Then reloaded my students work but I continue to get the Overload message again and again. Which means I hear a second or two before the message returns. I had to give up playing the students work. I have also followed instructions from Logic (pop up) telling me to adjust the multithreading. Still continuous stopping of logic tracks. Any further ideas. I have very little open that is draining the memory! Any ideas?? Thank you.
So my first thing Id want to look at is the specs on the computer opening the project. If you’ve got a computer with weaker processing power, that could be the issue. I’d also check and make sure everything is up to date on the computer. (Operating system and Logic Pro Version) Lastly try checking with the student to see if the project itself has a lot of plug ins, automation, etc. as the session could just be demanding a lot of processing power.
Done all of that , still serious issues. Froze all tracks too, still no joy, beginning to think the sneaky update apple done without my consent has ridiculously slowed down my iMac , never had this issue before the update
This is why I'm slowly moving back to Windows PC. Macs have become enormously deceptive and unreliable over the past 5 years. It's ironic how I switched to Macs in late 2011 for video editing/audio production and was amazed how fluid the workflow was.
you saved me
so helpful i even subscribed..can we do business???
my Logic Pro x is not open logic pro quit unexpectedly please help me fast
Make sure all other applications are closed and restart your computer. If that doesn’t work, make sure your computer is up to date and also ensure your I/O buffer size is set higher if it’s around 128 or so
can the same be done in garageband?
Hey there! Unfortunately, only bouncing in place can be done out of the tips I gave in the video. Because garageband is an introductory DAW, a lot of features are disabled. This means you cannot change I/O buffer size or sample rate. Hope this helps!
You cursed my computer when I put it up to 192 😂😂 won’t stop glitching.
Ima fix it tho
just bouncing my vocals in place solved every issue
That’s awesome! Glad the video helped!
😎