Icon Platform M+ MIDI Remote - version 4.0.0.rc1 Release Candidate

I just checked and the code only uses mFocusedQuickControls. So it will be whatever is in focus - so instrument controls when focus is on an instrument and track controls when on a track. At least it should be - unless there is a lock active in Cubase or something isn’t refreshing when the focus changes. I can’t test it myself right now but have noted the issue in my dev logs.

These are midi remote project, setting, script update, json config caching issues. The README.md file contains my attempt at getting a consistent method to get Cubase, including the currently open project, to refresh everything if you replace the midi remote script. It is still hit and miss. During development I tend to:

  1. Replace the script
  2. Open a project
  3. If the script has no errors it will usually initialise - with the incorrect midi ports assigned even though the icon will become active and move faders (only some ports are broken).
  4. Hit midi remote refresh scripts button
  5. 3 will happen again
  6. Chances are there will be a Shadow (disabled) icon midi remote as well as the newly initialised one (with incorrect ports)
  7. Remove the Shadow one
  8. Remove the one that says it is “working” - I usually use the Pop up window with the midi remotes in it to remove it since during dev I have it open.
  9. Delete the MIDI Remote\USers Setting\bfc_platformplussd_…json file.
  10. Re-add the control surface with correct midi ports - this time it should come up fully correctly
  11. Save the Project

Sometimes this will result in the project having the new setting embedded. Sometimes it doesn’t. I’ve never figured out a reliable way to get Cubase to update to what the actual script says when it is updated. The cached Json (step 9) will update as well during midi remote script reload (which is why its important to remove it, in case it decides to use it after the main script is updated).

It’s very annoying to say the least. My theory is that some part of the midi remote mapping is being stored in the Project file, and isn’t always updated when the script is.

On this aspect I don’t know what else to do. It appears to be outside the scripting control.