Support JACK MIDI input for shared midi
Bug #1890910 reported by
Milkii Brewster
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
There is currently no mechanism to combine signals from two MIDI controllers so that one controller can control another.
My specific use-case is having a 4-deck toggle button on a nanoKONTROL2 for a Numark DJ2GO without further sacrificing any of the limited buttons/functions available in the compact DJ2GO mapping.
If Mixxx used JACK MIDI, each controller profile enabled in the config UI could get a JACK input port, allowing the user to forward MIDI commands from additional sources to be interpreted by that mapping.
Revision history for this message
| Daniel Schürmann (daschuer) wrote | #1 |
| summary: |
- JACK MIDI input? For >1 integrated controllers + Support JACK MIDI input for shared midi |
| Changed in mixxx: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| tags: | added: jack midi |
Revision history for this message
| Swiftb0y (swiftb0y) wrote | #2 |
| lock status: | Metadata changes locked and limited to project staff |
To post a comment you must log in.
I am not sure if this is the best solution for this use case, but a Jack Midi input can be helpful to control Mixxx and a third party application at the same time.
For you use case, I propose the workaround to use controls from unused Samplers or such to share data between the two mappings for instance [SmaplerX], hotcue_y_clear.
I will rephrase the bug title for the general case.