Closed ScottChesworth closed 1 year ago
This makes sense. As to how it would be implemented:
So, not super hard, but somewhat tedious.
The hardest part is step 1 and a little bit of step 3. The rest is all basically just tedious copy pasting with adjustments for action ids. I can probably take a stab at the harder parts if you're up for taking a stab at the easier but more tedious parts after I'm done. :)
The name's Chesworth, Scott "easy but tedious" Chesworth...
No wait, the namespace is...
Gimme something to work on (so I won't have time to do these jokes)... :)
hi guys. In Osara's help, added the new lines for pan, mute and volume in post-FX, as well as pan and mute for Pre, but one more was missing, for volume, Control Shift Alt v. Keep showing up only on the track, greetings.
That's not a mistake. Control+Alt+Shift+V is only showing/hiding a track envelope, because there isn't an equivalent take pre-FX envelope.
During my (so far) flawed attempt to implement the reporting requested in #849, an idea occurred. As things stand, we have functions to report working with track envelopes, and best I can tell, to complete the request we'd need a bunch of new code to start reporting working with take envelopes. Instead, I'm wondering whether working with envelopes could be made more context sensitive? Here's how the UX would look from user perspective, taking our current key mappings as examples.
I'm definitely not far enough along to write this, but I'd love it to happen, it would make working with envelopes more intuitive and squeeze more functionality onto the key map without requiring users to remember additional keystrokes. Penny for your thoughts?