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

Chord Display keyboard range #12

Open
MusicMan74 opened this issue Nov 9, 2022 · 1 comment
Open

Chord Display keyboard range #12

MusicMan74 opened this issue Nov 9, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@MusicMan74
Copy link

Hello and thanks for Midi Jar!

It would be very practical IMO to have a chord/melody split point. (i.e. A4)

This way I can display my entire keyboard range (i.e. C2 thru C6) but notes above (i.e.) A4 are NOT included in the chord calculation. Additionally, I would like to highlight the melody notes with a different color (ignored by the chord calculation, and played with right hand).

@MusicMan74 MusicMan74 added the enhancement New feature or request label Nov 9, 2022
@ArTiSTiX
Copy link
Contributor

ArTiSTiX commented Nov 9, 2022

Thanks @MusicMan74 for the suggestion, i like the idea.

This could be done indeed, but i don't know when this would be shipped, though.
It makes me think that it may also have some interesting synergy with other useful features like Splitting midi.

One approach could be to simply add a split note (or start/end notes for chord range) and display other as melody.
But this is pretty limiting in terms of feature and future involvments.

Another approach could be to have a different routing logic and modules, one output module for "displaying" notes on a keyboard, and the chord-display module for the chords.
Then the chord-display keyboard could display both messages (like 2 separate MIDI devices), and i could introduce the MIDI split feature in the Routing module so that you could choose to split your keyboard, and send different parts to different output.
Or have 2 stacked keyboard and still be able to differentiate the "chords" keyboard from the lead keyboard.

I'll think about it in the next few days (MIDI advanced routing is one of the milestones i would like to achieve, like splitting / mapping notes, redirect MIDI ports, and remap values like velocity and such).

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

No branches or pull requests

2 participants