Xoo

AMD fTPM (onboard Ryzens) apparently satisfies the requirement. That said, I've never been able to get Windows 10 to play ball with mine (it constantly says it needs to be cleared).

Even better!

Can you not add Spectralayers as a Tools menu item in CbB so this works transparently and automatically? Checks his own notes...yes, you can. I did this with v4 and it worked fine (I don't like Spectralayers though so uninstalled it): Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Tools Menu\SpectraLayers Pro] "ExePath"="C:\\Program Files\\MAGIX\\SpectraLayers Pro 4.0\\Win64\\SpectraLayers.exe" "HelpFilePath"="C:\\Program Files\\MAGIX\\SpectraLayers Pro 4.0\\Documentation\\index.html" "MenuText"="SpectraLayers Pro" "Type"="WaveEditor" "StatusBarText"="Edit the selected audio event using SpectraLayers Pro" Change paths, YMMV etc.

+1 (unless it's an update to something I've previously possibly used the VST 2 version for - I assume the VST 2->3 migration won't work in most cases).

Thanks.

I've now gone to 21H1 and seems OK - I did have one blue screen(!), but I had one prior to 21H1 too (I think it's a bug in my HDMI audio driver). It also looks like Windows hasn't done its fun thing of making me reinstall some drivers (older Edirol PCR keyboard)!

Is there any documentation on how to use the EQ matching?

Did you get it to "Clean up system files" too? It often shows more to clean than it actually does end up cleaning (I have no idea why - it lied to me about 340MB just now ?), but it seems to be in "system files" that the big disk gobblers live, if anywhere. The other suggestion is to use junctions to move things you can't move (like Adobe CC) - I use a tool that integrates into explorer (https://schinagl.priv.at/nt/hardlinkshellext/hardlinkshellext.html) but there are command line tools in Windows that can do the same. - Find the big bad folder on C drive (let's say it's C:\ProgramData\Adobe CC - Create the same folder on D drive - D:\Adobe CC - Copy the contents of C:\ProgramData\Adobe CC to ?\Adobe CC - Delete C:\ProgramData\Adobe CC - Assuming you're using that tool, right click on D:\Adobe CC, and "Pick Link Source" - Go to C:\ProgramData - Right click and "Drop As..." - I usually use Symbolic Link rather than Junction, but both should be fine

And also run Disk Cleanup tool - there's quite likely gigabytes of Windows updates lurking around (cleanmgr). For what it's worth, my C drive partition is only 64GB, and I currently have over 40GB free on it. That's by ensuring I have large libraries, documents, samples etc on other drives/partitions (I can't be bothered to move a library of a few megabytes!) and keeping temp folders and the like clean. One of the biggest disk space suckers is C:\Windows\SoftwareDistribution\Download which doesn't seem to get cleaned up by the Disk Cleanup tool (my work machine has 600MB in it, and I've seen it have several GB after a Windows update).

Not sure where to start dissecting the "information", but +1 to @scook

Good idea: and Windows does this "natively" (within File Explorer), so no need to go fiddling around with command prompt or similar.

Funnily enough, I overcompensated for this on my own "Tungsten-" theme (it's basically an overlay for Tungsten which tweaks clip and track name colours, so no need to constantly update when there's a new release - I alternate between it and Blue Aston with my clip colour overlay applied) - I made the scrollbar thumb too close in colour to the scrollbar background to the extent it was invisible and I couldn't find it to grab it ?

I did???!? I forget these things nowadays ?

