Support high-resolution (14-bit) MIDI CCs. #15
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This comes in a few places: - firstly, adding six bytes to the memory map to store the 32 bits of data describing which faders are high-resolution. - secondly, reading/writing high-resolution data to both USB and TRS as appropriate - thirdly, handling the new data in save/load. It's not particularly attractive, but I believe it works just fine.
infovore
changed the title
BasicalLy: - the index of the loop is stepping through physical faders... - ...but we care about logical controllers, which alter when rotated - working out if a fader is high-res or not should respect that.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a new option to send 14-bit midi data from 16n; this is a companion to this PR in the editor software