Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using the qwerty keyboard to input midi notes in step input mode. #1255

Open
toadzrock opened this issue Dec 12, 2023 · 2 comments
Open

using the qwerty keyboard to input midi notes in step input mode. #1255

toadzrock opened this issue Dec 12, 2023 · 2 comments

Comments

@toadzrock
Copy link

Having the qwerty to input provides an additional option for users.

"Steal" the 2 rows of keys starting with Q, and A, when step input mode is selected, releasing the keys back to normal when step input is turned off.

So A would be C, W would be C sharp, S would be D, E would be D sharp, and so on, emulating the staggered positioning of back and white notes on a musical keyboard for 12 notes ranging from A to B on the qwerty.

The user would enter step input mode, and input with the qwerty, with the playback cursor stepping forward by grid to the end of the note just entered, in place for the next intended note entry.

Q is for rests, by grid, and would simply advance the playback cursor to the next intended note entry point. The user can still use the existing keys to advance (+) or rewind (-) the PB cursor as he or she desires.

2 additional keys raise and lower the "live" octave, so if P and L are those keys, pressing P once would move the live octave from starting at C3, to C4. Pressing L once would lower the live range, by octave.
There should be an indicator of some sort that specifies which octave is currently live.

This is a common practice among other daws as well, so the learning curve is reduced for those new to this type of inputting, but when implemented well, offers a fast and mouse free workflow, particularly for larger projects.

Alex.

@terminator356
Copy link
Member

Yes this was also brought up a few weeks ago, I can't remember where.

I mentioned that since many keys are already used - even in step mode,
a new special 'PC mode' button would turn on the PC keyboard so that all keys would
be re-directed to operate sounds.
Then turn off the 'PC mode' button to go back to normal.

@toadzrock
Copy link
Author

toadzrock commented Dec 12, 2023

Aaah, ok, sounds like a plan. Can I assume PCmode would only operate within the PR, and if the user closes the PR window, or escapes the PR window focus, PCmode automatically reverts to "normal"? (In case the user forgets to turn off PCmode before shutting the window, or navigating away from it for a moment.. A safety feature of sorts)

I think it's also worth keeping the transport controls outside of PR mode, so the user can stay in PC mode, inside the PR window, and audition what he or she's written.

Can I suggest the User having the choice to add or remove keys to/from PCmode, outside of the keys i've already mentioned? A good example is the NumPad keys which are usually allocated to selecting grid/note lengths, and the keys for navigating the PR canvas, including those you've just added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants