I’m trying to figure out how the Now Playing state works with regards to buffering.
I forced my Android client to the maximum quality and then tried to stream remotely to force a buffer event to see if it shows as “buffering” in Now Playing like I’ve seen before.
While the phone was buffering all the time not once did I see it showing as “buffering” in Plex Web’s Now Playing, the state was always “Playing”.
I repeated the process using Plex/Web for playback with the same result, constant buffering on the client but Now Playing just says Playing.
When are buffer events triggered? I’m pretty sure it used to happen but I can’t seem to be able to trigger it myself. Does it only trigger if the CPU cannot keep up with transcoding?
These tests were done with the PMS preview build 0.9.12.10 (the Android test) and using 0.9.12.8 when doing the test in Plex Web. Both are Centos 64 bit servers.
TIA
Update:
I simulated a slow connection by adding a limiter to my router and then streaming from a remote server. These are my results.
Clients that DO show buffering state:
Roku (Preview Channel)
PHT (Mac)
iOS
Clients that DO NOT show buffering state:
Android (never shows buffering)
Plex Web Chrome (seems to show when starting a stream but then not again)
Plex for Samsung Smart Hub (thanks davehobson)
Plex for Windows Phone (thanks davehobson)
Those are the only clients I have now to test with.
The windows 8.1 app gives a connection too slow message in the app itself, but I haven’t checked in Now Playing to see what it says. I’ll see if i can repro and report back.
Both Android and the web app also show a warning on the client side when the connection is too slow.
Would be great to hear from a ninja on this. I just want to know if this something the client needs to do on it’s end or if this something the server is currently trying to detect and is there a internal issue on this?
I know this is an old post, but on sync’ed music on an iOS client (iPhoneX in this instance) i get alerts from PlexPY that each track is buffering. I get approx 5 alerts per track. Not sure why the client would indicate its buffering locally stored content though.