It’s called latency or ping. There’s relays and routers that pass data where it needs to go. Everything in between the request device and the supply device adds to it. Furthermore, data is still a physical object that requires time to travel. The longer the distance, the more time it takes to get where it’s going. That’s simple physics.
latency and ping has absolutely nothing to do with video quality. the quality as it’s received by the client is going to be the exact same. You’re not losing data in the process. it’s not like a container ship that’s traveling across the ocean and for every 100 miles it travels it loses a container. If you’re getting buffering then sure, maybe you’re calling that ‘quality’ but it absolutely is not what anyone else means when they say quality.
It absolutely can. If you are accessing a server that is farther away, it has to traverse more distance on the wire and it takes more routers to pass the packets. The more hops you have, the more latency you have, especially if you get routed through a slower or overly congested link. All of that factors into the tcp window size, which can affect the transcode quality you receive.
absolutely not… you can travel literally a thousand miles without hitting a router if you’re traveling transcontinental, whereas if you’re in a dorm in college and you live right next to an T1 node you can be hitting 15 different routers because your college actually uses a virtual network provider from the other side of town.
Hops absolutely does not correspond to distance in any reasonable sense. Youtube also buffers to avoid that transcode quality issue, so no you’re getting the quality you ask for, but the bitrate might be different depending on your physical internet speed. The distance has jack shit to do with it.
Wut. Quality has absolutely nothing to do with distance to the cdn server. That makes no sense whatsoever.
It absolutely does…
It’s called latency or ping. There’s relays and routers that pass data where it needs to go. Everything in between the request device and the supply device adds to it. Furthermore, data is still a physical object that requires time to travel. The longer the distance, the more time it takes to get where it’s going. That’s simple physics.
latency and ping has absolutely nothing to do with video quality. the quality as it’s received by the client is going to be the exact same. You’re not losing data in the process. it’s not like a container ship that’s traveling across the ocean and for every 100 miles it travels it loses a container. If you’re getting buffering then sure, maybe you’re calling that ‘quality’ but it absolutely is not what anyone else means when they say quality.
It absolutely can. If you are accessing a server that is farther away, it has to traverse more distance on the wire and it takes more routers to pass the packets. The more hops you have, the more latency you have, especially if you get routed through a slower or overly congested link. All of that factors into the tcp window size, which can affect the transcode quality you receive.
absolutely not… you can travel literally a thousand miles without hitting a router if you’re traveling transcontinental, whereas if you’re in a dorm in college and you live right next to an T1 node you can be hitting 15 different routers because your college actually uses a virtual network provider from the other side of town.
Hops absolutely does not correspond to distance in any reasonable sense. Youtube also buffers to avoid that transcode quality issue, so no you’re getting the quality you ask for, but the bitrate might be different depending on your physical internet speed. The distance has jack shit to do with it.
Lol, ok.