Motivation
I find Dorico input to be very non-intuitive. That’s partly due to prior experience with other software, and partly due to my background in UI design that goes back a long way.
Goal
To create a method of input that lets me take advantage of all the other cool stuff in Dorico. It would be great if I could create something that is shareable when done, but primarily I just need a usable workflow.
Ground rules
I would like to keep this thread free of lengthy defenses of why my requirements are the way they are. I could discuss that elsewhere if you like, or you can feel free to opt out.
Requirements
This is an inital draft and will likely be updated.
R1 Common* entry tasks must be achievable with one hand.
R2 All entry will be done on a 34-key keypad. It will be programmable by QMK/VIA so that the key-codes being sent don’t have to be the ones marked on the physical keys.
R3 Pitch will not be selected by note name or MIDI keyboard.
R4 Modifier keys may not be required for common tasks but are welcome for uncommon ones. An exception will be made for core CUA* commands. (In conjunction with R2, a single press on the keypad may send a modified key-code so long as the user doesn’t have to press it.)
NON-requirements
N1 The commands do not have to align with any particular software’s existing input method, they can be entirely new.
N2 I don’t care about which comes first, pitch or duration - ideally I could change either as often as I liked before proceeding to the next note, but that is NOT a requirement.
Definitions
- Common tasks are those needed to input or edit the pitch and duration of notes in a single layer of one staff: this must include dots, accidentals, and tied values (especially those that are not possible via dots.) It also includes navigating among the notes of that layer/staff.
- CUA is the original standard for basic editing keys; e.g. CTRL-C for copy or CTRL-Z for undo.