@natemac, have you tried just remuxing the “broken” Futurama MP4 to an MKV? Many of the “not fast enough” errors people experience are with MP4 files, and just quickly remuxing them into an MKV makes it go away. Rather than spending a ton of time re-ripping your library with TunesKit trying to find the right formula, I’d just start by trying that with your existing files.
Thanks, how would one go about that?
This is getting really annoying now, after I saved the logs and restarted playback it did it again after about 5 minutes, I hope these logs are useful.
This is playing from a NUC over a gigabit wired lan, no WiFi.
rr.log (166.8 KB)
1-Plex Media Server.log (3.0 MB)
Thanks, @MxC_Trexx. I didn’t even know you could get logs from the player. I don’t have a Plex Pass and according to the link you provided you need a plex pass to get the beta’s unless I missed something. Here is the log from the Shield itself. I saw this in the log:
2-12 16:51:20.512 i: Showing toast: Your connection to the server is not fast enough to stream this video. Check your network or try a lower quality.
02-12 16:51:20.579 i: [Exo2VideoPlayer] Buffering has been notified.
02-12 16:51:20.581 i: [FF] ********************************************************
[FF] Statistics:
[FF] ********************************************************
State: Buffering Loading: Yes Auto Play: Yes
Surface: android.view.Surface
Position: 7:45 Duration: 2:19:57
Window Start: 0:00 Window End: 2:19:57 Position in Period: 0:00
Period Position: 0:00 Period Duration: -3:-12
Video: OMX.Nvidia.h265.decode
- Initialise Time: 45us Initialised: 1 Released: 0
- Input Buffers: 11161 Output Buffers: 11159
- Skipped: 0 Dropped: 0 Max Dropped: 0
Audio: OMX.google.raw.decoder - Initialise Time: 22us Initialised: 1 Released: 0
- Input Buffers: 34929 Output Buffers: 34929
- Skipped: 0 Dropped: 0 Max Dropped: 0
Memory Usage: 873.1133 / 2959.5508 Threshold: 216.0.
It always says “Your connection to the server is not fast enough to stream this video. Check your network or try a lower quality.” but it happens on everything. This file is 4K HDR but it happens on SD TV shows as well. It will never autoplay after this happens. I have to exit the file and start playing again.
logging.txt (1.2 MB)
1 Like
The easiest way is probably to just download MKVToolNix:
https://mkvtoolnix.download/downloads.html
Drop the MP4 file into it and then hit Start Multiplexing. Should take less than a minute. Then put that MKV on your Plex and test to see if it has the issue.
@rwoffice You win Plex master status.
At least the first test, putting the lossless rip though the remux let the Shield play it without issue and plenty of buffer.
@MwC_Trexx why would something like the remux fix this?
I just did one episode, we’ll start doing the rest shortly.
Thank you!
@natemac MKV is just a container/wrapper for the audio/video tracks.
The encoding of those tracks and time syncing of the audio/video is where most issues tend to come from.
Handbrake & Mkvtoolnix are established tools that have a long history and very active support/development community behind that to fix issues quickly that arise as well as add support for newer standards over time such as HEVC (h.265), etc.
So either tool would work fine for fixing your Tuneskit rips once Tuneskit had removed Apples DRM from the video files.
@natemac, the reason it works is because ExoPlayer v2 is borked in a litany of random ways, one of which is it throws out the incorrect and useless “not fast enough” message on some files, even though the underlying issue has nothing to do with your server speed or your available bandwidth. This seems to particularly affect MP4 and M4V files more than MKVs, though I’ve gotten it with both MKVs and AVIs as well.
So i tried playing an original iTunes rip MP4 using VLC and X-plore on the Shield over the network and those apps had no issue playing the video file unlike Plex.
@MwC_Trexx I posted both client and server logs from a session where this happened.
This happens with (as far as I can tell) any file, once it happens you hit stop and play again and it will continue playing (often from before the point it stopped).
If it were something wrong with the files then I would expect a given file to throw this message as exactly the same point every time, but it doesn’t, it’s random,
@xhonestly don’t worry about the beta, it doesn’t fix this issue.
@fizzyade I will try and get time to look at your logs today. Gets kinda crazy doing multiple peoples log in same forum post.
In terms of the file behaviour, if there was a “corrupt” spot in the file, then yes it would fail consistently at the same spot.
Based on the Nvidia post that I linked a few messages back, the issue will float all over.
From what it looks like, It is basically an issue with how the audio/video tracks are “interleaved” in the file. The Plex client is trying to fix the ordering, but depending on data rates, load on the Nvidia Shield, etc. where the issue flairs up will vary.
@natemac & @fizzyade - I have been chatting with a couple of the developers. Please do the following for me if you could.
@natemac - please take one of your Tunekit files and follow this process ( https://support.plex.tv/articles/201035968-generating-sample-files-from-media/#toc-2) to generate a sample media file from it. Add that file to your library and verify you still see the same issues with it.
@fizzyade please do the same with one of your problem files.
If both of those sample files show the issue, please PM them to me. I will get them to the Plex developers to help them work on the fix.
Their biggest problem right now is they can’t consistently reproduce the issue, which is making it challenging to work on a fix. They are working on some enhancements (no eta I can give you) that they think will help, but again until they can reliable reproduce the issue it is hard to fix it.
Doubtful a small section of the file is going to show anything, occasionally a file will play right through without issues, sometimes it might show the message after 10 minutes, might be an hour or occasionaly you might see it more than once playing the same file, rarely though.
To reproduce, you just have to let the shield continue playing until it happens, I’ve left it on and reproduced the issue, I see the problem at least once a day so your guys should be able to reproduce it, doesn’t seem to be file specific, plenty of my files will crap out and show the buffering message, but as I said earlier, never at the same point.
And just like that I got the buffering message 1 hour 7 minutes into ready player one.
I just repackaged one of my mp4’s into mkv and it worked flawlessly. Zero changes otherwise.
All of my rips are done with DVDfab and they all have the same problem since they’re always packaged in mp4.
Little inconvenient that mp4’s don’t work. I’m gonna be repackaging 10000 files for hours at this rate.
Describe your NW setup @fizzyade. Yours sounds like it might be a different issue.
UniFi switches, everything hard wired, NUC running PMS on Ubuntu 18.10 with media mounted via NFS4 using autofs from Synology DS916+.
Everything involved in the plex chain is hardwired with gigabit Ethernet. No WiFi involved.
Not sure if this has been seen by others…
Posted on the 25/1/2019
Blockquote
Quick update on the Plex issues with stuttering and server too slow messages while direct playing. We’ve gotten a few example files that reproduce this and have worked with Plex.
They’ve discovered the content that has these issues is muxed in a way where audio/video packets are out of order in the file and their play is trying to find time sequential packets for playbacks which causes a bunch of thrashing and causes the player not to be able to keep up with the stream at full rate and thus the pausing of videos or server too slow messages.
_They are working to figure out how to solve this by caching/improving the performance of this seeking. _
We don’t have an ETA on a fix yet, but this fix will likely come in the Plex client app itself and will be decoupled form SHIELD updates.
Blockquote
1 Like
Well that’s something at least.
