Xoo

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...

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?

This is really more of an idea for people to look at rather than a completed AM to show how AMs can be used in "unusual" ways. I have fxPansion's BFD 2 (and BFD 1 and BFD 3, but I've spent most of my time with BFD 2): it has internal grooves that can be triggered by MIDI from your DAW. In CbB, you can use a drum map to expose them or (thankfully because fxPansion implemented the VST note exposure API correctly) from a normal piano roll view. But it's not always obvious when they stop (especially as there are multiple latch modes in BFD 2) or what pattern is playing at a particular time. I've started building some AMs to expose the groove MIDI notes within the articulation lane, so you have more visibility over what is playing when. BFD 2 Grooves.artmap

Oh yeah. I'm sure I managed to do this yesterday somehow like this...it was late!

Slightly faster (this made me think of it): Arm the first track normally Before next recording, Ctrl-A, then Ctrl-click the record button on the new track to record

And Shared Utilities - that's where the cw*auto.dll is stored and if that's out of sync with your version of CbB, bad things (TM) happen. Ah, I see a certain @scook beat me to this ?

But did it look like a kitten..?

Or sustain pedal?

I've seen a development request with a hand-drawn sketch and the immortal words "like this, but better".

OK, so try this... Same file Search for DriverType= Set its value to 2 (ASIO)

It doesn't - I tried last night. Sorry ? I tried adding a DisableWDM entry just in case it also worked - no dice. Fortunately, WDM works for me in Windows 10/Project5, and if it didn't, my MOTU driver exposes a setting "Use WaveRT for Windows audio" (or similar - not at my PC right now) which bizarrely disables WDM in Project 5!