Msc dev #68
Open
Msc dev #68
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
*msc messages are saved and handled as hex string, easier to read than int in this special case
Open
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.
this adds MSC (Midi Show Control) to Action Cues and to the Cue Controller Protocols.
*MscMessage: write MSC messages
*MscParser: parse MSC messages
*session wide MSC Input is skipped for now (REST API)
*Keys are stored in hex sequence strings, like F0 7F 00 02 01 01 33 00 32 F7 (Generic Lighting, GO, Cue 3 Q_List 2), because they are easier to read, then the data fields of a mido sysex message.
Also most of hardware manufacturers of lighting equipment refer to these kind of notation.