You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Controller profiles: LC6000 as the first profile #43
The mapping becomes a named controller profile, so a later controller is a new profile file, not new code. v1 ships one profile, Denon LC6000 PRIME. The app shows which profile each controller uses.
Acceptance criteria
A profile has an id, a display name, the MIDI device name hints used to auto-match a connected device, and the mapping body that exists today.
The bundled LC6000 profile is the current default mapping, with its values unchanged.
A connected device whose name matches a profile's hints gets that profile. A device with no match is listed but not bridged, with a plain message.
Controller-specific behavior stays data-driven where it already is: relative jog encoding, 14-bit pitch, the LED color table and the pad notes. Anything that is still hard-coded to the LC6000 is listed in the PR as a follow-up, not generalized now.
Activity
Read the controller's profile, deck and devices from the Coordinator