Xoo

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?

1 - https://jstuff.wordpress.com/jbridge/ 2 - "Different" not improved - I've got a few 32 bit plugins that do not behave in jBridge at all (lock up their GUI and then Cakewalk almost immediately), which are solid in BitBridge

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.

And that is hiding, not disabling (yes, its global nature causes the issue, but the fact remains that it's hiding, not disabling a control). One can disable MIDI volume/pan controls, and there's good reason why being able to do the same for audio controls would make sense.

How do I disable the volume widget on a bus (or track) without hiding it?

Right click on bus - Hide Bus. It prevents your issue: "This will prevent accidental tweaks on your "FIXED MASTER BUSS" as it is now. I sometimes come across finding this I had accidentally panned lowered the gain or Volume on my Main Master Track/Buss/ Strip/Channel."

Hide the bus?

Should *optionally*: I'd suggest alt/shift clicking the collapse widget does a full collapse (and doing the same to a closed track should put it back to the previously expanded state).

I kind of see what you mean (and with envelope lanes, there is an envelope created - it's a dummy volume one so it's moot if it's an actual change or not, but with track lanes, I think it's very debatable whether a change has been made - I'm sure that a track always has lanes, it just may have only one that you've chosen not to see). I do think it's misleading as it implies more than is actually happening, at least in some cases - I don't think an "action" button should also reflect meaning in this way.

Intensity I can see why you'd want to be global.

I know, but consider this case... I have a single audio clip in a track. I've never clicked on the expand lane button. I click on it, and the lane shows; I click on it again and the lane vanishes. Nothing has been done to the lane, CbB is in the same state as it was before I clicked, but the button is now a different colour - to me, this implies that there is something "interesting" going on with the lanes. This is clearly not the case, so the button should reflect that (to be honest, I don't understand why there should be a third state for the button colour - Mute doesn't go into a third state just because I clicked on it once! I think this is poor UI).

I do not want snap to be global! I may be editing MIDI clips glued to measures in one and editing audio, where snap needs to be off, in another.

And lane buttons (drives my niggling sense crazy - why should a button's glow status change just because I clicked on it once???).

This.

It shows there's data in a track after the current time (there are no ellipses after the last clip in a track).

12 - No-one mentioned lawyers...

Thanks for the headsup about Sumatra - it's just replaced FoxitReader as my PDF reader of choice (lightweight and 64 bit!).

That won't set the command line parameters correctly, so it won't populate the registry with updated/new information.

This seems a very workflow specific requirement (ie. not that useful to a lot of people) - not saying it isn't, but what's the use case for this?

And if you run vstscan as adminiatrator, and CbB as a different user, you may not see the VSTs you expect in CbB (depends on if you're elevating or using another account which has admin privileges).