Two Curiosities in SAW64

[UpTilDawn]

I think this has only been the case in SAW64 and beyond (not in 32).

1 -
Sometimes, when I left-click on the timeline, the whole timeline suddenly shifts, instead of the cursor simply moving to where I clicked. It's disorienting and catches me off-guard to the point where I can't give any details beyond saying that I have to zoom out a bit to relocate where things are. I'm not sure if the timeline actually shifts, even. But I do need to reorganize for a moment.

2 -
When I first open a session that might have an output, or return at the top of the MT (my default f-key opens to the MT almost dominating the view) and then go to an f-key with the wide mixer dominating, the image is corrupted - displaying a view as wide as the normal input channel mixer, but with everything to the right of the more narrow output (and Return) mixer being just black.

I can fix it by scrolling down to an input channel and then back up again and all is good afterwards.

But, a related issue (I assume), is that after a session has been open for awhile (maybe 10 minutes, or longer??), certain plugins that are already inserted (from a few to many) will not display their controls/settings when opened to adjust parameters - I just see the SAW plugin window background inside the plugin's border. Sometimes, jBridge'd plugins will still show the banner at the bottom that shows the jBridge details.

I'm assuming this may be primarily an issue with how SAW and my graphics card are(or are not) playing.... but I don't know why it's only after awhile and with not all plugins... Maybe the second issue is a RAM issue??

Any suggestions would be helpful.

[Bob L]

First... download the latest 2.1 version if you are on V2.... if you are on the 1.4 version, then make sure you have the realtime priority option checked in the options view and see if that makes a difference.

Also, make sure your FKeys are not corrupted... go thru each FKey and make sure each window view is not corrupt in any way... if so... clean it up and resave the FKey... then resvae the entire FKey set as the default.... see if that helps.

Bob L

[UpTilDawn]

Thanks Bob.
I will look into both things as soon as time allows.

[ivanoff]

hi, also when soloing busses the solo led doesn't turn on sometimes in the multitrack.
I find SAW ( last version) freeze more often, I had to stop the process.

[Bob L]

If its version 2.0... definitely download 2.1... should stop any freezes.

Bob L

[ivanoff]

If its version 2.0... definitely download 2.1... should stop any freezes.

Bob L

Ok, I didn't see the new version.
Thanks very much Bob.
Regards

[jmh]

Sometimes, when I left-click on the timeline, the whole timeline suddenly shifts, instead of the cursor simply moving to where I clicked. It's disorienting and catches me off-guard to the point where I can't give any details beyond saying that I have to zoom out a bit to relocate where things are. I'm not sure if the timeline actually shifts, even. But I do need to reorganize for a moment.

Could it be re-centering on the cursor? Maybe this happens when the cursor is beyond the displayed timeline.

But, a related issue (I assume), is that after a session has been open for awhile (maybe 10 minutes, or longer??), certain plugins that are already inserted (from a few to many) will not display their controls/settings when opened to adjust parameters - I just see the SAW plugin window background inside the plugin's border. Sometimes, jBridge'd plugins will still show the banner at the bottom that shows the jBridge details.

I'm assuming this may be primarily an issue with how SAW and my graphics card are(or are not) playing.... but I don't know why it's only after awhile and with not all plugins... Maybe the second issue is a RAM issue??

I have yet to setup V2, but the Tokyo Dawn Plugins do this in 32 bit. They are probably my favorites.

When this first occurred, I had (for example) one version of Nova, and also the paid Nova-GE. I thought there may have been a dll mismatch, but I purged all instances of the free version, and it still occurs. The only remedy is to save, exit saw and reopen...

It does not seem to be time related to me. Those plugins always seem to initially display properly regardless of how long saw has been running.

EDIT:
It seems this is more likely to occur if there are multiple instances of the plugin deployed - but this may just reflect the increased likelihood that I open one of the interfaces.

[jmh]

A tidbit of info I came across - it may be totally irrelevant - or something already being done in saw.

A search of 'vst api refresh display' yielded:

'To refresh the display of a VST plugin, the host application should call the audioMasterUpdateDisplay event to ensure that the parameter display properties are updated. This is particularly important for plugins that may change their parameter names or values dynamically.'

Edit: On further searching, I'm not sure this call even belongs to a vst API. It was text duckduckgo spit out.

[jmh]

But, a related issue (I assume), is that after a session has been open for awhile (maybe 10 minutes, or longer??), certain plugins that are already inserted (from a few to many) will not display their controls/settings when opened to adjust parameters - I just see the SAW plugin window background inside the plugin's border. Sometimes, jBridge'd plugins will still show the banner at the bottom that shows the jBridge details.

I'm using 32 bit, so vst2. Are you hitting this with vst3? From what I've read, the plugin display is done differently in vst3.

[UpTilDawn]

I'm using 32 bit, so vst2. Are you hitting this with vst3? From what I've read, the plugin display is done differently in vst3.

This is the one reply I can address for now... I'll have more time over the weekend.

This issue actually started happening for me with the 64bit vst2 of Sonible Smart EQ3 (and 4 as well). I tend to only use one instance of it on the main out for overall eq shaping on the way out and haven't gotten into the use of multiple instances on tracks, or sub outs. I'm pretty sure I don't have the issue in SAWStudio 32bit (although I need time to confirm this).

I only just began doing the ini file thing for vst3 plugins, so I think I can say that it's not been a problem with those yet - but we're talking about just 4-5 plugins. Up to this point, the few other vst3s I've used have been through a bridge (is that what they're called?) - mainly Waves Studio Rack, which was offered for free and has been helpful. I just recently bought The Blue Cat Patchworks, with the intention of weaning myself from Waves, while I still only have a small handful of their plugs (I'm just not thrilled about how Waves invades my work time - for lack of a better description), although I do like how the ones I have add to my idea of good sound production.....

That aside, I initially thought the problems here were centered around plugs that used the most resources, but it's been a problem with an assortment of plugs - mostly 64bit vst2s, I suppose -

It's not an issue (for me) of multiple instances, since Sonible's Smart EQ3 (or 4) is the most irksome, single use plugin I struggle with in this regard. I, too, have found that all I can do to resolve the problem is to Save, Close and Reopen the session (or SAW itself).

I wonder, also, if this is connected to the sudden, but thankfully infrequent, freezes I'm experiencing, which force me to use Task Manager to end SAW and reopen SAW and the session (losing anything that wasn't saved just before the crash). It will freeze while playing, or sometimes, just when changing f-key views (the most infuriating moments, for sure). I can always tell, when I've "done too much", just as SAW locks up. But I cant predict and avoid.