pcm2a 9 Posted March 19, 2019 Share Posted March 19, 2019 For this issue the media is on a remote Emby server via Emby Connect where I do not have access to the server logs. When playing some shows I can only scrub in little increments 10-60 seconds and if I leave the show and resume it always starts back at the beginning. The issue does not occur on the web browser or Android TV Emby. Here is the details from one example show: Media Info lethal weapon S02E21 - transcode 1080p Video Title1080p H264 CodecH264 Codec tagavc1 AVCYes ProfileHigh Level40 Resolution1920x1080 Aspect ratio16:9 AnamorphicNo InterlacedNo Framerate23.976 Bitrate2,928 kbps Color primariesbt709 Color spacebt709 Color transferbt709 Bit depth8 bit Pixel formatyuv420p Ref frames1 NAL4 Audio TitleEng AAC stereo Default Languageeng CodecAAC Codec tagmp4a ProfileLC Layoutstereo Channels2 ch Bitrate127 kbps Sample rate44,100 Hz DefaultYes Containermov Size961 MB Any ideas why it works on other platforms but not Roku? Link to comment Share on other sites More sharing options...
ebr 14913 Posted March 19, 2019 Share Posted March 19, 2019 If the server does not have an accurate duration for an item, it won't be able to resume it. I believe this can happen with strm media. Link to comment Share on other sites More sharing options...
pcm2a 9 Posted March 19, 2019 Author Share Posted March 19, 2019 This is a bug that only plagues the Roku clients? It is working great on android and web browser. Link to comment Share on other sites More sharing options...
Senna 368 Posted March 19, 2019 Share Posted March 19, 2019 If the server does not have an accurate duration for an item, it won't be able to resume it. I believe this can happen with strm media. Isn't it, that the Roku Client reports back the media info to the server of non-probed strm media, when the client plays it ? On iOS and tvOS, my strm media that isn't probed yet, always report back ALL the media info to the server, including the duration, when those clients play it. Link to comment Share on other sites More sharing options...
pcm2a 9 Posted March 19, 2019 Author Share Posted March 19, 2019 Looks like it knows the length to me, at least on the server. Link to comment Share on other sites More sharing options...
ebr 14913 Posted March 19, 2019 Share Posted March 19, 2019 Since you didn't provide us with any specifics from this playback, I'm just making blind guesses... Link to comment Share on other sites More sharing options...
pcm2a 9 Posted March 19, 2019 Author Share Posted March 19, 2019 Without being able to access the remote servers logs what information can I provide besides what is on the screen? Are there some Roku logs that would provide more information? Link to comment Share on other sites More sharing options...
ebr 14913 Posted March 19, 2019 Share Posted March 19, 2019 You could send a log from the app but seeing an ffmpeg log from the server would tell us more probably. Link to comment Share on other sites More sharing options...
pcm2a 9 Posted March 19, 2019 Author Share Posted March 19, 2019 How do I pull a log from the roku client to attach here? Link to comment Share on other sites More sharing options...
ebr 14913 Posted March 19, 2019 Share Posted March 19, 2019 You don't. You send it from the app. Instructions are in our standard doc: How to Report a Problem Thanks. Link to comment Share on other sites More sharing options...
speechles 1917 Posted March 20, 2019 Share Posted March 20, 2019 (edited) What happens if you use "playback correction" while it plays. Does this cause the item to be seekable? It might be we are (directstream/remux) copying the video stream and because this is an in-progress live stream it might not allow seeking very well. If you use playback correction it should start a full transcode and allow seeking. Also seeing ffmpeg logs would be a big clue as to what is going on. If you use the Beta version of the Roku app this has an option called stats-for-nerds you can enable. This will also help diagnose what is going on. Edited March 20, 2019 by speechles Link to comment Share on other sites More sharing options...
pcm2a 9 Posted March 20, 2019 Author Share Posted March 20, 2019 Playback correction didn't make any difference. I ran a test and then submitted the logs from the Roku app. Username: pcm2a Time: 11:06 AM CST Show: Lethal Weapon S02E22 Screenshot showing the bad scrubber: Screenshot of the OSD that shows the correct time: Screenshot from Emby Beta of stats for nerds: Link to comment Share on other sites More sharing options...
ebr 14913 Posted March 20, 2019 Share Posted March 20, 2019 Emby knows the runtime because we probed this item at some point. It looks like the Roku player, however, does not. It looks like it is treating it as a live stream. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now