A thought from someone who works between video, music, design, and code: I totally agree with danielr78503840 that contextual switching should be optional. The default should be a stable control that you know will be there without looking. You know what I'd like to see? An abstracted mapping workflow that's the same across all adobe products, one that unifies keyboard shortcuts, gestures, custom touch bar buttons, and external devices. Not sure if anyone's familiar with this, but Ableton Live does a great job with this. You enter "mapping mode," and you can basically control any parameter with any key or MIDI (or OSC or whatever) device. And if the versatility isn't enough, you can always go into Max and code your heart out. I want to be able to define a custom slider on the touch bar, then open a single mapping interface and map that slider to (for example) the timeline in Premiere, page selection in ID, layer opacity in PS, keyframe easing in AE, and file scroll in Bridge. I don't want to have to write special macros for each app, or tunnel through keyboard shortcut menus every time I want to edit the mapping. I feel like the touch bar is a perfect test bed for this kind of thing. It really shines when it doesn't just emulate buttons, but instead acts like a control surface, with dragging, multitouch, etc. So it seems to me a natural pairing for effect controls (not just in premiere). For that to be useful, though, it has to be easily and fully customizable. In an ideal world, that customization would have a fast, intuitive GUI that could then be easily modified/extended in code (without finding some obscure buried preferences or script folder).
... View more