Incoming Streams - None

[Vincent Burel]

so, we have here a mysterious problem we never got before.

However there is a strange point in your message:
you are talking about 192.168.1.xxx computer and 192.168.0.xxx one
but i see only 192.168.0.xxx in the Host Address list in your posted VBAN Dialog box screenshot.

[sjc-or]

Any other ideas Vincent? All addresses are 192.168.0.x so 192.168.1.x must be a typo. My two computers are 192.168.0.134 and 192.168.0.136. They are connected via an ethernet unmanaged switch.


The interesting thing but I don't know if it helps if I set GB2 on and change the address from 192.168.0.136 to 192.168.0.255, then GA1 comes alive for about 60 seconds and then goes dead again. I know this is not a legal configuration but it is the only way I can see any action on incoming on the main computer.

I also looked at the configuration XML files and couldn't find any anomalies. I know the two computers can talk in both directions since VBAN chat is working fine. This whole configuration has been working for a long time and then just stopped a few days ago so I just upgraded both computers to the latest version to see if that would fix things but it didn't.



Steve

[sjc-or]

More information

For VBAN chat, it only works from 136 (game) to 134 (main) if 134 first sends a message to 136. After that it keeps working so there seems to be something with the initialization routine if I send first from 136 to 134 .

After the first message is sent from 134 to one 136 it works for a while but then nothing from 136 to 134. I'm not sure how long it takes before it stops working from 136 to 134 but at least 1 minute so maybe 1 1/2 minutes. Then if I send from 134 to 136 again, everything works in both directions

134 = 192.168.0.134
136 = 192.168.0.136

[Vincent Burel]

could you go in command prompt and type "ipconfig" in each computer and share the result here.

[sjc-or]

Here are the screenshots.

ipconfig-main.PNG (25.66 KiB) Viewed 19520 times

ipconfig-game.PNG (46.76 KiB) Viewed 19520 times

[Vincent Burel]

ok, IP are ok.

according your last description of the problem, it seems there is something limiting the bandwidth on our UDP protocol.
maybe the nature of the network has been changed on one of the computer (public / private) - sometimes causing strange network problem.

you may try to change the UDP port , at least to force the network permission question (a dialog box should appear to let you authorize Voicemeeter to use the network - for public and private network).

[sjc-or]

Would this be applicable if the firewall is off? I've tried many other UDP ports with no luck. I have not changed network configuration as it has always been set to private.

Steve

[Vincent Burel]

ok, could you post the screenshot of the Voicemeeter System settings dialog box of the PC not detecting stream (134) ?

[sjc-or]

Here you go.

Main-System-Settings.PNG (104.34 KiB) Viewed 19509 times

[Vincent Burel]

ok, i see nothing wrong, i've no more idea except to use another ethernet switch ... or check wire connection (plug).