Xoo

Not really as you may want to disable the send (I know, there's a manual disable button too) and then re-enable by moving it to a different destination. It would be too easy to send to none and delete by accident.

Alt-drag I believe.

Many years ago, the Waves plugin demos checked the system time to see if the demo period had expired. Resetting it to, say, 1 second after you last used one of them before running them again (and then restoring if necessary) goosed them effectively permanently. Of course, this was in the days before accurate timestamps on ecommerce sites and the like were so important so it wasn't so much of a big deal to have the "wrong" time on your clock.

To "solve" the PC reset, create a blank PC and save it as a preset (and then load it). Useful generally, although a "Reset" button wouldn't go amiss anyway.

Loop Construction View? Not perfect, but with a bit of lateral thinking, you can do some of this.

I have one plugin that crashes like this too - in your case, it's the VST3 listed first. You can zip the dmp file quite well, but this should help - also worth contacting the plugin's author. If you can, try a VST2 version of it too.

Can the CbB scanner be run with its current directory set to, say, %temp% so this or similar can't (famous last words!) happen? I know you can for shortcuts and I have when launching an external exe from a . NET application (ProcessStartInfo.WorkingDirectory).

If one is DOA, that could be the culprit - if you can't get to it physically to unplug, try disabling it in the BIOS if you can.

Which bits exactly?

Ho hum - I was optimistic there for a bit!

So it did work and then stopped working?

Suggestion: untick "Use MMCSS" in Cakewalk's preferences. There is some - ahem - disagreement about whether the driver or application should control use of MMCSS (Steinberg, MOTU and - from memory - RME all say it should be the driver, so I'd argue this is correct), and I wonder if there's some conflict here. It's only a guess mind!

Remember also that plugins can be excluded, which this doesn't take into account: HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\ExcludedPlugIns CLSIDs are used.

Add/edit the following to aud.ini: [Video] VideoEngine=0

I do agree it's over the top (you'd not necessarily want to sandbox every single plugin!), but the principle is correct, no? If not, then where is it wrong?

Interesting comments on this from the developers of Ardour: https://ardour.org/plugins-in-process.html

To me, this sounds like you have the tracks going to 2 destinations simulataneously (master and direct to the hardware), and if the master is then also going to the hardware output, then potentially you are going to get some phasing (you shouldn't, but there may be something else afoot here) which will affect the sound quality in the way you describe. I may be misunderstanding your routing however.

4 - 0.5 = 3.5dB; 4 + 0.5 = 4.5dB. Seems to make sense to me.

It overrides if and only if the setting in Preferences isn't the default - it's not obvious (not totally illogical, but not exactly clear, since you don't know a colour is set to the default without clicking the Default button!).

And thanks to this thread and both of you, I can at least now run a dark PRV myself (no wonder I've never liked most people's themese :-)).

@Starship Krupa: I still see the different left/right pane backgrounds with v2. If anything, they're more different now:

@Colin Nicholls: that's the ticket. Not sure i) which colour setting it is there (I can dig sometime) or ii) why it behaves in SPlat when we *didn't* have the dark colours implemented in the same way. Nor, for that matter, iii) why Mercury doesn't use the (whatever it is) colour in Preferences, but other themes do... And there's something else at play since it doesn't "work" for my own custom theme (one based on Canopus' Lead)...and it looks like a bug. Black Keys Background(s) settings appear in both Theme and Colour Preferences and both seem to work... - Pick something silly for them in a Theme (I picked pastel green and pastel pink for obviousness) - Fire up CbB using that theme and you'll see the Theme's colours respected: Tasty. - Open up Colour Preferences, change Color Category to PRV and select PRV Keys Background (Db/Eb) and pick your favourite different colour. Like mud brown: So, which one actually takes precedence? It seems that if the Colour Preferences option is anything other than the category default, it uses that, else it uses the theme, but don't quote me on that! It seems to behave the same way with the (PRV) Grid Background setting too. No wonder it's confusing!

Cool. I will check with restart, but I don't think it's that. UPDATE: It's not. It's fine in SPlat (final version), but Tungsten et al in CbB throws those horrid black lines for the black notes.

I do know...I just.need to find it (again...I keep forgetting). Weird about the PRV, but like I said, I've had it on every dark/Tungsten theme forever (SPlat days IIRC).

Is there a common plugin you use? I've mainly seen this when a plugin has "issues" with being unloaded. Try with a totally blank project to see if you have the same problem?