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] Enable a way to renumber / remap groups in generated GTBs for MIDI 1.0 devices especially #208

Open
Psychlist1972 opened this issue Jan 12, 2024 · 0 comments
Assignees
Labels
area-service-or-api 🖥️ Related to the Windows Service, core API, abstractions, etc. area-user-tools ⚙️ Related to the user-focused tools like Settings feature request 💡 New feature request or proposal under consideration 🤔 Features under consideration

Comments

@Psychlist1972
Copy link
Contributor

The cable numbers we map to groups may not always result in an appropriate MIDI CI pairing. There will be times when the user needs to be able to remap these through the settings application.

This may require generating function blocks (and having a service-side responder for it) as well as message translation, and use that information to override the Group Terminal Blocks.

This may be useful for MIDI 2.0 devices, but the priority is MIDI 1.0 devices.

@Psychlist1972 Psychlist1972 added feature request 💡 New feature request or proposal area-user-tools ⚙️ Related to the user-focused tools like Settings area-service-or-api 🖥️ Related to the Windows Service, core API, abstractions, etc. under consideration 🤔 Features under consideration labels Jan 12, 2024
@Psychlist1972 Psychlist1972 self-assigned this Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-service-or-api 🖥️ Related to the Windows Service, core API, abstractions, etc. area-user-tools ⚙️ Related to the user-focused tools like Settings feature request 💡 New feature request or proposal under consideration 🤔 Features under consideration
Projects
Status: No status
Development

No branches or pull requests

1 participant