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

[Feature] Allow switching Key from web interface #16

Open
sreich opened this issue Jun 4, 2023 · 2 comments
Open

[Feature] Allow switching Key from web interface #16

sreich opened this issue Jun 4, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@sreich
Copy link

sreich commented Jun 4, 2023

I've really loved the web interface feature...I have the app hooked up to my computer and then i have my tablet show the chord interface while I practice in piano marvel and other spots.

This works super well and it wasn't even a feature I knew i wanted. but, i'd love to be able to switch certain settings from the server interface. Like what key it is in

@ArTiSTiX
Copy link
Contributor

Hello @sreich, sorry for late reply.

This is indeed something that i would like to do, but the issue is more due to the way i designed the Web interface with Websockets.
Currently, only MIDI messages are transmistted to the web interfaces, and read-only settings.

My next important update will be a rewrite of the midi routing, because of the issue you mentioned with ALSA, and the need to update JS dependencies, i will switch to a fork of node-midi which makes my connection strategy buggy.

Once this rewrite is ok, and 1.4.0 is published, i will start to work on v2.0.0 (complete rewrite of the app), but before v2, a few improvements could be done in the current modules.

I know that currently, having settings separated from the modules is a big UX issue, thus the need for a v2 of MIDI Jar.

And one of the improvement i have in mind is to have all "modules" of MIDI Jar kind of independant of each other, and working in both the Web interface and the Main window (and maybe some of them could directly be running on the backend side and transmit module-specific events instead of raw MIDI messages).

Also, i would like those modules to be arranged in a View, so that if you need a specific view in the web interface that is different of the main window, you could arrange things like you want, i.e.:

  • a key switch on the left of the keyboard, with the circle of fifths
  • 3 keyboards, all routed to a single chord display

This could help developing new modules, and use them in different contexts (my personal needs is to have different keyboard configurations in OBS, but currently there is only one config :( ).

@ArTiSTiX ArTiSTiX added the enhancement New feature or request label Jun 20, 2023
@sreich
Copy link
Author

sreich commented Jun 20, 2023

Excellent thanks, sounds very promising. I'm looking forward to the upcoming rewrites. Thanks for the design explains

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