I sideloaded the 6.12.0 version, and it’s back to direct playing everything for me. I tried the new 6.16.2 today, and it was still broken. Plays for about 5 seconds, and the buffer runs out and says it can’t be direct played. Seems that 6.12.0 is the answer for now, at least for me.
Has this issue been acknowledged by Plex at all?
I am surprised people having it on nVidia Shield.
I am running latest PMS on Synology NAS and Plex Client on SHIELD and on Sony TV.
SHIELD - all OK
Sony TV - lagging. (buffering) if bitrate is higher than ~35000kbits
PS: MX Player doesn’t buffer on SONY. It plays smooth even ~70000kbits bitrate files.
@mmhorda said:
I am surprised people having it on nVidia Shield.
It doesn’t seem to be related to the processing power of the player. I am the OP and I definitely see the issue on my Shield, which is one of the most powerful streaming boxes available. It’s been reported that the issue started when Plex switched to ExoPlayer, but Emby also uses ExoPlayer yet doesn’t suffer from this buffering issue. I’ve been using it for the past ~2 months with no issues. It was annoying to switch over, yes, but the lack of a fix from Plex even after all this time would seem to validate my choice. Can’t really complain as Plex is free (Emby charges a small fee for the client apps), but for me it’s worth the price of 2 coffees to have a working media management solution. Perhaps precisely because the app is paid, the Emby team also seems more responsive to user requests and issues reported on their forums.
I am in no way affiliated with Emby; just reporting my findings in case they may benefit others who are frustrated by the lack of a fix from Plex.
yes I understand but I have nVidia Shield too and I do not have such issue there. I am watching quite heavy files. Instead I have buffering issues on SONY Android TV.
It is either I have some beta version where it is already fixed for SHIELD or the problem is somewhere else.
It has nothing to do with the files, it has to do with player being broken. Just read the previous page of this thread, downgrade to 6.12, and turn off auto updates until some time in the distant future when they fix it.
@rwoffice said:
It has nothing to do with the files, it has to do with player being broken. Just read the previous page of this thread, downgrade to 6.12, and turn off auto updates until some time in the distant future when they fix it.
Exactly. I have confirmed and reproduced this with a selection of different media files.
I have 20Mbps home internet connection and I’m streaming from a 20Gbps dedicated server. Using the latest PMS (1.13.0.5023).
Nvidia Shield Client 6.13> (exoPlayer2): max bitrate achieved without a ‘network not fast enough’ message is 1080p 8Mbps dropping to 720p 4Mbps on occasions.
Nvidia Shield Client 6.12 (exoPlayer): a steady 1080p 12Mbps with no ‘network not fast enough’ message.
The issue definitely lies with the player or there’s some sort of overhead that’s been miscalculated into exoplayer2’s profile on the PMS.
Seems like my same issue I have with the Tivo app as well as FireTV. This really needs a fix from Plex fast!
Just cancelled subscription - kids haven’t been able to watch anything on our FireTV or FireStick for 3 months now. Has been a great 3 years - but time to go I think.
@tfatman said:
Just cancelled subscription - kids haven’t been able to watch anything on our FireTV or FireStick for 3 months now. Has been a great 3 years - but time to go I think.
I don’t understand these posts at all. Why are you sitting around for 3 months with a broken client when there’s a hundred posts saying to just downgrade to 6.12 and you can have a working client again? I understand why you would drop Plex Pass in protest since the bug isn’t getting fixed, but I don’t understand why anybody is intentionally suffering with an unusable client when you can just “fix” it yourself in like 5 minutes.
Pro Tip to Everyone: If you’re one of the seemingly thousands of people having the Not Fast Enough error, the Lost Connection error, the Skips to Next episode error, or any other bug that was introduced with ExoPlayer v2 at the beginning of February and still hasn’t been fixed, then do yourself a favor and just downgrade your client to 6.12 and end your suffering until the devs get around to fixing the problems.
@rwoffice said
downgrade your client to 6.12 and end your suffering until the devs get
around to fixing the problems.
This is true, and a solid workaround, but I think there is major frustration since there are 5 revisions (counting 6.17 beta) since all these issues started, but no successful fixes, and little if any acknowledgement that the devs are making any progress or for that matter that they are actually working on the issues…
I personally feel they forgot the golden rule “if its not broke, don’t fix it” and should have not switched to exoplayer in the first place. I am holding at 6.12 and testing each new revision I can hoping.
I don’t disagree with you at all. In another thread I even went so far as to collect media info from multiple users and track down the source of one of the issues, and I’ve provided plenty of logs and screen shots for my own problems. If they would just acknowledge these issues as even existing in the first place I think that would go a long ways, but the silence is deafening. They’ve even stopped bothering to ask for logs or samples, which to me means they either don’t care, or don’t have any idea what’s wrong.
My point in the above post was only to say to users that 3 months later if you’re still facing these issues then you must be a masochist because you’re intentionally suffering with a broken client since you very well know you could just quickly solve all of your problems by reverting.
6.18 version finally doesn’t force transcoding with turned on subtitles but still buffering on Sony Android TV. Works perfectly on SHILED with HDR and high bitrate videos, no buffering.
@mmhorda said:
6.18 version finally doesn’t force transcoding with turned on subtitles but still buffering on Sony Android TV. Works perfectly on SHILED with HDR and high bitrate videos, no buffering.
Is that in beta?
@jpirotte said:
Is that in beta?
I think it is beta yes.
@mmhorda said:
6.18 version finally doesn’t force transcoding with turned on subtitles but still buffering on Sony Android TV. Works perfectly on SHILED with HDR and high bitrate videos, no buffering.
That would be great news, I hope it’s true. Thanks!
I hope Devs or moderators won’t be too mad. As this is a third place i am leaving logs at.
I really hope someone can find it and check what is wrong with it.This issue continues since v6.13 (downgrading to v6.12 solves the issue).
Seems like nobody is actually looking at this issue at all and never will.
Clearly there is a difference with buffer between version 6.12 and all the rest after it.
Something actually happened recently (maybe latest PMS version made it a bit better but still far from perfect)
Okies - so I figured out that side loading on FTV was not painful - thanks @rwoffice
First thing I tried was 7.0.2 - on the off chance that something was fixed. Issue still exists - the only way to get a movie to play with out the “not fast enough” error is to force a transcode - regardless of quality (1080p high bit rate down to 480p low bit rate) anything that tries direct play fails with the “not fast enough” issue - if a play media that requires a transcode, or drop the playback video quality to force a transcode things work ok. If I can figure out how to get player logs out of the FireTV I’ll post them. The error is 100% repeatable (annoyingly).
Am taking advice and sideloading 6.12 for now.
@tfatman said:
Am taking advice and sideloading 6.12 for now.
This is the only solution right now.
All what you’ll probably loose is subtitles (you will have to switch them off) if you will want direct play.
