I often use the montage to compare plugin chains, as part of the Mastering Process.
This means that I will have chains of several plugins on each track, so I can jump (solo) between them for comparison. But this often means that my CPU struggles to play the single tracks without hiccups, even though I only listen to them one track at a time.
So I wonder if it’s possible to stop the processing for the tracks that are muted, to free up CPU ressources in Wavelab?
::
Mads
Thanks for answering. Process with Multible Cores helped overall. But I still wonder why a track below (Track 3) with no plugin processing, still is more or less, as CPU hungry (as Track 2).
Maybe your OCELOT Limiter is the bottleneck. Remove it to see if it makes a difference.
Also, are you sure there is no plugin in the output section?
No there’s nothing on the output. I removed Ocelot (even if it was bypassed). But that didn’t help either.
I understand it’s a suprise for you too..?
The scroll bar shows that there are many more tracks than what you currently display in your pictures. What are they?
They are different leftovers from the same project.
To make sure they are not disturbing anything, I have removed them now and saved the Audio Montage as a new name. Using four tracks all in all. Three with effects and one without. No matter, the CPU is still stays the same soloing all four tracks individually. In other words, there’s no clear difference with and without effects.
Note that the CPU meter of WaveLab does not indicate the total amount of CPU consumed by WaveLab, but the CPU that consumes the most. As the idea is to have an indicator that could explain dropouts, it’s sufficient.
This being said, this does not explain your case.
If I follow you well, by putting a solo track without any plugin on it, then the CPU consumption remains always very high.
I have no explanation for this, especially since it doesn’t do it for me.
The only solution to understand what is happening in your place is to remove one by one the elements and see what is happening at the level of CPU consumption.
Yes you got it right.
I played around a little more and discovered the following: On the project with more tracks (before reducing them and save under new name), I could get the CPU level up (with dropouts and all), just by moving a track down (from track three to track six). Also, this seemed to be even more the case, if there was a Reference track present in the Montage, and I got it below that.
I also found out (in the reduced track project) that even if I the CPU meter stayed the same between tracks, I could, by stopping playback on the track without effects and start playing again, get the consumption down to a lower level.
I hope all this can help investigate the issue further. This has been a returning issue for me in Wavelab, and I never understood what was happening.
Reference tracks are always being processed, but generally they are there to host pure audio, and even if they can have plugins, that’s not their purpose. So if you don’t have any plugin on the reference track, you should not consume CPU for them.
I’m aware of that, and that was what I had (no processing on the reference track).
What was surprising was, that the presence of the reference track, seemed to have an influence on the CPU level as described, on other tracks. Just as the position of the tracks played a role.
