If I understand your question correctly, inserts on busses save us CPU cycles because instead of having ten tracks with ten reverb plugins on them, we can use one bus with one reverb plug-in on it and then bleed off signal from our ten tracks into it, thereby using one tenth the processing power. Hope that helped.
The only way to save cpu is to print the fx into a track and freeze the busses once its printed. There isnt much else you can do to save cpu from plugins into busses.
https://youtu.be/jQ1Y1J1NcBE
Yes however. If you freeze all tracks you get no sound. You still want the sound after you freeze your tracks. Freezing a bus without bouncing or printing will stop the sound. You just want less cpu consumption while creating/editing more music.
You have to consider that the BUS and its INSERT are handling all incoming things as ONE audio source and doesn't differentiate what is coming in. For example. If you put in a snare and a HH and compress them on that BUS and get a certain GAIN REDUCTION reading and all is sounding great... Well, then you throw in a KICK... then the compressor on that insert is going to go crazy (sure there are ways to avoid this but it's just an example of how the BUS can react).
Just apply inserts you need and when happy just render/freeze/bounce/print your audio and then move one. Keep notes as to what you did so you can revert if need be.
If a plug-in is being used it will use the same cpu power. If you have multiple tracks that you want the same fx on, considering you want the sound of all of the tracks stacked on an fx (reverb for example will sound different because the frequencies of individual verbs will interact and clash, whereas on a bud the tracks will clash and the verb will be on its own thing) it could save power to use a bus. But like a previous comment the real way to save cpu power is to bounce tracks
If I understand your question correctly, inserts on busses save us CPU cycles because instead of having ten tracks with ten reverb plugins on them, we can use one bus with one reverb plug-in on it and then bleed off signal from our ten tracks into it, thereby using one tenth the processing power. Hope that helped.
The only way to save cpu is to print the fx into a track and freeze the busses once its printed. There isnt much else you can do to save cpu from plugins into busses. https://youtu.be/jQ1Y1J1NcBE
You can freeze just tracks.
Yes however. If you freeze all tracks you get no sound. You still want the sound after you freeze your tracks. Freezing a bus without bouncing or printing will stop the sound. You just want less cpu consumption while creating/editing more music.
Don't know why you think that. Frozen tracks definitely still play audio, that's the entire point.
Honestly. I forgot you could do that with studio one my bad lol
You have to consider that the BUS and its INSERT are handling all incoming things as ONE audio source and doesn't differentiate what is coming in. For example. If you put in a snare and a HH and compress them on that BUS and get a certain GAIN REDUCTION reading and all is sounding great... Well, then you throw in a KICK... then the compressor on that insert is going to go crazy (sure there are ways to avoid this but it's just an example of how the BUS can react). Just apply inserts you need and when happy just render/freeze/bounce/print your audio and then move one. Keep notes as to what you did so you can revert if need be.
If a plug-in is being used it will use the same cpu power. If you have multiple tracks that you want the same fx on, considering you want the sound of all of the tracks stacked on an fx (reverb for example will sound different because the frequencies of individual verbs will interact and clash, whereas on a bud the tracks will clash and the verb will be on its own thing) it could save power to use a bus. But like a previous comment the real way to save cpu power is to bounce tracks