2 weeks have passed, so I am pinging again
2 more weeks. Stuck in lockdown, would love to be using Plex on Roku.
You are destroying your files - somehow.
The āsampleā above says itās an hour and 50 minutes long, but thereās nothing on it.
When I remux the file - itās now 1 second long - and thereās nothing on it.
I think whatever drawing board you were working on - go back there 'cause what youāre doing isnāt working. You may be destroying the samples. What Iāve seen so far isnāt media - and if it is, it needs to be longer than a second.
I took a Blu-ray MKV rip (which plays on RasPlex and VLC), and āddā the file head. Yes, the metadata says it is longer that the file actually has, but (for example) VLC plays the content in it.
Iāll try using mkvtoolnix
Remuxed with mkvtoolnix
Spider-Man-dbg-001.mkv.gz (24.3 MB)
Pinging this thread again.
I donāt even have an unpacker for that crap.
ā¦and Iām not going to get oneā¦
for a .gz? Thatās a standard compressed-file format for about 30 years now. Why does the site allow it if you wonāt deal with it? You want a zip? Here.
Spider-Man-dbg.zip (24.3 MB)
2 weeks later, pinging again.
I went and tried Emby, and while they have a bunch of other problems, they donāt seem to have THIS problem.
I have tested the sample, and every variation works for me.
Using a setup having support for DTS (global video quality set to original)
- Video direct played
- Every audio stream I choose worked, include the DTS-X (MA) audio - it was converted, or when I enabled the āAllow DTS-HDā option to pass the core through, it direct played.
Using a setup without DTS support (global video quality set to original)
- Video direct played
- All audio streams worked again, and the DTS streams were converted to AC3 5.1 audio.
Using a setup with lower quality settings (backed down from original quality)
- Full transcode worked properly, and could play option, while audio and video were converted.
Iām at a bit of a loss here, not having the ability to replicate the failure on a Roku. Possible Iām not replicating something in your client setup, of there is something going on with the synonolgy.
Could you follow the steps below so I can examine the client logs?
- Open the Plex channel
- Enable Remote Logging in the settings
- Attempt to play the video, and let it fail
- Disable Remote Logging
- Report back with the time/timezone and username if different than your forums user.
Weirdly, now this file plays. But the original still doesnāt (though behavior seems different - now it stalls for a second and then goes to the āPreviousā screen without trying to play the media.
I am trying to find a media file that fails and isnāt 23GB
I remuxed the whole 23 GB file, and bizarrely it seems to play now. What info can I provide to understand this?
I repeated this on another problematic title (Solo, 40 GB) and it ALSO works.
Something about the MKV file that MakeMKV produces makes Plex/Roku unhappy.
How can I find out more?
I ran mkvinfo on both, hereās the diff
remux.diff.txt (9.2 KB)
Any thoughts on this?
Ping?
I think the most interesting part of that diff might be this:
-| + Lacing flag: 1
The original file had lacing enabled, the remuxed one doesnāt.
Historically lacing hasnāt been a well-supported feature in players, and even the used-by-Plex-on-Android ExoPlayer struggled with it
This is amusing because they refer back to the Plex forums:
I donāt know if the Roku, specifically, has trouble with Lacing. I know that MKV lacing and compression are common container compatibility issues for dumb āsmartā devices. Thatās one thing that remuxing and āMKV Fixingā utilities often remove.
The newest version of MakeMKV is just a few days old. It might be worth trying that, to see if the behavior has changed.
Iām curious if your problem files all have Lacing enabled, and if your working files donāt.
Good idea. Latest MakeMKV still sets Lacing (I just tried re-encoding one). Some of the films that work do have Lacing set, and some do not. 
Darn! Yeah that was the biggest hole in the theory anyway - MakeMKV is super popular and there would be a lot more noise about this.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.