Cubase randomly swaps MIDI ports #4
Comments
|
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
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A55VOMRPMPLHK2HUJT2Q5STW4NXMVANCNFSM6AAAAAAV5VU5Q4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
github-actions bot
pushed a commit
that referenced
this issue
Mar 17, 2023
## [1.4.1](v1.4.0...v1.4.1) (2023-03-17) ### Bug Fixes * Make MIDI port names unique to fix an issue where Cubase would randomly swap identically named MIDI ports (such as multiple extender ports) ([b7a0659](b7a0659)), closes [#4](#4)
|
🎉 This issue has been resolved in version 1.4.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #1 (comment)
The text was updated successfully, but these errors were encountered: