Whoa boy this helped me immensely! Having a 4 year old Windows laptop upgraded to the gills I often have CPU load issues. The biggest single change was turning off all power saving while plugged in and also giving resource priority to my DAW while it's open. So much processing power released with a few click. Great video!
Good stuff , a huge problem that can occur is your hard drives, HDD you will run into problems the more plugins and VST’s your running through the hard drive from it as a opposed to an SSD. Especially if your running virtual instruments. M2 and ssd are definitely ideal for this, and if you can spread out what you use amongst multiple drives that will be the best option. I have an m2 and ssd and hdd and my hdd is only used for superior drummer 3 and saving my cubase projects.
Thanks for your comment Shane. Indeed, HDDs can be an absolute bottleneck, that’s why I recommend using SSDs with high read and write speed. The suggested video (End Card) talks all about it… and more! 😎🙏
There's is absolutely important gain to using higher sample rates! The amount of aliasing you'll end up with with things like saturation and compression is insane!
Using high sample rates never will make or break a mix. Concerns regarding aliasing can be addressed by using the oversampling function available in most recent saturation plugins. A good exercise can be done by comparing a session at 96kHz and one at 44.1/48kHz to see that the audible difference is negligible, if any.
One of the biggest problems with Windows 11 and modern CPU's in combination with a DAW is core parking. Disabling it will greatly improve things on many levels.
- Windows 11 - Live 11.3.13 (apparently this is supposedly fixed in later versions) My i9 13th gen overclocked to 5.43 needed all the efficiency cores to be turned off as well as all the cpu throttling options in bios - to get rid of random popping. Took me months to figure it out.
I agree with most, except 44.1 kHz. Best to work with is 48 kHz. Little more headroom. Almost no difference with CPU. But it's personal preference. There should be a list of quality low CPU (fast) plugins. Melada Production is one of them. Light and high quality. Top tier coding. Bad user interface (but they improved recently by adding graphic design). Finally. Good practice is to use one heavy plugin per channel or bus. If you need 3 heavy plugins working on one track, bust them one by one to another and use one heavy plugin per bus. So basically to create cascade. This cheats CPU to process each bus per one core/thread, basically creating parallel processing. Sometimes it helps.
Thanks for your comment Mikelo! Indeed 48kHz works as well, but it’s really about personal preference at that point. A list of high quality, low-CPU plugins is a great idea for a next video. I’ll keep it in mind! 😎🙏 For bus processing, you are correct as well! Many mixers and producers tend to overlook that and load way to many things on sub busses!
sample rate doesn't give you more headroom, bit depth does. Sample rate is about frequency range, with 48kHz you'll get less aliasing but you can get round this in 44.1 if you use oversampling which means your plugins will be processing internally at higher sample rates.
@@happyshadowthe over sampling requires a good bit of processing. It’ll be nearly the same usage. That being said my opinion doesn’t matter I work in 88.2 ;) Edit: I wonder what happens if you record at 88.2 then mix at 44.1?
@@stevewoodyt there's no point as when you down sample you have to low pass up to Nyquist to avoid those higher frequencies folding back down the spectrum causing aliasing, so you lose all that high frequency information you get with the higher sample rate anyway. I think 48 is the sweet spot unless you have a low spec computer then 44.1 is good so at least you can choose which elements of the mix you wish to use over sampling. When I record classical music I use 92, for pop music I use 44.1 as I like the freedom to use loads of plugins.
This content is filled with great ideas for people new to resource and session management. I do not completely agree with mixing at 44.1khz. I do have some plugins that run better at higher sample rates despite having to oversample. Still, you make it easily understood by suggesting a lower sample rate. Really great job here. I will be sending people to this video for useful ideas
Thanks for your comment! If you have no CPU issues and feel that it sounds better, then I’d say go for it. So many people new to the mixing world jump in the high sample rate wagon without really knowing why! Thanks again for sharing, it means a lot! 🙏😎
Great Basic Tips 👍🏾 I use Cubase Pro. And I always do these things. Throughout time I've noticed which 3rd party plugs are CPU extensive and deal with them as you've described. Vsts like Kontakt, Izotope mastering plugs, & oversampling etc., Can eat up the CPU rather quickly!
Great video. I wouldn't say dsp cards is the way to go especially if you're thinking about UAD. the chips used are 400mhz single core. That was fine in 2007, but not today. Getting an older computer that runs let's say 2500 MHz on 8 threads will give you so much more power, combine that with the free plugin audiogridder, and you can run all your favorite native plugins from the old computer via a cat cable. Bonus is you have another computer for random stuff. Been using audiogridder for 3 years now. Works great even on the same computer and not on another via cat cable, as the plugin will spread the load more efficiently across all cores and not choke on one core that usually is the bottleneck in Daws (except reaper).. You should check it out. 😊
Thanks a lot for your comment man! Yes, you are absolutely right about the SHARC chips, it’s more meant to serve as an “expansion” on an older system… probably one of the many reasons why UAD started to release native plugins. Thanks, will check out Audiogridder! 😎🙏
@@OliBeaudoinaudiogridder is a great way to avoid plugin conflicts, eg. I have a separate pc for IZotope because I noticed that having some other vendors plug-ins open with iZotope at the same time can cause one or the other to crash, solved it with audiogridder
Great info! One thing you may not know is that if you use multiple instances of the same vst instrument in Cubase it does not add much more cpu load. This may not apply to other DAWs.
Thanks for your input man! I actually didn’t know! Cubase is such a powerhouse with so many features that I keep discovering and understanding… and they are constantly adding more! 😂 Hard to keep up! 🙏
Lower sample rate increases latency. I produce at 64 bit 384 khz, latency is non existent at those levels, meaning absolute purity when i hit midi notes and internal sequencing and automation is exact. You need to learn to use the DAW's how they where designed, they have replaced tape machines, before DAW's you had a 24 track tape machine. You print to tape, so today you have to print to DAW. Meaning get your s**t sorted out, print then freeze all the garbage vsts hogging that channel. Leaving 500 plugins open, and midi devices constantly playing is not a logical way to work. Commit > print > freeze > move on.
Absolutely Jason! This video is meant to remind those simple things we tend to forget! Printing as we go may be one of the best tips to stay light and efficient! 🙏
Great question. The short answer is no, but with a caveat. Using a higher sample rate doesn’t directly affect latency, but does increase CPU usage for each plugin loaded, so in terms, it can affect latency if your system is already struggling with the DSP load. Adjusting to a higher buffer size should be #1 priority. The second would be to remove some plugins in your sessions that may be adding additional latency, such as linear phase EQs, etc. For example, if you have Fabfilter Pro-Q3 and change from zero latency mode, to linear phase mode, you’ll see a pretty drastic change in latency. Hope that helps! 🙏
Yuo! that's what I have to do lately in LOGIC ...just as you said but still I'm waiting for the new Mac STUDIO to come out. ( i'm running a Late 2017 iMac i5...not good : )
DAWs with a lighter footprint such as Reaper can be a good option, you are 100% right. A lot of mixers may not be willing to learn a new workflow, key commands, etc., that’s why they usually stick with the same DAW.
Watch this next to Optimize your MAC for MUSIC PRODUCTION: ruclips.net/video/b6crH3wXYqw/видео.html
Whoa boy this helped me immensely! Having a 4 year old Windows laptop upgraded to the gills I often have CPU load issues. The biggest single change was turning off all power saving while plugged in and also giving resource priority to my DAW while it's open. So much processing power released with a few click. Great video!
Thanks AJ! Glad it helped! 😎🙏
Good stuff , a huge problem that can occur is your hard drives, HDD you will run into problems the more plugins and VST’s your running through the hard drive from it as a opposed to an SSD. Especially if your running virtual instruments. M2 and ssd are definitely ideal for this, and if you can spread out what you use amongst multiple drives that will be the best option. I have an m2 and ssd and hdd and my hdd is only used for superior drummer 3 and saving my cubase projects.
Thanks for your comment Shane. Indeed, HDDs can be an absolute bottleneck, that’s why I recommend using SSDs with high read and write speed. The suggested video (End Card) talks all about it… and more! 😎🙏
There's is absolutely important gain to using higher sample rates! The amount of aliasing you'll end up with with things like saturation and compression is insane!
Using high sample rates never will make or break a mix. Concerns regarding aliasing can be addressed by using the oversampling function available in most recent saturation plugins. A good exercise can be done by comparing a session at 96kHz and one at 44.1/48kHz to see that the audible difference is negligible, if any.
One of the biggest problems with Windows 11 and modern CPU's in combination with a DAW is core parking. Disabling it will greatly improve things on many levels.
Thanks for chiming in Frank. Great tip to know for PC users!
- Windows 11
- Live 11.3.13 (apparently this is supposedly fixed in later versions)
My i9 13th gen overclocked to 5.43 needed all the efficiency cores to be turned off as well as all the cpu throttling options in bios - to get rid of random popping.
Took me months to figure it out.
@@ghfjfghjasdfasdfYeah, the pops and clicks only get worse on newer cpu's because of all the power saving crap built in Windows by default.
@franckinthestudio Indeed! It’s usually best to disable power saving functions for audio production.
@@OliBeaudoinExactly!
I agree with most, except 44.1 kHz. Best to work with is 48 kHz. Little more headroom. Almost no difference with CPU. But it's personal preference.
There should be a list of quality low CPU (fast) plugins. Melada Production is one of them. Light and high quality. Top tier coding. Bad user interface (but they improved recently by adding graphic design).
Finally. Good practice is to use one heavy plugin per channel or bus. If you need 3 heavy plugins working on one track, bust them one by one to another and use one heavy plugin per bus. So basically to create cascade. This cheats CPU to process each bus per one core/thread, basically creating parallel processing. Sometimes it helps.
Thanks for your comment Mikelo! Indeed 48kHz works as well, but it’s really about personal preference at that point.
A list of high quality, low-CPU plugins is a great idea for a next video. I’ll keep it in mind! 😎🙏
For bus processing, you are correct as well! Many mixers and producers tend to overlook that and load way to many things on sub busses!
I was thinking the same. Alot of plug-ins also work best with 48 kHz.
sample rate doesn't give you more headroom, bit depth does. Sample rate is about frequency range, with 48kHz you'll get less aliasing but you can get round this in 44.1 if you use oversampling which means your plugins will be processing internally at higher sample rates.
@@happyshadowthe over sampling requires a good bit of processing. It’ll be nearly the same usage. That being said my opinion doesn’t matter I work in 88.2 ;)
Edit: I wonder what happens if you record at 88.2 then mix at 44.1?
@@stevewoodyt there's no point as when you down sample you have to low pass up to Nyquist to avoid those higher frequencies folding back down the spectrum causing aliasing, so you lose all that high frequency information you get with the higher sample rate anyway. I think 48 is the sweet spot unless you have a low spec computer then 44.1 is good so at least you can choose which elements of the mix you wish to use over sampling. When I record classical music I use 92, for pop music I use 44.1 as I like the freedom to use loads of plugins.
This content is filled with great ideas for people new to resource and session management. I do not completely agree with mixing at 44.1khz. I do have some plugins that run better at higher sample rates despite having to oversample. Still, you make it easily understood by suggesting a lower sample rate. Really great job here. I will be sending people to this video for useful ideas
Thanks for your comment! If you have no CPU issues and feel that it sounds better, then I’d say go for it. So many people new to the mixing world jump in the high sample rate wagon without really knowing why! Thanks again for sharing, it means a lot! 🙏😎
Great Basic Tips 👍🏾 I use Cubase Pro. And I always do these things. Throughout time I've noticed which 3rd party plugs are CPU extensive and deal with them as you've described.
Vsts like Kontakt, Izotope mastering plugs, & oversampling etc., Can eat up the CPU rather quickly!
Thanks a lot! Yes, Cubase is a powerhouse with so many features and plugins that most people overlook or don’t know about!
Great video. I wouldn't say dsp cards is the way to go especially if you're thinking about UAD. the chips used are 400mhz single core. That was fine in 2007, but not today. Getting an older computer that runs let's say 2500 MHz on 8 threads will give you so much more power, combine that with the free plugin audiogridder, and you can run all your favorite native plugins from the old computer via a cat cable. Bonus is you have another computer for random stuff. Been using audiogridder for 3 years now. Works great even on the same computer and not on another via cat cable, as the plugin will spread the load more efficiently across all cores and not choke on one core that usually is the bottleneck in Daws (except reaper)..
You should check it out. 😊
Thanks a lot for your comment man! Yes, you are absolutely right about the SHARC chips, it’s more meant to serve as an “expansion” on an older system… probably one of the many reasons why UAD started to release native plugins. Thanks, will check out Audiogridder! 😎🙏
@@OliBeaudoinaudiogridder is a great way to avoid plugin conflicts, eg. I have a separate pc for IZotope because I noticed that having some other vendors plug-ins open with iZotope at the same time can cause one or the other to crash, solved it with audiogridder
Thanks for the tip!
Great info! One thing you may not know is that if you use multiple instances of the same vst instrument in Cubase it does not add much more cpu load. This may not apply to other DAWs.
Thanks for your input man! I actually didn’t know! Cubase is such a powerhouse with so many features that I keep discovering and understanding… and they are constantly adding more! 😂 Hard to keep up! 🙏
Very good Oli. Thank you very much, very useful and relevant to me at the moment. Go well ok
Thanks so much Rob. Glad it helped 🙏
Excellent 👌
Thank Frank! Cheers!
Buffer 1024 tabarnak!
🤣
Very true
🙏
love your channel
Thank you so much! Let me know if you have any questions you’d like to be answered! 🎚️🎛️🎵
Lower sample rate increases latency.
I produce at 64 bit 384 khz, latency is non existent at those levels, meaning absolute purity when i hit midi notes and internal sequencing and automation is exact.
You need to learn to use the DAW's how they where designed, they have replaced tape machines, before DAW's you had a 24 track tape machine.
You print to tape, so today you have to print to DAW.
Meaning get your s**t sorted out, print then freeze all the garbage vsts hogging that channel.
Leaving 500 plugins open, and midi devices constantly playing is not a logical way to work.
Commit > print > freeze > move on.
Absolutely Jason! This video is meant to remind those simple things we tend to forget! Printing as we go may be one of the best tips to stay light and efficient! 🙏
So that means lower sample rate “decreases” latency then correct?
Great question. The short answer is no, but with a caveat. Using a higher sample rate doesn’t directly affect latency, but does increase CPU usage for each plugin loaded, so in terms, it can affect latency if your system is already struggling with the DSP load. Adjusting to a higher buffer size should be #1 priority. The second would be to remove some plugins in your sessions that may be adding additional latency, such as linear phase EQs, etc. For example, if you have Fabfilter Pro-Q3 and change from zero latency mode, to linear phase mode, you’ll see a pretty drastic change in latency.
Hope that helps! 🙏
Yuo! that's what I have to do lately in LOGIC ...just as you said but still I'm waiting for the new Mac STUDIO to come out. ( i'm running a Late 2017 iMac i5...not good : )
Those new mac studio look good. Hopefully it will last you as long as your i5! 🙏
Hmmm ! Quebec ?
Oui! 🙏😎
l'accent Québecois all the way!
Can’t hide it 😂
@@OliBeaudoin Moi aussi j’en ai un lol
🤣🙏
The best thing against cpu overload is the use Reaper.
DAWs with a lighter footprint such as Reaper can be a good option, you are 100% right. A lot of mixers may not be willing to learn a new workflow, key commands, etc., that’s why they usually stick with the same DAW.
❤
❤️
Waves Abbey road reverbs😂...you know what talking about
Absolutely! 😂
I disagree with the 44.1 statement. 48k will help cramping.
Both are great options!
not going to select the highest buffer size that’s not my issue
It’s usually the first thing to address before going deeper into other potential issues
Please do not do this set the session to 48khz
Why?
@@OliBeaudoin The guy below just told you why sir headroom
These are all lies
🤣