-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Restore Connection After Device Reboots - force client UDP port #117
Comments
Hi! Thanks for the report! I just implemented it in the statemachine branch. It's still not ready for master, but I think it already behaves better in some cases. It just need more testing. It adds a I will think a way to have more consistent ports for autodetected (mdns/zeroconf) peers. Ideally for rtpmidid as client there is a way to always send from the same port for all clients.. but needs more work. Anyway note for myself, it should be possible having an udp router that has the real connection and redirects the data to the peers based on initiator_id or ssrc. Can you try to compile and test it? |
So I'm fairly novice at compiling and doing command line stuff. How do I install this latest release you mentioned? What commands do I need? |
This will work for debian based distros. Other are similar:
Alternative you can try There will be a new release soon, I hope, but there are still some bugs to fix. |
I’m trying to have my Linux device automatically connect to an iConnectivity RTP port whenever one or the other powers off. The problem is, with my Linux device set as the initiator, the 5-digit port changes on every connection. With the other device as initiator, it connects but I have to manually select from the newly created ports in the MIDI menu. And it keeps creating ports.
What do I need to do in the ini file to get this working?
Thank you in advance if you have time to answer!
The text was updated successfully, but these errors were encountered: