-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MIDI communication issues with rtpMIDI #27
Comments
I have resolved the problem and it is not related to the script itself. Obviously, the script does a much quicker communication than the Mackie controller, which I have used before in Cubase. Therefore the response did not came in the right timing (I guess). I have finally change the communication speed of rtpMIDI. This fixed all issues, like wrong fader position and not responding controllers. Maybe this is an helpful information for other users, who are using the X-Touch via ethernet. So I apologize for any confusion. |
This is awesome news @Pendejo10 – thanks so much for sharing it! I've heard of similar issues from other rtpMIDI users, so your finding might also help them (@JDubs73?) 🎉 |
@bjoluc I set the "Standard-Bitrate" to 250000. Important to know is, that there is a bug in the UI of rtpMIDI. The bitrate is not reflected in the UI properly, although the value is set to maximum it always shows the lowest value. But if it has been set once, the value is stored correctly. |
I appreciate the tips, thanks!
|
🎉 This issue has been resolved in version 1.10.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Configuration:
Cubase 13.020
Main Device with two extenders connected via ethernet using rtpMIDI
Device: {"extender", "extender", "main"}
Everything seems to be connected very well, parameter are set correctly on all controllers (rarely a fader is wrong) but one of the three controllers cannot send any parameter to the DAW (no Fader, buttons nor pan)
In most of the cases it is the first extender, which cannot send parameter but it is always reflecting the correct status, e.g. if I click "Solo" on another controller the mute state appears on all controllers correctly.
The reload of the script in the MIDI Remote Manager doesn't help.
The text was updated successfully, but these errors were encountered: