SAW Studio v2 and MT Load
Moderator: Bob L
Re: SAW Studio v2 and MT Load
You could try disabling groups of tracks (or maybe number select one half, then the other) to attempt to see if you can identify one particular (or some) plugin that is related to the high loading.
Re: SAW Studio v2 and MT Load
Understood, Bob. I will keep that in mind.Bob L wrote:If using SAC as a front end, then you have no control over SAWStudio buffers... SAC takes over and balances them out... SAC should be used for live low latency with buffers set at 64 or 128 max... and as for FX that cause the floating point error, you can always just keep some open room mic active on the track or bus so the levels never go all the way to zero.
Bob L
Re: SAW Studio v2 and MT Load
I had been doing this sort of thing in this particular five-song session.jmh wrote:You could try disabling groups of tracks (or maybe number select one half, then the other) to attempt to see if you can identify one particular (or some) plugin that is related to the high loading.
That helps with the freezes.
My current curiosity has shifted to the difference between running the RME/SAW buffer settings at 2048, or 1024 (and 512 it seems) and the dramatic MT readings.
I'm speaking about editing/mixing in SAW, without SAC as the front end again, as I typically have done, when not tracking.
I think I will create a duplicate session in SAW 32bit tomorrow, using the same 64 bit plugins, through jBridge (just to see how much impact the plugins are actually having). I will run both 64 and 32 bit sessions without SAC (64 and 32, respectively) at 4 x 2048 buffers and 4 x 1024 buffers and see what there is to see.
Re: SAW Studio v2 and MT Load
This is the configuration i always use. Many mixes have regions here and there with long gaps in between.UpTilDawn wrote:I'm speaking about editing/mixing in SAW, without SAC as the front end again, as I typically have done, when not tracking.
Whenever I'm doing any sidechaining, I patch a vst on the keyed track to let the compressor or gate to return to their 'normal' levels to avoid surprises. That has the opposite intent - to avoid auto fx bypass. I guess I have to be careful what plugin I use, as that could cause the problem being discussed. (Also if the key has any gaps between regions, I just mix a 'helper track' that is contiguous audio).
Anyway, I'm curious what you find that is causing the loading.
Re: SAW Studio v2 and MT Load
An update -
Okay, finally got this tested in both SAW 32bit and SAW 64bit.
I used all 64bit plugins, with jBridge to port the 64bit plugs into 32bit SAW.
The session consisted of five songs, recorded at 48k/24bit and separated into their own group of 11 tracks per song, across the timeline - around 20 minutes long. There's five aux channels with six various 64bit vst fx and a total of nine different 64bit vst fx inserted in various track/channels throughout the five songs, as well as a number of SAW native plugins. Plus, each channel has some amount of channel strip eq and dynamics. And the main output has a small number of vst and native fx, also.
The 64bit session has automation across some tracks and most inserted fx are bypassed until they are needed. The 32bit session has all fx active all the time and there is no automation. Neither session has significant editing to the original regions.
At 4 x 512 buffers, the 32bit session played normally, with a single group of 11 tracks active at around 27-30% MT load. Each additional group of 11 tracks added just 10% load, with a total load of 70% for all 55 tracks.
At 4 x 512 buffers, the 64bit session played normally, with a single group of 11 tracks active at around 21-22% MT load. Each additional group of 11 tracks added just 2-3% load, with a total load of 32-33% for all 55 tracks.
At 4 x 2048 buffers, the 32bit session played normally, with a single group of 11 tracks active at around 25% MT load. Each additional group of 11 tracks added just 8-9% load, with a total load of 61% for all 55 tracks.
At 4 x 2048 buffers, the 64bit session played normally, with a single group of 11 tracks active at around 20% MT load. Each additional group of 11 tracks added just 1% load, for the first four groups. However, adding in the fifth group jumped the MT load to 99%. I was initially able to get the load to jump back down by disengaging up to eight tracks.
Further checking revealed that I could actually load up all but one or two tracks and keep the MT at 24%, depending on where on the timeline I started playback. But, as soon as I enable one more track, or even engage a couple of channel strip processes on an active channel, the MT load jumps to 99% (or rapidly climbs). The choice of tracks and timeline position is totally arbitrary, though and doesn't seem to be dependent on any particular fx, fx chain, or timeline event. It just appears that when some amount of "load" is reached (around the 24-30% mark), the MT jumps to 99% on playback.
This doesn't happen in SAW 32bit.
Sorry for the really long-winded post, just to reach the same conclusion I started with.
Okay, finally got this tested in both SAW 32bit and SAW 64bit.
I used all 64bit plugins, with jBridge to port the 64bit plugs into 32bit SAW.
The session consisted of five songs, recorded at 48k/24bit and separated into their own group of 11 tracks per song, across the timeline - around 20 minutes long. There's five aux channels with six various 64bit vst fx and a total of nine different 64bit vst fx inserted in various track/channels throughout the five songs, as well as a number of SAW native plugins. Plus, each channel has some amount of channel strip eq and dynamics. And the main output has a small number of vst and native fx, also.
The 64bit session has automation across some tracks and most inserted fx are bypassed until they are needed. The 32bit session has all fx active all the time and there is no automation. Neither session has significant editing to the original regions.
At 4 x 512 buffers, the 32bit session played normally, with a single group of 11 tracks active at around 27-30% MT load. Each additional group of 11 tracks added just 10% load, with a total load of 70% for all 55 tracks.
At 4 x 512 buffers, the 64bit session played normally, with a single group of 11 tracks active at around 21-22% MT load. Each additional group of 11 tracks added just 2-3% load, with a total load of 32-33% for all 55 tracks.
At 4 x 2048 buffers, the 32bit session played normally, with a single group of 11 tracks active at around 25% MT load. Each additional group of 11 tracks added just 8-9% load, with a total load of 61% for all 55 tracks.
At 4 x 2048 buffers, the 64bit session played normally, with a single group of 11 tracks active at around 20% MT load. Each additional group of 11 tracks added just 1% load, for the first four groups. However, adding in the fifth group jumped the MT load to 99%. I was initially able to get the load to jump back down by disengaging up to eight tracks.
Further checking revealed that I could actually load up all but one or two tracks and keep the MT at 24%, depending on where on the timeline I started playback. But, as soon as I enable one more track, or even engage a couple of channel strip processes on an active channel, the MT load jumps to 99% (or rapidly climbs). The choice of tracks and timeline position is totally arbitrary, though and doesn't seem to be dependent on any particular fx, fx chain, or timeline event. It just appears that when some amount of "load" is reached (around the 24-30% mark), the MT jumps to 99% on playback.
This doesn't happen in SAW 32bit.
Sorry for the really long-winded post, just to reach the same conclusion I started with.