Re: VBAN Stream on internet
Posted: Tue Dec 24, 2024 9:41 am
Don't think so, we are all running gigabit internet, wired connections, and in-home using gigabit as well.
Running about 10 megabit/s of data (both ingress and egress), and then running speedtests to the max capacity of our internet connections doesn't influence/hurt anything.
We did find that the change on powersettings of the NIC's in the PC made our connections MUCH more stable. We now rarely see issues where we used to have issues on a daily basis (issues only with VBAN's UDP traffic).
Is there anything we can do using wireshark to check for timing or packet loss issues of the UDP streams on tx and rx side when a stream is having issues?
From the manual:
ERROR LED: shown on the right are blinking red in case of reception errors:
1- Overload: we received too much packets (audio stream comes too fast)
2- Corrupt: we received corrupted packets
3- Disorder: we received older packets
4- Missing: we missed packets (lost)
5- Underrun: not enough packets received (audio stream comes too slow or is stopped).
We see issues 3, 4 and 5 happening, nothing improves when we change "net quality" (Fast, optimal, slow, etc).
Cheers,
David
Running about 10 megabit/s of data (both ingress and egress), and then running speedtests to the max capacity of our internet connections doesn't influence/hurt anything.
We did find that the change on powersettings of the NIC's in the PC made our connections MUCH more stable. We now rarely see issues where we used to have issues on a daily basis (issues only with VBAN's UDP traffic).
Is there anything we can do using wireshark to check for timing or packet loss issues of the UDP streams on tx and rx side when a stream is having issues?
From the manual:
ERROR LED: shown on the right are blinking red in case of reception errors:
1- Overload: we received too much packets (audio stream comes too fast)
2- Corrupt: we received corrupted packets
3- Disorder: we received older packets
4- Missing: we missed packets (lost)
5- Underrun: not enough packets received (audio stream comes too slow or is stopped).
We see issues 3, 4 and 5 happening, nothing improves when we change "net quality" (Fast, optimal, slow, etc).
Cheers,
David