Xoo

This is caused by the "Always Open All Devices" setting in Preferences\Audio\Playback and Recording and lots of audio tracks with input assigned.

I've just checked the last version of SONAR Platinum and the mouse wheel doesn't scroll there - I thought it did too, but I think both our memories must be wrong

Replace.

Ah - fair point.

Can you not just fudge this with multiple instances either in separate tracks or something like BlueCat's Patchwork? More tedious, for sure...

And the new PowerToys has a shell extension (Power Rename) that may do what you want too: https://github.com/microsoft/PowerToys

If you keep having to update eLicenser, that suggests something has changed on your machine there (or eLicenser itself has changed, which is why SONAR and CbB are both affected). Now it's also possible that Cakewalk (in both CbB and SONAR) do something that is not quite "on-spec" which causes this problem for you, but that's a different issue (and hard to pin down, especially for users). Worth trying in another DAW if you have one (or download a demo to check).

Could it be one of a Grouped control? If you have 2 controls in a group and a custom relationship set up, it's possible to get one to be limited to a maximum of 12, when the other moves up to 127. I don't *think* that's the case here, but it's all I can think of and may be worth digging into.

Fair enough, but it's sometimes not taken into account when comparing DAWs.

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 ?