logo

Live Production Software Forums


Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

2 Pages<12
Options
Go to last post Go to first unread
admin  
#21 Posted : Saturday, December 14, 2024 7:09:48 PM(UTC)
admin

Rank: Administration

Groups: Administrators
Joined: 1/13/2010(UTC)
Posts: 5,227
Man
Location: Gold Coast, Australia

Was thanked: 4332 time(s) in 1528 post(s)
We do not recommend changing Windows network settings, as this could mess up things even more.
As this issue only effects a very small number of YouTube streamers and not any other streaming providers, a change on the computer side of things is unlikely to help.

One test you can try is to ping a.rtmp.youtube.com from the command line:

Quote:
ping a.rtmp.youtube.com

Pinging a.rtmp.youtube.com [142.250.67.12] with 32 bytes of data:
Reply from 142.250.67.12: bytes=32 time=17ms TTL=115
Reply from 142.250.67.12: bytes=32 time=16ms TTL=115
Reply from 142.250.67.12: bytes=32 time=16ms TTL=115
Reply from 142.250.67.12: bytes=32 time=16ms TTL=115

Ping statistics for 142.250.67.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 17ms, Average = 16ms


One theory is it relates to specific servers in specific locations, as a.rtmp.youtube.com automatically routes to what it thinks is the nearest server using a process called "Anycast".
If the ping times are quite high (>100ms) then it indicates YouTube is not picking the best server for your location.
thanks 1 user thanked admin for this useful post.
congoblue on 12/16/2024(UTC)
bulent_atlas  
#22 Posted : Monday, December 16, 2024 1:14:36 AM(UTC)
bulent_atlas

Rank: Newbie

Groups: Registered
Joined: 10/21/2022(UTC)
Posts: 9
Turkey
Location: ankara

Thanks: 4 times
Was thanked: 1 time(s) in 1 post(s)
Originally Posted by: admin Go to Quoted Post
We do not recommend changing Windows network settings, as this could mess up things even more.
As this issue only effects a very small number of YouTube streamers and not any other streaming providers, a change on the computer side of things is unlikely to help.

One test you can try is to ping a.rtmp.youtube.com from the command line:

Quote:
ping a.rtmp.youtube.com

Pinging a.rtmp.youtube.com [142.250.67.12] with 32 bytes of data:
Reply from 142.250.67.12: bytes=32 time=17ms TTL=115
Reply from 142.250.67.12: bytes=32 time=16ms TTL=115
Reply from 142.250.67.12: bytes=32 time=16ms TTL=115
Reply from 142.250.67.12: bytes=32 time=16ms TTL=115

Ping statistics for 142.250.67.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 17ms, Average = 16ms


One theory is it relates to specific servers in specific locations, as a.rtmp.youtube.com automatically routes to what it thinks is the nearest server using a process called "Anycast".
If the ping times are quite high (>100ms) then it indicates YouTube is not picking the best server for your location.


ping a.rtmp.youtube.com

Pinging a.rtmp.youtube.com [216.58.214.140] with 32 bytes of data:
Reply from 216.58.214.140: bytes=32 time=84ms TTL=56
Reply from 216.58.214.140: bytes=32 time=73ms TTL=56
Reply from 216.58.214.140: bytes=32 time=84ms TTL=56
Reply from 216.58.214.140: bytes=32 time=85ms TTL=56

Ping statistics for 216.58.214.140:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 85ms, Average = 81ms
bulent_atlas  
#23 Posted : Monday, December 16, 2024 1:18:08 AM(UTC)
bulent_atlas

Rank: Newbie

Groups: Registered
Joined: 10/21/2022(UTC)
Posts: 9
Turkey
Location: ankara

Thanks: 4 times
Was thanked: 1 time(s) in 1 post(s)
We have been broadcasting 10 hockey games a day on the same network via Blackmagic Web Presenter for 9 days. But when I try to stream via Vmix, it doesn't take more than 2 minutes for me to go to yellow. I don't think the problem is with YouTube. I think the problem is related to Windows.
STADIORADIO  
#24 Posted : Monday, December 16, 2024 8:09:57 AM(UTC)
STADIORADIO

Rank: Advanced Member