Couple of things: 1 - Have you (intentionally or unintentionally) disable 8.3 file naming on the drive where your VST dll's are stored? For historical reasons, Cakewalk needs the 8.3 file naming to be enabled (https://www.tecklyfe.com/windows-server-tip-disable-8-3-naming-strip-existing-short-names/#:~:text=To disable 8.3 naming system-wide%2C run the following,short names%3A fsutil.exe 8dot3name strip %2Fs %2Fv D%3A). NTFS can do funky things with 8.3 names even if you delete a file and copy a new one with what should be the same 8.3 name back in, if you do it quickly enough, Windows gives it a new 8.3 name... 2 - Given the above, have you tried uninstalling and then re-installing, rather than updating, which might create the same 8.3 name for the new file (if it's essentially the same filename/8.3 name(? 3 - There's no central registry for VST IDs, so there's merit in using the filename (else you could end up with 2 different VSTs with the same ID...what to do then?), but there's probably improvements that could be made (eg. use filename to disambiguate if you have 2 dll's presenting the same ID). But that would possibly(?) break backwards compatability, and we know how good Cakewalk is with that. 4 - It's probably possible to hack the relevant registry keys to make it work, but you'd likely have to do it every VST scan (definitely if you do a full rescan): HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Cakewalk VST X64\Inventory DosName, FullName andFullPath are probably the values that would need to be tweaked within the plug-ins key. But I can give no guarantees of what would/wouldn't happen, so do so at your own risk.

20H2 working OK for me - I had to drag my PC kicking and screaming as MS was convinced it was never ready for the update, but it's worked fine.

I'd completely forgotten this song - brings back a lot of (old) memories!

Alternatively, open up regedit (Registry Editor), navigate to HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Cakewalk VST X64\Inventory\c:/program files/Cakewalk/shared utilities/Internal/Saturation Knob.dll, and hasVstEntryPoint from 0 to 1. Open CbB and rescan VSTs; you may need to close and re-open CbB (I did, but that may be because I was registry editing at the same time). It'll appear as a plug-in and a PC module.

Time flies. You cannot. They fly too quickly. ---------------- Ah, the joys of the English language.

Thanks for this link - hard to keep on top of everything to update these days!

1 - Who says? 2 - That Sweetwater article explicitly says "Myth: VST 3 plugins are more efficient" (they can be, as there are some features that VST 3 supports more easily than VST 2, but there's no guarantee). 3 - VST 2.4 is only being phased out if a host/plugin wants it to be (there are some restrictions on new developers, but not those with existing VST 2.x licence agreements). The (non-DSP) coding is *very* different, so this is not necessarily trivial at all. And since the existng plug-ins work, why "waste" time re-writing them?

It'll just not be called Windows, hence Windows 10 will have been the last version of "Windows". Problem solved ?

Do you need to even display them?

Depends on the NAS, the network speed and the network usage (congestion)...oh, and how much data you need to pull (eg. if a NAS can't do one audio track, it's broken :-)).

Memory - use the built-in Windows RAM checker (I forget how to do this offhand) - definitely sounds like failing memory (might just need reseating or similar).

I think it depends on the foreground colours - I'm currently using (when not using Blue Aston) a very slightly modified Tungsten theme, which just changes clip foreground and background colours (so all I do is merge my theme with Tungsten when necessary and re-save it in the Themes folder). My clips' backgrounds go lighter and I don't see a loss of contrast (well, technically I do, but it doesn't seem to have a negative effect on the clarity). So I just tried a quick test, where I darkened the background selection colour (0B0B0C as it happens, but pretty much picked randonly!). There is more contrast, as expected, but it actually looks worse to me - also, the clip header (Maximise Waveform Height = off) now jumps out as it's light, and the overall effect is a bit unpleasant (to be fair, I think the clip header needs to blend in more with the selected colour anyway, but that's a different matter). Before and after screenshots attached. UPDATE: I've just noticed the colour in the Theme Editor "Clip Background (selected)" isn't actually used all the time. Mine is set to #444448, but if I use the colour grabber tool in the Theme Editor to actually grab the colour from a selected clip, it varies from this at the very bottom of a selected clip to #555559 at the top. Interesting, eh? The clip header and the unselected clip also similarly gradates. UPDATE 2: There's also 2 lines added top and bottom of the clip when you select it, in a light colour (I say light, as I can't see how to change it - ideas?), which makes a dark selected clip header look ugly. To demonstrate, make the selected clip header and selected clip background both black.