Xoo

Under 2 seconds here for the CbB 16 track template. AMD Ryzen 5 2600 (6 core/12 threads), stock speed (3.4GHz, but it boosts itself to ~3.75GHz all the time), 32GB RAM, NVMe Windows/application disk, SSD (Samsung 860 EVO 250GB) data drive, 2GB nVidia GT 1030 video card. So nothing that special (for 2020!). Windows Defender realtime scanning disabled completely.

Did you hear about the man who had his house made backwards so he could watch TV?

And, from memory, you can change the filter on multiple tracks using quick grouping.

My bad terminology - I don't mean driver interfaces, I meant using different "driver" APIs (sure, they're not all drivers in terms of pure Windows nomenclature). Rather than having to interface to ASIO, WDM, DirectX, MME, WASAPI, just write an ASIO interface layer and pass the buck to an off-the-shelf translation layer for non-ASIO soundcards.

Do you mean this setting in aud.ini? AutomationDecimationMsec=50

Saves them having to write multiple driver interfaces - they just write an ASIO interface and let ASIO4All etc handle the wrapping if a real ASIO driver doesn't exist. Makes a lot of sense from a coding perspective (especially if you're primarily aiming at "pro" users).

There is a hacky way round this now (although manually entering is a good idea) that may work: Change the project tempo to what you want the clip to be at (let's say 100bpm) AudioSnap the clip Open the AudioSnap Palette Select From Project - tempo set at 100bpm Change project tempo back to what it should be Note that tempo stays at 100bpm in AudioSnap Palette

Check that your Workspace (Lens) does not exclude video view.

*Vice* President, surely?

Agreed - just pointing it out for a quick (if not free) fix.

Ah - I was referring to plugins. Fair enough.

Short-term, BlueCat's patchbay.

Very unlikely it uses .NET.

Real web techies pronounce www "dubdubdub" ?

And it would need to be auto-sorted so MIDI FX were at the top of the bin and audio at the bottom (mixing them up makes no logical sense!). Or a split bin on a Simple Instrument Track.

Hmm - I was sure that was it. I also thought (but can't find) there was a setting that said something like "Allow record enable during playback" that may have been the candidate... Does your project have a number of audio tracks equal to the number of "test" wavs that get created?

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.