Xoo

What happens if you drag the VSTi into a track's FX bin rather than the synth rack?  Some synths (eg. Pentagon) do expose their inputs in this way (Pentagon works as a vocoder if you so).

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.

38 minutes ago, jackCA2A said:

Thanks Mark. No, freezing is not what I'm after here.  Disabling a track is what i want.  BTW, is there anything Cakewalk can't do? ...Can't believe it's free.  

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*.

On ‎5‎/‎7‎/‎2019 at 12:05 AM, Starship Krupa said:

No more Reaper madness.

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).

2 hours ago, Starship Krupa said:

That is an interesting theory. Like a "race" condition in programming?

Given the vagaries of the VST specification, it's not at all impossible that CbB calls various VST APIs in a different order to (some) other hosts.  And some plug-ins expect one order, and others another, and a third kind don't mind...

Alt-F4? :-)

6 hours ago, Rick Hamouris said:

*UPDATE - LOL... shot myself in the foot real bad... the default IO's were ASIO, my creative X-Fi only uses WDM... so once I fixed that... voila!

 

Chiming in here... I not only get a failure at the UI notification but endup with a BSOD error stating DPC_WATCHDOG_VIOLATION (with the resultant forced restart)

I've tried updating hard drive drivers, but I don't have iastor anywhere.

I've attached my sysinfo file (memory.dmp is too big)

'preciate the feedback

 

sysinfo.txt

Having had those BSOD errors for a while (Windows 7), I found out that it was my video card (NVidia) causing them.  But it wasn't the drivers or the hardware, rather the card had worked itself slightly loose in the PCIe slot!  I unscrewed it, reseated it and it was fine...until it happened again.  Did the same thing again and it's OK - I think there's a heating/cooling cycle that makes this happen in my case (pun unintended).

That may not be what's happening in yours, but I'd look at the video card rather than anything else.

There used to be a limit of 30 or so "do nothings" and SONAR would crash.  That does seem to have been increased if not removed.

At work I have a similar USB mic and that won't work in Exclusive mode either, for no good reason I could ever find.

I assume you mean WASAPI not ASIO?

Optional please.

Difference between DAWs, although it's entirely possible in the Export dialogue to not include the effects of volume (untick Track Automation, although this will also disable any pan too).

16 minutes ago, synkrotron said:

I had Samplitude.

It was a dogs breakfast and after about a month of creating a "test project" with it I uninstalled.

Each to their own, as the saying goes...

Ditto.  I hoped to at least use the FX/synths in CbB or a.n.other DAW but I couldn't.  I did get SF11, Spectal Layers (which I still don't understand!) and some Izotope plug-ins bundled so it wasn't a complete write off.