Groups: Registered
Joined: 10/1/2013(UTC)
Posts: 196
Man
Location: Bovalino (Italy)

Thanks: 86 times
Was thanked: 3 time(s) in 3 post(s)

I find myself in the same conditions. Network on 4G LTE modem, speed test with excellent performance, like 40 mega down 40 up. Until last week everything was ok, today I find myself doing a live broadcast and after a few minutes the vmix stream flashes. If I stop everything and restart, it starts fine then after a few minutes it flashes again. I had to lower it to 1.5 megs to finish the transmission. I also have win10.
ckvideo  
#25 Posted : Monday, December 16, 2024 10:22:05 AM(UTC)
ckvideo

Rank: Member

Groups: Registered
Joined: 3/21/2022(UTC)
Posts: 24
Germany

Thanks: 1 times
Was thanked: 4 time(s) in 4 post(s)
Originally Posted by: nerdygirljoni Go to Quoted Post
I'm getting so frustrated and losing money. Does anyone know how to debug if a windows update is causing "real time buffer full" error? I'm more on the creative end of things and not so much the technical stuff so I don't even know where to begin, or what to say to viewers /big cry shrug/


Hi,

things are complex, so lets try to break it down:

  1. You need a stable network connection. Fiber or copper DSL is best, WiFi is a no-go and mobile networks can be tricky.
  2. Make sure you stream with constant bitrate (CBR) activated. If you don't, traffic shaping in the providers backbone can do all strange things. Cutting video from Powerpoint still slide to a moving crowd will most certainly create a hiccup in the upstream. Bitrate will rise, traffic shaping does not keep up and vMix can not transmit its video buffeers, you get the dreaded orange flashing.
  3. RTMP is no good, even if YT and lots of others support only this. RTMP is 20 years old, runs on TCP and is brittle in mobile networks, unstable networks and across continents. It gets worse with higher bitrates as well. The reaseons are complex, but unfortunately the problem is there. (Read this for details.
  4. In short: Use RTMP only up to 6-8 Mbit/s, use it on the same continent, use it on stable networks. Do intensive tests.
  5. On mobile networks, use SRT to get into the "real" Internet. You can set up a instance of DataRhei Restreamer on a VPS and go from there via RTMP to YT or other ingest points.
  6. Bandwidth tests are not enough. They help to set your bitrate - do not use more than 75% of what the speed test gives you. The other killer are jitter and packet loss. Try this website with Chrome/Edge and the proper parameters to get an idea how good your uplink is.
  7. If you stream to a Wowza server, make sure all the buffer parameters for ingest are set up correctly.


On mobile networks:

  1. Use 5G if you can.
  2. Measure the available bandwith and adapt your upstream bandwidth accordingly.
  3. Use HEVC instead of H.264, if possible. Same quality, less bandwidth.
  4. Use SRT. Use SRT. Use SRT. :-)
  5. If you use bonding technology, understand how it works and do extensive tests. Use SRT.



Sorry that this is not easier, but hopefully these points may help you a bit.

Good luck and let us know how is goes.

Christian

admin  
#26 Posted : Monday, December 16, 2024 11:55:42 AM(UTC)
admin

Rank: Administration

Groups: Administrators
Joined: 1/13/2010(UTC)
Posts: 5,227
Man
Location: Gold Coast, Australia

Was thanked: 4332 time(s) in 1528 post(s)
Originally Posted by: bulent_atlas Go to Quoted Post

Pinging a.rtmp.youtube.com [216.58.214.140] with 32 bytes of data:
Reply from 216.58.214.140: bytes=32 time=84ms TTL=56
Reply from 216.58.214.140: bytes=32 time=73ms TTL=56
Reply from 216.58.214.140: bytes=32 time=84ms TTL=56
Reply from 216.58.214.140: bytes=32 time=85ms TTL=56

Ping statistics for 216.58.214.140:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 85ms, Average = 81ms


This is interesting as it indicates Google is doing anycast via DNS instead of by IP.
(The IP here is different to what we see in our tests from Australia for example)

You can try setting your DNS servers in Windows to the Google DNS as per the following, then reboot and see if the ping has better results:

https://developers.googl...ed/public-dns/docs/using
Users browsing this topic
Guest
2 Pages<12
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.