Xoo

I meant UAC of course not UAT...too much project work in real life!

Or a popup window hidden somewhere waiting for user input?

I'd be inclined (as I have) to put the x86 VST folder in the root of the C drive to avoid badly behaved/written VSTs falling foul of UAT and refusing to work. EDIT: UAC not UAT.

We've all done it... 🙂

I've been doing this with some old projects: open in CbB, note which plugins don't load, re-open in the last SONAR Platinum (x86), note down 32 bit settings (actually, I usually have the project open in both hosts simultaneously, just am very careful which one I save from!) and listen in isolation then try to recreate in CbB. Tedious but you can get some wins too! Even Microsoft haven't killed 32 bit completely...Windows Media Player 32 bit is still the default media player in 64 bit Windows 10 (and it's a complete pain trying to get the 63 bit version to be the default in its place...I'm not sure it's even possible in recent Windows 10 releases!).

Macrium Reflect is your friend here: image before you do anything so you can go back to square one at any time. And it's free!

Offset set for these tracks (offset mode)?

I doubt it (hope not!).

I copied the authorisation files from an image to try to find out the error code (I didn't note it down at the time) and the old files no longer generate the error. Go figure.

2020.01 early release first noticed. Then (I guess) 2019.11 on reversion.

Nope. Old PC that's worked until 2(?) days ago. Reauthorisation had no effect. Even restoring from a >2 day old backup put it into unauthorised and unauthorisable mode.

It's still occurring now. UPDATE: Solved by one of the Cakewalk support guys (very quickly too!). I had to delete the existing hidden auth files on my machine for CbB then re-authorise.

Also, ASIO can only support one driver concurrently: disable all uses of ASIO4All in Cakewalk, then you should be able to select the Komplete ASIO driver.

Windows update? https://www.thewindowsclub.com/apc_index_mismatch

Also, and I know you've been a Cakewalk user for years so sorry if this sounds like teaching you to suck eggs, do check you don't have a VSTi in the project(s) with MIDI out enabled (not that this would explain the sudden onset of the issue).

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.