IMHO, the problem lies at the venue site. If the Riviera doesn't have the capacity to handle that kind of stream, then it is not going to be received well by anybody, no matter what connection or browser you have.
If the evening of the finals, there was another event going on simultaneously that was using the Riviera's connection, that would diminish the capability of the finals to be streamed live.
I am no computer guru, but I think therein lies the problem -- at the Riviera -- and not the streamer themselves. They can't help it if the Riviera's connection sucks.![]()
Guru or not you are right. It has to deal with their upload bandwidth. The mistake they made with the stream was to not cap the users watching it. This seems like a crappy thing to do, but it keeps a maximum number of people watching it problem free.
It's not like that. Basically when someone streams to a ton of people, they have a few ways of doing it. But the big guys use multicasting, which is very efficient. Probably kozoom does too.
Normally if information gets sent on the internet, there are computers that route the information between the sender and receiver. Several of them. Like there's gonna be 18 hops between when I post this and when it arrives at azb. Most of these hops are servers whose main job is to route information. They don't really do anything else. And they have various schemes for doing it more efficiently. But it's their job to figure out where the info needs to go and forward it in an efficient way.
When people don't use multicast, they send it multiple times to multiple targets and each server routes all the info to all the receivers. Basically, even though the information is the same (it's the exact same streaming video and audio) it gets routed independently as if there were 1,000 separate streams to a 1,000 separate people.
When multicast is used, they send to a limited set of receivers and those random internet servers do the work of splitting up the same single stream to broadcast to the 1,000 viewers. There are fewer hops in between and the work of getting it to the viewers is offloaded to those servers out there... rather than having the original sender do all the work.
I may be wrong on this... but probably the riviera is not at fault and has nothing to do with it. They send it the stream out efficiently using multicasting, and various ISP servers then do the work of farming it out to individual viewers. Some ISP servers do this well and send it out efficiently. Others not so much.
I don't think there will be an easy fix like "just upgrade the facilities at the venue" or "decrease the number of viewers by making it PPV". If it simply got slower and slower as more and more people watched, there wouldn't be anyone with a perfect stream. If it were just a question of geography (like the guy who gets it in 12 hops will have a better stream than the guy who gets it in 19) then I would have had a crappy stream, being really far from vegas.
I think it's just a general limitation of streaming. Every time I've been part of some live stream (not just pool-related stuff) a few people are going to get lemons and complain. It may or may not be fixable at the ISP's end. Probably not.
I am not the biggest expert on streaming here and I'm working with limited info so I freely admit I may be full of it on this one![]()
It's not like that. Basically when someone streams to a ton of people, they have a few ways of doing it. But the big guys use multicasting, which is very efficient. Probably kozoom does too.
Normally if information gets sent on the internet, there are computers that route the information between the sender and receiver. Several of them. Like there's gonna be 18 hops between when I post this and when it arrives at azb. Most of these hops are servers whose main job is to route information. They don't really do anything else. And they have various schemes for doing it more efficiently. But it's their job to figure out where the info needs to go and forward it in an efficient way.
When people don't use multicast, they send it multiple times to multiple targets and each server routes all the info to all the receivers. Basically, even though the information is the same (it's the exact same streaming video and audio) it gets routed independently as if there were 1,000 separate streams to a 1,000 separate people.
When multicast is used, they send to a limited set of receivers and those random internet servers do the work of splitting up the same single stream to broadcast to the 1,000 viewers. There are fewer hops in between and the work of getting it to the viewers is offloaded to those servers out there... rather than having the original sender do all the work.
I may be wrong on this... but probably the riviera is not at fault and has nothing to do with it. They send it the stream out efficiently using multicasting, and various ISP servers then do the work of farming it out to individual viewers. Some ISP servers do this well and send it out efficiently. Others not so much.
I don't think there will be an easy fix like "just upgrade the facilities at the venue" or "decrease the number of viewers by making it PPV". If it simply got slower and slower as more and more people watched, there wouldn't be anyone with a perfect stream. If it were just a question of geography (like the guy who gets it in 12 hops will have a better stream than the guy who gets it in 19) then I would have had a crappy stream, being really far from vegas.
I think it's just a general limitation of streaming. Every time I've been part of some live stream (not just pool-related stuff) a few people are going to get lemons and complain. It may or may not be fixable at the ISP's end. Probably not.
I am not the biggest expert on streaming here and I'm working with limited info so I freely admit I may be full of it on this one![]()