Xoo

Hold down shift to open in "safe mode", and choose not to enable that plugin when prompted.

Yes and yes (that included a simultaneous motherboard and CPU family swap - Intel to AMD, so pretty impressive). That said, I'd take a system image (eg. Macrium) before pressing go...2

Totally empty and on scanning - hence nothing to do with audio at all (or opening the standalone).

Analysis time is as expected (scales with sample length). It's the fixed startup time (at scanning too when no audio is involved): update checks are off.

Problem: the first time within a CbB session that Melodyne 4 (any version thereof that I've tried) is added to a clip as a region FX, the audio mixdown happens as quickly as expected, but the Melodyne UI takes ~11 seconds (consistently) to open - and then the analysis to occur. Subsequent instances open immediately (and then analyse in expected time). This delay also happens when scanning the plug-in (eg. plug-in reset) and also when opening the Melodyne standalone - so this is *not* a CbB issue, but a Melodyne one (it's just I don't open the standalone except to check how it's behaving). This happened on my old PC (Windows 7, Quad Core Q6600) and also my new PC (Windows 10, Ryzen 5 2600), so it's not obviously an OS/CPU issue. It did *not* happen with Melodyne 2 on the old PC. It happened on the free version (Essential) I received with SONAR Platinum, but also with Assistant which I updated to over the Christmas break (special offer). I know of one or two other CbB users who've experienced this (I forget who now though), but I'm surprised that it's not mentioned more frequently if it's a common issue (or people just accept it). My guess is that it's a Melodyne authorisation issue given when it occurs in the Melodyne life-cycle. Is this common and does anyone know how to resolve it? It's not a show-stopper, but I'd really hoped that the upgrade to Assistant at least would solve it.

I think you're right...can you successfully use the ACT plug-in and the Cakewalk Generic in tandem (I think you can, just not sure if they give the functionality you need)?

Is this down to record mode (I guess you'd want to be in Sound On Sound mode)?

This is inherited from the template(s) you create files from, so set these .cst files up as you want, and then subsequent files created from them will have this disabled.

You can exclude individual plugins in the Plugin Manager (Tools menu).

I like this idea.

"Write" as XML with a good DTD (docbook?) and export to PDF, HTML, ePub quite easily.

I have a feeling you've got to have the Browser in focus when you do it (so I agree it's a bug as this isn't what you expect).

Remember also that Windows 10 build 1909 came out recently and if you updated to that around the same time as .11, it may be causing some or all of these problems (I "only" had to reinstall drivers for my Roland PCR-300 but others may be affected more).

Sorry - bounce to split and then delete onetrack.

Or delete one track and center pan the other.

I think it may depend on the plug-ins... I inserted an audio track and then a mono audio clip into the track. I added two plug-ins to the FX bin: first, the old Cakewalk Mono Delay, followed by the Sonitus Delay. I made the Mono Delay 100% dry (so uneffected in practice) and select the "Going going gone" preset in the Sonitus. The Mono Delay has a single pin coming from it, the Sonitus Delay has two - as expected. Whether the track interleave is mono or stereo, I get the delay bouncing between the 2 speakers. It doesn't matter if I set the track interleave to mono or stereo - the result is the same. That's not to say there isn't an issue in CbB's handling of mono (I think there is - some mono plugins (eg. UAD?) perform better on mono tracks in other DAWs, but all CbB's tracks are, as far as I understand, stereo behind the scenes so this advantage is never gained - but it's not totally broken in this instance). Update: Cakewalk Mono Delay followed by Nomad Factory Tempo Delay and the result is mono; followed by the old Project 5 (rebadged in a latter SONAR) Tempo Delay, stereo; 32 bit bridged Kjaerhus Delay, mono; Melda flanger (64 bit VST3), mono. I'm seeing a pattern here. My deduction is that it works as per Reaper (logically?) with DirectX effects, but not with VST ones.

Is this the "10 second delay on opening Melodyne for the first time"? If so, yes, it's definitely a thing (and tied into authorisation in the widest sense of the word - also happens on scanning it as a plugin), but subsequent uses within the same CbB session open OK.

What sample rate are you running at? From memory' TTS1 had issues at some rates.

I have an Ultralite Mk 3 hybrid - occasionally (and this goes back over 2 systems, Windows 7 and Windows 10), it won't connect to USB on power-up, but a power cycle always fixes it. Otherwise, rock-solid. I've just moved it to the new system (Windows 10/Ryzen 2600) and it's even happy plugged into a USB 3.1 socket, which pleasantly surprised me.

P5 worked for me under 64 bit Windows 7 and now under 64 bit Windows 10.

Yes but...one of the issues I have with the existing implementation is that widgets in the TV don't align between tracks in folders and tracks outside folders. You may think that's being picky, but in terms of visual clarity (and efficiency in moving the mouse), it's important - this would only get worse with nested folders. How would (any of) you suggest handling this to make it visually clear which widgets are the same ones in the different folder levels?

Or Alt-left click where you want to split.

It's likely that one of the "big" (like 1903) Windows updates changes relevant settings - you'd probably previously changed the setting that shawker mentioned and 1903 reset it.

FWIW, iLok required.

Is that the one that stops my tunes making me vast amounts of money and fame?