(no title)
aldarisbm | 1 year ago
Maybe I just don't have the right combination of devices, and/or I absolutely need a wired connection. Regardless, I could not stop thinking how having physical media would avoid these drops.
aldarisbm | 1 year ago
Maybe I just don't have the right combination of devices, and/or I absolutely need a wired connection. Regardless, I could not stop thinking how having physical media would avoid these drops.
Dalewyn|1 year ago
You do.
criddell|1 year ago
> https://electronics.sony.com/bravia-core
> 7: The Pure Stream™ feature requires an Internet speed of at least 43 Mbps. To enjoy at the highest speed of 80 Mbps, you need an Internet speed of 115 Mbps or faster. Ethernet (wired LAN) connections are limited to 100 Mbps due to the TV's product specifications. Therefore, to enjoy 80 Mbps with Pure Stream™ functionality, you need to connect to a Wi-Fi router that supports IEEE 802.11 ac/n (wireless LAN).
NovemberWhiskey|1 year ago
everforward|1 year ago
I find it roughly equal as things go.
The buffering thing genuinely confuses me. I get why it happens at a technical level, but the failure mode is odd. None of the content is live, just buffer the next 5 or 10 minutes to disk and have the player read from the disk buffer.
That should never buffer unless the network is degraded for a long while.
The full solution would be to just let people cache the entire video and watch directly from disk, but I believe that’s intolerable to the IP folks.
Macha|1 year ago
But the original DASH implementation was very aggressive about keeping a minimal buffer size and downgrading quality at the slightest hiccup. I was also on a not particularly great internet connection at the time, so I used to pause 720p at the start and let it buffer enough for uninterrupted playback, but YouTube's changes meant that just buffered like 15s and then shifted down to 360p. There were add-ons to force dash off to mitigate the problem but iirc YouTube was starting to make higher qualities dash exclusive.
Clearly someone at YouTube was optimising to reduce time-to-play and buffering but in a typical metrics driven approach, excluded the possibility that for some videos these were less bad problems than 360p videos. At that time I was watching a lot of let's plays and programming tutorials and most of the people were uploading content recorded and intended for 720p or 1080p, so unreadable text because of quality downgrades was a big problem for me at that time.
Nowadays I just brute force it by having comically excessive amounts of internet (2gbps ftth) so YouTube randomly deciding garbage quality is much rarer, but it still happens sometimes.
actionfromafar|1 year ago