Thanks for those suggestions! Also, when a midi track is selected during playback, Logic is typing up resources for the "just in case" you need them for that track during playback. Away to reduce cpu load further is to add a blank audio track and simply have it selected during playback and the cpu meters will drop even further. Sometimes pretty dramatically. Also, Logic will share the session load across multiple processing threads but it still does not have the ability to split the plugin load of a track across multiple threads. This means that if you have a stack of heavy cpu plugins on a track, your session could have one of those processing threads max out and stop the session playback due to cpu overload. If that happens, you will need to move those plugins to aux tracks and bus the track signal to them instead so the cpu load can be shared across the main and aux tracks instead.
One solution makes more difference….. One empty audio track and select that when starting play no more heavy spike on one core. Problems solved. While playing you can leave the empty track of course.
Dude the freezing thing helped so much. My newer computer gives me the Overload message so easily and I always resorted to having to bounce in place and delete original track and just hope to god I wouldn’t want to make any more changes…. This is so easy :D
Hi George, @@knuckledustermusic I have an album coming out and perhaps you'd be interested in helping me take it to a higher level. It" s in logic. I have a studio with good gear. Theme is: the current Ukrainian war. btw. I sing as well... I know it will cost $.
Great tips! Thank you! I prefer bounce in place to freezing tracks, though. When I freeze tracks, I tend to get this weird popping noise when I start the tracks from the beginning. Also, it's annoying to have to wait for Logic to freeze and unfreeze stuff while I'm working. I prefer to bounce the tracks in place, and then if I need to make changes I can just unmute the original track, make the changes, and re-bounce it. PS - I love your logo! It's a fist made of piano keys. Awesome!
(Regarding the situation at 1:25) The "custom" bar doesn't apply the same in this video as it does for other people. The custom bar is your own personalized / customized LCD display panel i.e. not everyone has customized it to display performance meter. Click on the arrow as demonstrated in the video, then instead of clicking on "custom" go to the "customize control bar and display..." located a few rows below the custom option. Here you have on/off boxes for multiple display settings. In the last row of the third column you can check the "performance meter CPU/HD" and select "save as default". Your custom bar is now displaying the performance meter as it is in the video.
Good point! For anyone who's interested I go over the Custom Menu bar in more detail here: ruclips.net/video/fvODFTf31Ko/видео.htmlsi=w36nzmumdQNtnanc&t=316 Cheers Georges
You’re welcome! Let me know if there’s anything I can help with. You’ll find a similar learning curve with all DAWs, but once you’ve spent a bit of time with it I’m sure you’ll be glad you stayed with Logic Pro. Cheers Georges
You're welcome! Bounce in place is still a thing. Freezing tracks does the same thing except that the track freeze is quickly reversible. That way you can make changes if needed. Cheers Georges
I prefer bounce in place and hiding/muting the the plugin or instrumental track in case the instrument is incompatible for some strange reason....last time my battery plugin was only doing stereo and everything mono would be automatically removed. meaning I'd have to remember the name of the sample used and reload it in every session.
I just found something: if you have midi tracks in your projects - right click on the track and select bounce in place (once you’re done creating all midi events and are happy with it), that converts the midi to wav and it seems to have solved my issues!
I prefer bounce in place and hiding/muting the the plugin or instrumental track in case the instrument is incompatible for some strange reason....last time my battery plugin was only doing stereo and everything mono would be automatically removed. meaning I'd have to remember the name of the sample used and reload it in every session.
You're welcome. It's essentially the same thing. The advantage of freezing is that you can quickly unfreeze and make any changes and then re-freeze your track. This is especially useful for software instruments. I hope that makes sense. Cheers Georges
i had no idea the cpu meter popped out, dang lol. do you ever use low latency mode? i'm on a macbook and it's been very useful when i am doing e drums or i have a huge file.
How about advice for those using real instruments either miced or plugged directly into the computer, in combination with the digital instruments logic offers?
The same tips apply. You'll just need to manage your I/O buffer size so that you don't have too much latency when recording though (low latency mode will help too). Freezing software instruments and audio tracks with lots of plugins is the ticket. Cheers Georges
Thanks George. I’ve had mixed results with freezing tracks. I’ve also read that freezing tracks isn’t always the best option. One option that I’ve adopted that seems to work pretty well is to set each track’s “input” to zero or no input when you aren’t recording in a particular track.
hi Georges, thanks for sharing. please help, i got notify while i'm playing my midi drum on logic pro. : " Error while trying to synchronize Audio and MIDI. Sample rate 41.307 recognized."
Thanks! You can quickly freeze and unfreeze individual tracks as you're working on them, but ya you'll have to wait a little bit each time for the tracks to freeze. Cheers Georges
If you've done all this, closed all other applications, and made sure to have free space on your hard drive, then I'm sorry to say it might be time to look at a faster mac.
Holy crap. I just started messing around with the Logic 11 session bass, and keyboard plugins and they are seriously overloading my system. What the hell? None of my third party plugins do that.. but as soon as I load up the logic bass bass, it's destroying me. I'm on an M1 too .. totally optimized. Changing my buffer and playback does nothing.
@@knuckledustermusic Narrowed it down. It's not any of Logic's instruments. It's this Neural dsp amp emulator I'm using. I can't believe what a resource hog this thing is. It's like you have to bounce everything down to even use more than one instance of it. As much hype is out there for Neural dsp .. I can't believe more people aren't complaining about this.
Great job Apple, your hardware, your OS and App and issues like this... brilliant... after all the years with advances in technology... this should not be an issue.... Microsoft is not much better... the results of corporate greed...
Are intel macs at a noticeable disadvantage compared to m2 macs? I noticed apple saying that logic would be optimized for m2, and I didn’t have any speed or latency issues until recently after the optimized logic for m2
For now I would say you're fine with an Intel mac. Both my macs are currently Intel. The issue going forward will be that they'll slowly stop being supported. Cheers Georges
More ram will help if you have alot of software instruments loaded. It will help with disk speed issues. A faster CPU and more cores will be helpful if you have lots of plugin fx loaded on each of your tracks. Think of ram as allowing you to have more things open or loaded, and CPU speed controlling how fast you can operate them. I hope that helps. Cheers Georges
I listened to this video some months ago, and it solved my issues for quite some time, but now even with my settings maxed, I seem to be getting the same message again, more and more frequently. I admit, my Mac is quite old, and I now use it only for music, but have lots of storage used from music already- and for the processing threads, I only have 4, not 16- are these considerations alone, enough to slow down my Mac this much? I have buffer size to 1024 and range to large, threads to automatic or 4 (only have 4). The message used to only appear on big projects with lots of tracks, audio, midi, etc., but now even when I’m in a new project with 4-6 tracks, and little to no plugins, my computer struggles to play. Do I just need a new computer, or more processing threads / better hardware? I have a Macbook Pro 12 with Intel Core i5 processor, 8gb memory.
If you were having success before, then it could just be that you need to clear some space on your hard drive. If you're running out of space, it'll slow things down for you and give you these messages. Cheers Georges
Great advice,but on my older iMac the processing threads option is just 2,4 automatic only,why is this and does it actually make a difference to my System Overload problem?
You should set it to 4 (the highest number possible). If it's set to 2, you'll be limiting the processing power that Logic Pro has access to. Selecting a larger I/O buffer size will make the biggest difference. Cheers Georges
Hi Georges I am new using Logic Pro X I am using Kontakt 7 in the track when I add the freezer bottom not show in the track if I add an audio track it show?. Thank you for your videos and support I have subscribed.
is there a way I set 1024 buffer size and go recording with autotune without an delay in it? You know what I mean. I learned till yet, that I have to set it to the smallest amount, like 32, to record with plugins and without a delay, but is it really the only one way?
It worked great for years, but suddenly I can no longer record when the buffer size is small.. and I don't know what I changed or where exactly the error is
Your best bet is to record in Low Latency Mode (Go to the menu Record->Low Latency Monitoring Mode) and then start reducing the buffer size as much as you can without getting the System Overload message. Cheers Georges
What is the difference between the on/off tracks and freeze tracks? When I turn tracks off from Logic says it helps with resources, but the plugins are still on in the rack, so I’m not sure.
on/off will mute your track and disable the plugins (you'll notice the plugins are shaded). Freezing tracks will basically bounce a track in place. Meaning it'll convert everything to audio, so all the plugins and/or software instrument will be bounced into an audio file which is easier for your computer to playback. Cheers Georges
Thanks for replying, George. However, I have since learned that turning off a track does not shade or disable plugins, it simply turns off the track in the arrange view. At least in my experiments. I’m not sure what causes the “shaded” plugins, unless it is low latency mode. I’m with you on freezing tracks to save cpu resources, though.
@@joelremiel if you turn off a plugin itself it'll appear grey and will be disabled. When you first open a project, you may notice that some plugins are blue with white lettering (active plugins) and some are blue with grey lettering (inactive). The ones with grey lettering are usually found on blank or muted tracks and the plugins will remain inactive until there is audio or midi being played through them. That way Logic Pro can save processing resources until it's needed. The on/off switch for tracks does the same thing. I hope that makes sense. Cheers Georges
Make sure you set your Processing Threads to the maximum available in the Preferences/Settings. Freezing your tracks will help a lot if you are limited to 4 threads. Cheers Georges
►► Download my free Logic Pro Hotkey Cheatsheet at → www.knuckledustermusic.com/lpxhotkey
Thanks for those suggestions! Also, when a midi track is selected during playback, Logic is typing up resources for the "just in case" you need them for that track during playback. Away to reduce cpu load further is to add a blank audio track and simply have it selected during playback and the cpu meters will drop even further. Sometimes pretty dramatically. Also, Logic will share the session load across multiple processing threads but it still does not have the ability to split the plugin load of a track across multiple threads. This means that if you have a stack of heavy cpu plugins on a track, your session could have one of those processing threads max out and stop the session playback due to cpu overload. If that happens, you will need to move those plugins to aux tracks and bus the track signal to them instead so the cpu load can be shared across the main and aux tracks instead.
You're welcome and thanks for the comment and extra tips!
Cheers
Georges
This video has solved (vastly improved) my frustrating older Mac speed problems. Thanks a million.
Happy to hear it! You're welcome!
watch the video in 1.5 speed setting
No
Thank you ahah, most videos I speed up helps with concentration
😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂
Thanks bro
Lmao
One solution makes more difference….. One empty audio track and select that when starting play no more heavy spike on one core. Problems solved. While playing you can leave the empty track of course.
Why is that?
@@trceb Because selecting another track would result in one core spiking. Try and see the massive difference.
Best way to prevent CPU spikes while playing is to add an empty audio track or click on an existing audio track and then play the project.
OMG half way through this vid and you've already solved my issues! You the man!
Happy to hear it!
Cheers
Georges
Thanks so much…I’ve had this problem for years. Finally got it figured out.
I'm glad you got it solved! Happy to help!
Cheers
Georges
Dude the freezing thing helped so much. My newer computer gives me the Overload message so easily and I always resorted to having to bounce in place and delete original track and just hope to god I wouldn’t want to make any more changes…. This is so easy :D
Glad to hear it's working for you!
Cheers
Georges
Informative and straightforward!
Thank you 🙌
@@prod.heyBlicky you’re welcome!
hey, I used to study Logic with you at Vancouver Community College 2018. You're a really cool teacher and like the Doors. Thanks for everything!
Hey thanks James! Glad to see you here.
Cheers
Georges
Hi George, @@knuckledustermusic I have an album coming out and perhaps you'd be interested in helping me take it to a higher level. It" s in logic. I have a studio with good gear. Theme is: the current Ukrainian war. btw. I sing as well... I know it will cost $.
@@jamesewanchook2276 Hey James, shoot me a message and we can chat: www.knuckledustermusic.com/site/contact
Cheers
Georges
Great tips! Thank you! I prefer bounce in place to freezing tracks, though. When I freeze tracks, I tend to get this weird popping noise when I start the tracks from the beginning. Also, it's annoying to have to wait for Logic to freeze and unfreeze stuff while I'm working. I prefer to bounce the tracks in place, and then if I need to make changes I can just unmute the original track, make the changes, and re-bounce it. PS - I love your logo! It's a fist made of piano keys. Awesome!
(Regarding the situation at 1:25)
The "custom" bar doesn't apply the same in this video as it does for other people. The custom bar is your own personalized / customized LCD display panel i.e. not everyone has customized it to display performance meter.
Click on the arrow as demonstrated in the video, then instead of clicking on "custom" go to the "customize control bar and display..." located a few rows below the custom option. Here you have on/off boxes for multiple display settings. In the last row of the third column you can check the "performance meter CPU/HD" and select "save as default". Your custom bar is now displaying the performance meter as it is in the video.
Good point! For anyone who's interested I go over the Custom Menu bar in more detail here: ruclips.net/video/fvODFTf31Ko/видео.htmlsi=w36nzmumdQNtnanc&t=316
Cheers
Georges
Thank you very much changing the buffer settings and freezing the software tracks did the job
You're welcome! Glad to hear it!
Cheers
Georges
George, thank you for your clear and to the point video. #appreciated!
You're very welcome!
Thanks to the knowledge you shared, I was able to solve my problem very effectively.. Thank you very much.
You’re most welcome. Glad you got it sorted!
Cheers
Georges
Excellent solutions to common problems with multitrack sessions. Thanks for sharing preferences settings that help solving many problems.
You're welcome! Happy to hear it helped!
Cheers
Georges
Finally my dreaded system overload is gone! Thank you so much for your step by step guide. 10 stars ✨
Glad to hear it! You're welcome!
I’m at work but I’m sure this is going to work when I get home very straightforward video good stuff
Thanks!
Great video, bro literally has the cheat codes
Thank you!
Thanks George. I like your videos! Sometimes Logic just frustrates me so much that I want to change DAW's. I'm still hangin on though.
You’re welcome! Let me know if there’s anything I can help with. You’ll find a similar learning curve with all DAWs, but once you’ve spent a bit of time with it I’m sure you’ll be glad you stayed with Logic Pro.
Cheers
Georges
Thank you. Excellent channel! Anyone else having this problem since Native Access updated Kontakt to 7.6.1?
You're welcome. I haven't updated Kontakt yet, so nothing to report from me.
Thanks for your wonderful video, I will be giving these a go very soon.
You’re welcome! Good luck!
Cheers
Georges
Thank you so much bro 🙏🏼🙏🏼🙏🏼
@@Mr.White369 you’re welcome!
brother, this is so helpful, helping learn more about Logic, ty!
You're welcome!
More useful than most Logic videos. thanks. This used to be called "bounce in place" right?
You're welcome! Bounce in place is still a thing. Freezing tracks does the same thing except that the track freeze is quickly reversible. That way you can make changes if needed.
Cheers
Georges
Cool, I learned something.@@knuckledustermusic
I prefer bounce in place and hiding/muting the the plugin or instrumental track in case the instrument is incompatible for some strange reason....last time my battery plugin was only doing stereo and everything mono would be automatically removed. meaning I'd have to remember the name of the sample used and reload it in every session.
This was very helpful. Thanks !
You're welcome!
Thank u . Saved me alot
You're welcome!
Thank you man! Great tips. I learned about the threads option.
You're most welcome!
Cheers
Georges
Well done on a great channel , thank you !
You’re welcome and thanks for the support!
Cheers
Georges
Nice video, 📹 simple and very informative.
Glad you liked it!
Thanks for the suggestions
You're welcome!
this was fixed welldone George very helpful 😁😁😁😁😁😁 thanks a lot freezing is the answer
You're welcome!
Good information, thank you!
You're welcome!
Thank you for your advice now I got it figured out. I subscribe your channel now. 👍
Thanks for the support!
Appreciate it, George!✨
You're welcome!
Excellent info! Thank you for this!
You're welcome!
Just a query, when you go into the processing threads my highest value is 8, whilst your 16 why that? and thank you
It's just that your CPU has less threads available. A MacBook Air for example will have less threads than a MacBook Pro.
Cheers
Georges
Hi George. This video was very informative and helpful. Thank you very much. 🙂
You're welcome Brian!
I learned a lot in this video, thanks 🙏
You're welcome! Happy to hear it!
Cheers
Georges
Thanks a lot for that! real valuable video!
Glad it was helpful!
Thanks George. A good, concise, helpful video…Brillant content. Thanks for helping so much
You're very welcome!
Thank you my friend, this was heaven sent 🙏🏽
You're very welcome
Great tutorial! Huge help
Thanks! Glad to hear it!
Thank you for your help！
You're welcome!
Thank you, this was a big help.
You're very welcome!
hey.... great help!! Thanks!
You’re welcome!
Thanks for the info.
You’re welcome!
Great help George thank you so much
You're welcome!
Sweet! Thanks!
You're welcome!
Thank you
You're welcome!
also some 3rd party plugins will spike the threads ,even on a mac studio , right now spaced out by Baby audio is a spiky one
For sure there are some CPU hungry plugins out there! Freezing those tracks will help.
Cheers
Georges
Very helpful - thanks 👍🏻
You're welcome!
thx bro
freezing track help a lot, cya.
Happy to help!
Thank you!
You're very welcome!
Thanks George!
You're welcome!
thank you
You're welcome!
Sir whenever I open my vst's there's always a detuning problem
so can you please help me regarding this
Thanks! Your help is much appreciated : )
You're welcome!
Thank youu!!!
You're welcome!
None of this worked 😭😭😭
Yeah… same here and I upgraded from 4 to 8 GB RAM, too..
I just found something: if you have midi tracks in your projects - right click on the track and select bounce in place (once you’re done creating all midi events and are happy with it), that converts the midi to wav and it seems to have solved my issues!
@@SixStringJoy I was able to figure it out as well. I just stack my tracks and it fixes the issue
Excellent tutorial and much thanks.
You're welcome!
Thank you, good sir!
You're welcome!
Nice one man, Thanks!
You're welcome!
Thanks bro!
You're welcome!
I prefer bounce in place and hiding/muting the the plugin or instrumental track in case the instrument is incompatible for some strange reason....last time my battery plugin was only doing stereo and everything mono would be automatically removed. meaning I'd have to remember the name of the sample used and reload it in every session.
Ya freezing doesn't always work flawlessly with multi-output software instruments.
Thank you bro.
You're welcome!
Thank you sooo much for the tips! How does freezing differ from bouncing to audio?
You're welcome. It's essentially the same thing. The advantage of freezing is that you can quickly unfreeze and make any changes and then re-freeze your track. This is especially useful for software instruments.
I hope that makes sense.
Cheers
Georges
yessss
Thanks for a great video! I have entered my sixth decade in this life and need to be tutored in the senior tempo!
You're welcome! Let me know if there's any other topics you'd like to see covered.
Cheers
Georges
i had no idea the cpu meter popped out, dang lol. do you ever use low latency mode? i'm on a macbook and it's been very useful when i am doing e drums or i have a huge file.
Yes I use low latency mode all the time! Pretty much any time I'm recording audio or midi.
Cheers
Georges
How about advice for those using real instruments either miced or plugged directly into the computer, in combination with the digital instruments logic offers?
The same tips apply. You'll just need to manage your I/O buffer size so that you don't have too much latency when recording though (low latency mode will help too). Freezing software instruments and audio tracks with lots of plugins is the ticket.
Cheers
Georges
Thanks George. I’ve had mixed results with freezing tracks. I’ve also read that freezing tracks isn’t always the best option. One option that I’ve adopted that seems to work pretty well is to set each track’s “input” to zero or no input when you aren’t recording in a particular track.
Thanks friend u just help me God Bless
You're most welcome!
hi Georges, thanks for sharing. please help, i got notify while i'm playing my midi drum on logic pro. :
" Error while trying to synchronize Audio and MIDI. Sample rate 41.307 recognized."
Usually a system reboot will solve this issue. I hope that helps.
Cheers
Georges
Great ideas. Still having issues (can't freeze since I'm creating the track and don't have the full song done yet). :(
Thanks! You can quickly freeze and unfreeze individual tracks as you're working on them, but ya you'll have to wait a little bit each time for the tracks to freeze.
Cheers
Georges
Yeah. Thank you too!@@knuckledustermusic
What do I do if I do all of this still and my system is still overloading 😢
If you've done all this, closed all other applications, and made sure to have free space on your hard drive, then I'm sorry to say it might be time to look at a faster mac.
Holy crap. I just started messing around with the Logic 11 session bass, and keyboard plugins and they are seriously overloading my system. What the hell? None of my third party plugins do that.. but as soon as I load up the logic bass bass, it's destroying me. I'm on an M1 too .. totally optimized. Changing my buffer and playback does nothing.
That's a bummer. All I can suggest is to freeze as many tracks as you can (and close any other applications other than Logic Pro).
@@knuckledustermusic Narrowed it down. It's not any of Logic's instruments. It's this Neural dsp amp emulator I'm using. I can't believe what a resource hog this thing is. It's like you have to bounce everything down to even use more than one instance of it. As much hype is out there for Neural dsp .. I can't believe more people aren't complaining about this.
Great job Apple, your hardware, your OS and App and issues like this... brilliant... after all the years with advances in technology... this should not be an issue.... Microsoft is not much better... the results of corporate greed...
Are intel macs at a noticeable disadvantage compared to m2 macs? I noticed apple saying that logic would be optimized for m2, and I didn’t have any speed or latency issues until recently after the optimized logic for m2
For now I would say you're fine with an Intel mac. Both my macs are currently Intel. The issue going forward will be that they'll slowly stop being supported.
Cheers
Georges
Is it the interface or the MacBook with the issue ?
If you're getting these messages it usually means your MacBook can't keep up (not your interface).
Cheers
Georges
Is this issue related to RAM or something else? I'm no expert on computers so just wondering if doubling my RAM is going to help with this?
More ram will help if you have alot of software instruments loaded. It will help with disk speed issues. A faster CPU and more cores will be helpful if you have lots of plugin fx loaded on each of your tracks.
Think of ram as allowing you to have more things open or loaded, and CPU speed controlling how fast you can operate them.
I hope that helps.
Cheers
Georges
@@knuckledustermusic Thankyou. I’ll go ahead and order some more then. Can’t really do much about the other stuff.
im getting sample rate issues when im at the max processing threads, when i go to only 2 it works. Anyone know why?
How many threads is your max?
I listened to this video some months ago, and it solved my issues for quite some time, but now even with my settings maxed, I seem to be getting the same message again, more and more frequently.
I admit, my Mac is quite old, and I now use it only for music, but have lots of storage used from music already- and for the processing threads, I only have 4, not 16- are these considerations alone, enough to slow down my Mac this much?
I have buffer size to 1024 and range to large, threads to automatic or 4 (only have 4). The message used to only appear on big projects with lots of tracks, audio, midi, etc., but now even when I’m in a new project with 4-6 tracks, and little to no plugins, my computer struggles to play.
Do I just need a new computer, or more processing threads / better hardware? I have a Macbook Pro 12 with Intel Core i5 processor, 8gb memory.
If you were having success before, then it could just be that you need to clear some space on your hard drive. If you're running out of space, it'll slow things down for you and give you these messages.
Cheers
Georges
no problems ever until i tried waves plugins, disk overload even after uninstall. any suggestions please. -music by PREXENTS #prexents
Great advice,but on my older iMac the processing threads option is just 2,4 automatic only,why is this and does it actually make a difference to my System Overload problem?
You should set it to 4 (the highest number possible). If it's set to 2, you'll be limiting the processing power that Logic Pro has access to. Selecting a larger I/O buffer size will make the biggest difference.
Cheers
Georges
@@knuckledustermusic Thank you 👍
You're welcome!@@dirtysolarremix
Hi Georges I am new using Logic Pro X I am using Kontakt 7 in the track when I add the freezer bottom not show in the track if I add an audio track it show?. Thank you for your videos and support I have subscribed.
Hi, try creating your Kontakt track as a Stereo track instead of a Multi-Output track.
I hope that helps.
Cheers
Georges
Hi Georges not didn't`t work. Thank you very much
is there a way I set 1024 buffer size and go recording with autotune without an delay in it? You know what I mean. I learned till yet, that I have to set it to the smallest amount, like 32, to record with plugins and without a delay, but is it really the only one way?
It worked great for years, but suddenly I can no longer record when the buffer size is small.. and I don't know what I changed or where exactly the error is
Your best bet is to record in Low Latency Mode (Go to the menu Record->Low Latency Monitoring Mode) and then start reducing the buffer size as much as you can without getting the System Overload message.
Cheers
Georges
@@knuckledustermusic thanks Georges!! Greetings from Germany
What is the difference between the on/off tracks and freeze tracks? When I turn tracks off from Logic says it helps with resources, but the plugins are still on in the rack, so I’m not sure.
on/off will mute your track and disable the plugins (you'll notice the plugins are shaded). Freezing tracks will basically bounce a track in place. Meaning it'll convert everything to audio, so all the plugins and/or software instrument will be bounced into an audio file which is easier for your computer to playback.
Cheers
Georges
Thanks for replying, George. However, I have since learned that turning off a track does not shade or disable plugins, it simply turns off the track in the arrange view. At least in my experiments. I’m not sure what causes the “shaded” plugins, unless it is low latency mode. I’m with you on freezing tracks to save cpu resources, though.
@@joelremiel if you turn off a plugin itself it'll appear grey and will be disabled. When you first open a project, you may notice that some plugins are blue with white lettering (active plugins) and some are blue with grey lettering (inactive). The ones with grey lettering are usually found on blank or muted tracks and the plugins will remain inactive until there is audio or midi being played through them. That way Logic Pro can save processing resources until it's needed. The on/off switch for tracks does the same thing. I hope that makes sense.
Cheers
Georges
Yes, it does make sense.
What if I only have 4 threads
Make sure you set your Processing Threads to the maximum available in the Preferences/Settings. Freezing your tracks will help a lot if you are limited to 4 threads.
Cheers
Georges
👍
🤘🤘
Sounds like swedish pop
Is that good or bad? 🤣
@@knuckledustermusic thats very good 👌😍
None of this worked. I’m sick to FUCKING death of getting system overload ever nanosecond. Logic and Apple absolutely suck.
This guy’s lying for views .. this DID NOT work !!!!
Thank you
You're welcome!