Xoo

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!

I have it switched on (nVidia GT1030) and it works OK with Cakewalk - doesn't make an obvious good or bad difference in anything I use to be honest.

Graphic design that uses fonts still seems to be a Mac stronghold in my (current) experience.