Just thinking about the interaction of actions and surface - all of this might be obvious but just riffing.įor the surfaces to be maximally useful they need to be modal. Most often the idea would be to remove buttons (ones that are out of context) so that you don't press them mistakenly.Įxample 1: If you are not tracking, the record arm and record buttons just clutter things up, they can and should be hidden, so that they are not inadvertently pressed.Įxample 2: If you use an Apollo or equivalent, the input monitoring section is generally just clutter, the Apollo console takes care of that chore. You have to be able to change workflows quickly, perhaps in a way very like the layers on the live digital boards. Otherwise why would you spend the money, time, and effort on all this mess. So workflow has to be the BIG number 1 with a bullet. depending on the user's role at the moment - mixer, editor, post-pro, etc. I now think the ultimate control surface is a hybrid made up of various phones/pads/fader packs/scrub jog wheels, etc. As far as the ultimate control surface, I've been thinking about / working on this for over 10 years now - first programming I ever did in this space was the Faderport drivers for various DAWS in 2006.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |