Closed bjoluc closed 1 year ago
Thanks for flagging this @limageurpublic! I suspect this might happen due to duplicate internal MIDI Remote API port names. Let me write a potential fix tomorrow. When would you be available for testing it with your setup?
Hi, I'll be free between 11am and 15am max
Le jeu. 16 mars 2023, 21:08, bjoluc @.***> a écrit :
Thanks for flagging this @limageurpublic https://github.com/limageurpublic! I suspect this might happen due to duplicate internal MIDI Remote API port names. Let me write a potential fix tomorrow. When would you be available for testing it with your setup?
— Reply to this email directly, view it on GitHub https://github.com/bjoluc/cubase-xtouch-midiremote/issues/4#issuecomment-1472669413, or unsubscribe https://github.com/notifications/unsubscribe-auth/A55VOMRPMPLHK2HUJT2Q5STW4NXMVANCNFSM6AAAAAAV5VU5Q4 . You are receiving this because you were mentioned.Message ID: @.***>
:tada: This issue has been resolved in version 1.4.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
New issue...it seems like the script or cubase api "lost" the midi ports defined at the set up ! the midi ports were in and out in the same order at set up ... xtouch ext, xtouch, and Desktop.... but at the next start up of cubase project...the midi out ports seem to be unordered and, at this moment, the first extender ( called stouch-ext ) doesn't work properly anymore....it show the tarcks names but not colors....
Originally posted by @limageurpublic in https://github.com/bjoluc/cubase-xtouch-midiremote/discussions/1#discussioncomment-5334656