At this point, Plex just send an engineer to one of our houses with the issue and I’ll host the guy for a week at home to fix this crap for the team.
It is getting ridiculous now.
5 Likes
+90000
Same here. Constantly give error with speed even though I’m on 600mbps. Uninstaller update, currently <6.0 version and working fine.
I too am getting the error with speed issue. I was getting it on my shield and Fire TV sticks & Pendants. This was happening only with TV Shows and Movies I processed through M4VGear (purchased from iTunes store). They play just fine from my apple TV’s, iOS and web portal.
After some playing around I can get them to work by changing the CC option to “English (EIA_608)”. Not ideal because I get random CC stuff on screen when I don’t need subtitles at all. If I choose “NONE” for subtitles the shows will not play or I get the speed error.
Hopefully the devs can fix the issue and in the meantime maybe I can help others out with a temporary fix.
Plex,
Do you have an ETA on fixing this issue. The last release did not fix it.
I have found this error myself streaming 4k to my Roku. My fix is to switch the damn audio stream from TRUE-HD 7.x over to DTS 5.1 or ACC.
I think this message is misleading.
Try switching audio to acc or something lower if the video has it.
How is this still an issue? Both Plex and Nvidia have known about this for over a year. Plex staff above are still asking for logs, how are they not able to reproduce this internally in their lab environment?
1 Like
When is this going to be fixed??? I want my direct play back…my shield and Plex Pass are useless for months…
1 Like
Worked on by nvidia, probably fixed with the next public release on the Shield.
I have been getting this error on my Fire TV Cube. However, I’ve noticed it mainly happening at the END of a video file. The video plays perfect, but at the very last second of the video, it comes up with this connection error and the video doesn’t finish.
To my knowledge, my videos are playing at original quality, but it’s hard to tell because the Plex settings are disjointed and/or vague. Transcoder quality is “automatic” through the website, and Home Streaming is set to “Maximum” in the app itself. Does this mean it will play directly? (and why can’t I just access all settings in one place?)
Here’s the media info for one of the files that did this. I wonder if certain video file metadata is triggering this error?
Can we get an update on this?
2 Likes
Have the same problem on Nvidia shield Cannot play movies longer than 5-10 seconds.
1 Like
I saw something on the Nvidia Shield beta forums yesterday that seems to refer to this problem…
I signed up for the new build that they seemed to indicate might fix this. I really hope it does. Once I get the build and test it, I’ll post what I find.
Definitely fixed the issue for me
1 Like
Is that the 7.2.3+ build?
Where do you want the logs sent (all the information for attaching and sending in the link you posted is wrong or links broken)? This issue is well over a year old now. Apart from getting the message, the Plex client will also refuse to connect to the server when it’s launched for the first time, videos, regardless of resolution/complexity will transcode (they can be 720p or 1080p h264 mkv, 720 or 1080 MPEG2 TS (ATSC OTA) recording via Plex etc… Force-Quitting and restarting the app 5 or so times will usually allow these videos to Direct Play.
This happens on both my Shields running the latest release software. Refresh rate switching is NOT on and I believe Passthrough hasn’t made a difference. Both are wired to a GigE network.
No such problems from PMP on desktop/notebook or iOS player on iPhone and iPads.
Oh, and I’ve tested with two different server platforms too.
Originally Windows 7 with a Core2Duo @ 2.something GHz, 8GB RAM. Now on UnRaid with Docker running Dual 8-core Xeon E5-2650 v2 @ 2.60GHz with 64GB RAM
Taken from server log when getting the issue that prevents Direct Play:
Apr 28, 2019 13:36:11.903 [0x14928868d700] DEBUG - MDE: analyzing media item 11511
Apr 28, 2019 13:36:11.903 [0x14928868d700] DEBUG - MDE: Ponyo (2009): Direct Play is disabled
Apr 28, 2019 13:36:11.903 [0x14928868d700] DEBUG - MDE: Ponyo (2009): media must be transcoded in order to use the hls protocol
Apr 28, 2019 13:36:11.903 [0x14928868d700] DEBUG - MDE: Ponyo (2009): no direct play video profile exists for http/mkv/h264
Apr 28, 2019 13:36:11.903 [0x14928868d700] DEBUG - MDE: Ponyo (2009): no direct play video profile exists for http/mkv/h264/ac3
Apr 28, 2019 13:36:11.903 [0x14928868d700] DEBUG - MDE: Ponyo (2009): no direct play video profile exists for http/mkv/h264/ac3
I think you are confused about the issue here. The issue is not with server hardware or settings. Some of us have Enterprise grade hardware with dual 6 core Xeons and over 100 GB’s of RAM. The issue seems to be strictly with the Android Plex client streaming locally. I have Roku clients and they stream fine local or remote. I have both an XBone and a PS4 and the both work fine. The only clients that have problems are my Sony Android TV and my Fire TV Stick 4K.
3 Likes
@XweAponX, this is a well known bug with the software, and is acknowledged by both Plex and NVIDIA. The confusion is because of the terrible error message, which leads a lot of people down a troubleshooting path spending hours trying to fix something that they can’t fix.
2 Likes
