I'll keep the description short. Working with a streamer using two rigs, Gaming Rig receives VBAN Audio from Streaming Rig. Streaming Rig cannot run VMR-Streamer and VBAN due to listen port conflict.

Symptom:

• With VoiceMeeter Potato v3.0.2.1 and VMR-Streamer from same
• "Primary" machine runs VBAN, Control -and- Incoming Stream, accepting both from "Secondary" machine
• "Secondary" machine runs VBAN Outgoing Stream to "Primary" machine (Audio Stream established and working)
• "Secondary" machine runs VMR-Streamer, properly configured for VBAN Control stream to "Primary" machine
• -- VMR-Streamer fails to connect
• "Primary" machine shuts down VoiceMeeter Potato (or disables VBAN)
• "Primary" machine runs VMR-Streamer, same configuration
• -- VMR-Streamer connects and works properly
• "Primary" machine restarts VoiceMeeter Potato (or enables VBAN)
• -- VoiceMeeter engine throws error, unable to start VBAN, Socket In Use.

Conclusion; VMR-Streamer opens a listen socket on the same port VBAN uses for incoming connections, fails without indication of cause when this socket cannot open (Message implies VBAN host is at fault)

Suggested fix; VMR-Streamer EITHER:

• A) Does not need any listen port (since it is not receiving connections) and should AVOID OPENING such
• B) Should not need the same listen port number and should acquire port number via RANDOM FUNCTION or ALLOW CONFIGURATION

Possibly relevant code; vban_cmd.c -- VBAN_InitSocket called by VBANCMD_StartThread

I can't get it to compile (very little Windows experience with C/C++ but plenty on the Linux side) or I would simply submit a PR.