Icon Platform M+ MIDI Remote #15
Open
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
Start button and Led now work WIP Still getting CC messages from Jog wheel (works but CC messages pass through to track?)
Start of SelectedTrack page
…nge the button usage: - touch a fader is select track - Sel button is now Monitor Enable - Push a Pan encoder and it will open Channel Settings Window - and it might even be programmed to shift to a suitable page to edit it but I don't know yet.
…ey are not bound on a page
…ave Send and Focus QC. and EQ1-4 on/off. plus basic channel controls for mute solo etc.
|
Just wondering if any of these PRs will ever be reviewed and added to the user library? |
…on was to unreliable for my taste As a result the Master Fader is now ALWAYS the AI control
…on first line will show the current Zoom function for the jog wheel - it will only be correct when either of the zoom buttons are first pressed. When the buttons are disabled it will return to Z (unfortunately). As soon as you activate again it will be Z - zoom, or N - Nav depending on what the actual underlying state is (which is flipped by pressing both Zoom buttons at the same time as shown on the Platform M+ display) The second line last letter will show S (Scrub) or J (Jog) when the Zoom lights are both off and the Jog wheel is pushed. Thus showing what mode you are in. WIP - trying to figure out if there is a way to do this more sanely. Unfortunately the MCU setting for zoom is only sent when zoom is first activated. This needs to be translated into some form of state machine in MIDI Remote script.
…on midi remote scripting quirks.
…value - few changes elsewhere to deal with quirks of midi remote
…y need to duplicate a line
Update to use fader Touch for Cubase 13.x
…dated. Probably need to rethink the display handling, it is to messy to see what the issues are.
Tried some new things for understanding.
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 is an Icon Platform M+ (in MCU Mode) Midi remote script with:
Known Issue:
When first started in any new session the Midi Remote will show correctly but when a function is pressed (e.g. select Channel when on the Mixer Page, or simply select a channel in Cubase with the mouse) the Midi Remote will grey out and disconnect.
When this happens selecting a Channel in Cubase (or pushing one of the remaining controls active in the Midi remote on the transport section) will refresh the midi remote - ALL functions will then work normally for the rest of the session.
I'm of the view this is a Bug in the Midi Remote engine as its completely reproducible in other midi remote script implementations. Looks to me like something is not being initialized correctly and it takes a couple of channel selections to fix it.
I've also noticed when first connected the midi remote will initialize to Mixer Bank 1, even if your Selected Channel in Cubase is in a completely different bank.
Definitely have some additional features I'd like to see (multi track automation so I can selected 4 tracks (SATB) and then have QC1/2 for Selection 1, QC1/2 for Selection 2 ... That way I can automate an SATB instrument section all in one hit. Be great to have the ability to map to/from CC's in general rather than just QC (though I do like QC for fader automation of course. - which reminds me, I need to check if QC automation works with Note Expression and similar note+CC editing functions. Gonna be a pest for orchestral expression if they don't!).
Great start thought, really looking forward to more.
Cheers,
Rob