Xoo

https://www.bing.com/search?q=daw+freeze&form=QBLH&sp=-1&ghc=1&pq=daw+freeze&sc=8-10&qs=n&sk=&cvid=A28D37239611445D808AD5995C408633 "Every supported DAW has a similar feature (typically called Freeze or Track Freezing) that will non-destructively commit all active effects to a new audio file and disable the plug-ins used to process the original track, which will free up additional DSP in the case of UAD plug-ins. Track Freezing is usually an automatic process, whereas soloing a track and bouncing it to a new track will require you to manually mute and disable the plug-ins used on the original track." I'd say Freeze means exactly what Cakewalk says it means!

It's not a bug as such - that's how ND-MIDI editing is supposed to work.

Try this (this setting affects split behaviour): - Open Preferences - Check the Advanced radio button - Customization\Editing - Untick "Non-Destructive MIDI Editing" Repeat your test. Otherwise, rather than Trim, do Bounce to Clip.

It did work sometime (as I didn't use to swear at it :-)) but not sure when it broke!

You also get emojis if you're not careful ?

That's 2 knobs though, not one knob and one button, right (that does make sense - it's the double mono/stereo button that doesn't to me)?

Why do you need 2 mono/stereo buttons (I get the pan control bit)?

I just popped in an Asus nVidia GT1030 silent card (https://www.amazon.co.uk/gp/product/B0716JTSRW/ref=ppx_yo_dt_b_asin_title_o08_s00?ie=UTF8&psc=1) as an upfrade from an older nVidia card and it works very nicely with Cakewalk.

Find the relevant .vst3 file in C:\Program Files\Common Files\VST3 and delete it (or, preferably, rename it to, say .vst3bad) and rescan in Cakewalk.

You can also bind a shortcut key.

No worries - I learned tricks about the Matrix View from your video, so good swap ?

Agreed.

No, Bill, you're not: it's broken (well, it doesn't work as expected based on the GUI anyway).

Nice - you know that clicking on an empty cell in a row stops that row playing (even when in "latch" mode), so you don't need to use the "kill all" button?

https://lmgtfy.com/?q=kvr

I've had to do this with one (old) 32 bit VSTi (in the days of 32 bit SONAR too) - that's excluding the case where BitBridge refuses to recognise one 32 bit VST as a valid VST, despite everything else under the sun detecting it as such... Note that you'll lose this if you do a reset/rescan, so you may need to re-apply (my fix is to export the relevant registry (sub-)key and zap that in when necessary).

Try saving to a completely different location too (if you haven't already)?

Is D a network share or local drive? If the former, have you rebooted the server? If the latter, have you rebooted your PC?

Just updated Windows to 2004 by any chance? If so, there's a thread on KvR about this with some possible ideas.

Or (better?) implement some mode like other DAWs do where non-realtime tracks (ie. no input monitoring) playback at a higher/multiple of the ASIO buffer. Even if you have to click a button when you want it to activate (on all tracks for mixdown), it's clearly doable - hopefully on the Bakers' radar (and close up at that too).

I've opened .wrk fikes created in Cakewalk Pro Audio 9 in CbB...

I'm not sure how the scaling works on MIDI tracks - on audio volume, it's definitely just additive.

1 - Aha...read up on Offset Mode. I think it does what you want/.

Having 2 volume controls makes it more confusing for users (IMHO).

Novel!