Xoo

@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?

Apart from the PRV (which is unusable in virtually every theme*, Tungsten included, so I can't blame you ?), this is really, really nice. My other minor nitpick would be to make the 2 colours below the track view panes the same so it jars a bit less. Something like: instead of: * I can't see how anyone can find this bearable:

HDMI cable to a monitor?

Not sure if it's been mentioned, but I found Odin2 a couple of days ago - very nice (and, of course, free): https://www.thewavewarden.com/odin2

Guitar solo in Comfortably Numb (Delicate Sound of Thunder) - first time I heard it was almost tear-breaking.

What do the meters say? Is this just something psychological going on?

I feel like this is not disimilar to the sampler FR...there are 2 different "requirements" that are getting conflated and confused. The existing Drum Maps in CbB are really "MIDI Output Mapping" - the fact that they can be used for drum mapping and drum note naming is almost coincidental - and as such (as @scook pointed out above) make sense to remain where they are, as part of the track settings. Now having their UI improved is a different matter and probably one where we would all agree that improvments could be made (we'd probably argue about how of course :-)). Remember that this feature comes from a time when multiple, external MIDI modules were often used to create a full drum kit (I had 2 Alesis D4s and a DM5 at one stage, so I've been there!), so is focused on that kind of setup. Then there's the new requirement (as I understand it) to be easily able to set the names of notes in the PRV for a single drum soft-synth (be that dedicated or sampler based). Mapping across ports and channels and notes is pretty much irrelevant and the Drum Maps are absolutely overkill - and not in the sensible place. So I think this FR should be thought of in this context and trying to link it in with Drum Maps is a red herring. Note that there is VST2 (and 3?) standard functionality for a soft-synth to expose note names to the host - very few do this, which is a pity (fxPansion BFD 1 and 2 do this - even for the DXi version of BFD 1! - as does Cakewalk's own Session Drummer 3, and even fxPansion's venerable DR-008 does, but I gather not many more do).

Ah yeah - forgot that step!

a) Yes ? b) No c) Alongside (and keep installed plug-ins assuming you set VST scan paths correctly)

Yes, but it's not trivial: - Open regedit - Navigate to HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Core\Recently Used Plug-ins - Delete any subkeys or values under this key - Right click on the key and choose permissions - Untick Full Control (ie. leave it with Read as the only ricked box) for the user you've logged in as - Click OK - Repeat for HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Core\Recently Used Synths

Have you tried the MIDI MFX effects?

It depends on whether the plugin manfacturer has updated the VST2 (yes, the VST2...) to say what the VST3 replacement is. Bonkers logic as it requires re-shipping old plugins!

I may be missing something with these, but I have Move Studio 16 Platinum and it won't import QuickTime files, so these aren't usable. Anyone?

Might have been that to be honest (it was a while ago), but it bugged me a lot anyway. I may re-try when 1.8 is out of beta. UPDATE (January): I can't get it to glitch now, so it may have been an issue with the audio drivers (I was playing using WASAPI at the time, which I find quite unpredictable). I don't think I'm going to keep it installed though - the UI for the synth at least is just too finickety for me to work with.

Groan ?

Or you can create a shortcut to use start /affinity <bitmask> <exename> eg. start /affinity 0x555 cmd.exe starts cmd.exe using cores 0, 2, 4, 6, 8, 10 on my 6/12 core Ryzen.

I like the idea of Surge, but found it extremely glitchy to use (as in audio glitches) - I think there is/was an issue with the release control not being smooth, as it was at the end of notes that I could hear a "click". Or maybe the presets were badly programmed. Either way, it didn't inspire me to keep it installed.

I loved my MMT-8!

And (just in case): Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ASIO for the 32 bit "ASIO" driver.

3.2.3 is the latest anyway (and they sound pretty nice at first quick listen).

Not knowing the exact amount CbB attenuates by, but could it be the difference (when adding up multiple tracks) between 3dB attenuation and a more accurate 3.01dB? db = 20 * log10(amplitude) But it can be cheaper (in terms of CPU) to calculate 6.02 * log2(amplitude), where 6.02 ~= 20 * log10(2)) * * log10(2) = 0.301029996, 20 x log10(2) = 6.020599913 Or different tapers on the pan law (remember CbB - and SONAR before it - can do sin/cos as well as square root)?