Xoo

Remember that by default (from memory anyway), Reaper runs its look-ahead processing, so not all tracks are "Live" (the equivalent of being able to being IMable in CbB). If you disable that, odds on it'll behave much closer to how the other applications do.

I have a sorry history of major Windows 10 updates - I've never had one work seamlessly and have always had to do it via the Windows10Upgrade path. With 1909 to 2004... I originally had an old nVidia card that wasn't supported (it was also not getting good driver updates and was quite slow), so Windows Update "correctly" wasn't attempted when it was available. I replaced the card with a supported nVidia card and - yay! - Windows Update says it can update to 2004. It failed. And now Windows Update reports the "...Once it's ready for your device, you'll see the update available on this page" message again. Except it *is* available for my device (on paper), but there is seemingly no way of telling Windows Update that this is the case and to try again, so I'd be back to the Windows10Upgrade path, which is a pain to go through. Not that there's anything I want in 2004, but I'd like to not be too far behind on major Windows versions.

Right click on clip, PRV, no?

Yes, right click works like that.

Or create a new track, drag copy clips and link them (so they stay in sync with the source). Or use something like Blue Cat's Patchwork

Can I take the 5th? ? "Sometimes as part of workflow, but not regularly and only for some functions"

I'd just really (and have requested this back in the pre-X series days!) the waveform to have the distinct coloured line round the edge like Cubase - it looks so much cleaner to me.

Seems to be working today.

Ditto: 499KB,

Global folder is set in Preferences\File\Audio Data (not in Preferences\File\Folder Locations). Yes, there's an argument for all folder locations to be set on the same preferences page...

Steve Hillage meets Pink Floyd - nice.

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.

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