Skip to content

Conversation

@rhgg2
Copy link

@rhgg2 rhgg2 commented Jul 12, 2025

I have a Novation LaunchKey mk4. It can transmit 14-bit fader and encoder data, and uses an MSB/LSB encoding via CC parameters separated by 20h. This is captured perfectly by the FaderportClassicFader14Bit message generator type.

However, the FaderportClassicFader14Bit message generator uses a one-byte key, which means that it hogs all possible CC parameters on a given channel. The Novation sends slider data for multiple faders and pots via MSB/LSB CC pairs on the same channel, and as such does not work with the FaderportClassicFader14Bit message generator as it stands now.

As far as I can tell, there is no reason for this message generator to use only a one-byte key. This pull request updates it to use a two-byte key, which means that it works not only with the Faderport Classic, but also the Novation range. (Actually, there are now two two-byte keys: one for the MSB and one for the LSB.)

@rhgg2 rhgg2 force-pushed the faderport14update branch from 0e34eb6 to a66df0c Compare July 12, 2025 09:46
@rhgg2 rhgg2 force-pushed the faderport14update branch from a66df0c to ce98749 Compare July 12, 2025 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant