Kevin Perry

That was close to my conclusion too :-( Thanks

Canopus - do you have any idea (post-09 update) how to change the colour of the text appearing on top of MIDI notes in the PRV? I have the unenviable position of dark grey on black (or similar) so the new feature is pretty useless for me.

What is your auto-save set to? If set to a very low number of changes, and you have a big file, it could cause this. It's in Edit\Preferences\File\Advanced (you'll need to enable Advanced view via the radio button in the preferences window). Does it happen with small (new) files? Any disk issues on the drive(s) you're saving too (run chkdsk) that autosave may be exposing? How long does a "normal" (ctrl-S) save take on these projects?

Makes sense to me too.

+1

It's possible to disable the recent behaviour (which I can't see any benefit of having) by restricting registry key permissions.

I'm still waiting for it to make me my tea in the morning.

For what it's worth, after reading this thread, I checked a 32 bit plug-in (MHC's Ambient Keys) which has the same problem - in both 32 bit and 64 bit SONAR/CbB - the preset changes to preset #1 (counting from #0 in the plug-in's preset list). Using the demo version of jBridge resolves the issue. Interestingly, though, it has the same issue in my quick'n'dirty 32 bit VST checker Chainer and Samplitude. So it looks like some vagary in the VST spec that many hosts (and bridges) don't deal with in the way all plug-ins expect, but jBridge does. Maybe this will help the Bakers work out the issue (perhaps the same happens with the internal VST handling in CbB too for 64 bit plug-ins).

Not related to DAW performance as such, but Intel Hyperthreading is now recommended disabled for security reasons. https://www.theregister.co.uk/2019/05/14/intel_hyper_threading_mitigations/

I can get it working if in C:\VeeSeeVST but nowhere deeper so far (on 2 machines). Crashes VSTScan hard on my DAW, simply doesn't get scanned properly on my work machine. UPDATE: Confirmed on my DAW that any folder below C:\ (or, I assume, another root) crashes the VSTScan. C:\VeeSeeVST and it works fine. That inspires me with little confidence in the quality of the software, which is a pity as it's *FUN*.

I see what you did there :-)

That's what I used too (and I too renamed vst2_bin). I'll try on my other PC sometime tomorrow.

Not here it doesn't work - VST scan hangs for ages on the _effect dll and never seems to complete its scan.

Related? https://www.theregister.co.uk/2019/04/24/windows_10_may_2019_update_block/

Device manager does - you need to change the view type to "devices by connection" (or similar -not at PC right now).