ddurdle 75 Posted May 16, 2018 Share Posted May 16, 2018 Is there a way to force direct stream on chrome client's (or other web clients that still allow for direct play) for Live TV playback? Link to comment Share on other sites More sharing options...
Luke 37024 Posted May 16, 2018 Share Posted May 16, 2018 Well it should already be whenever possible. Can we please look at an example? Thanks ! Link to comment Share on other sites More sharing options...
ddurdle 75 Posted June 28, 2018 Author Share Posted June 28, 2018 I think my original question was mis-read. I have a STRM file. I want to force direct stream or transcode when I play it back with emby chrome. right now, it always goes to Direct Play. I have a 29MBps bitrate file which stutters badly with Direct Play. I have tried setting both the user's profile and server profile maximum Internet streaming rate to 1MBps, but it always chooses Direct Play. Link to comment Share on other sites More sharing options...
Luke 37024 Posted June 28, 2018 Share Posted June 28, 2018 The reason the server value doesn't apply is because this is a remote domain. However the app setting should apply. We'd have to look at an example. Thanks. Link to comment Share on other sites More sharing options...
ddurdle 75 Posted June 28, 2018 Author Share Posted June 28, 2018 By app settings, do you mean this? Link to comment Share on other sites More sharing options...
Luke 37024 Posted June 28, 2018 Share Posted June 28, 2018 Yes. Link to comment Share on other sites More sharing options...
ddurdle 75 Posted June 29, 2018 Author Share Posted June 29, 2018 I was trying to capture some logs to post here and ran into some inconsistencies so I need some confirmation before I try to recapture results. Does the web chrome emby use different logic on different OSes? What about chrome vs chromium? Link to comment Share on other sites More sharing options...
Luke 37024 Posted June 29, 2018 Share Posted June 29, 2018 Well the browser reports to us what is supported so that can make a difference. Link to comment Share on other sites More sharing options...
ddurdle 75 Posted June 29, 2018 Author Share Posted June 29, 2018 (edited) I'm capturing the logs but here is what I'm seeing. I tried to change my test case by using a movie encoded with VC1. In chromium on linux I can see it starts back automatically with transcode (as expected). If I switch audio tracks during playback, I can see it continues to transcode (looking at emby dashboard and in stats for nerds) but switches the audio track, as expected. On Windows and on Mac, with Chrome with the same file. If I start the file with the defautl audio track (track 0), it plays back with transcoding, but if I switch audio tracks, I see the status switch to "direct play" in both status for nerds and in the emby dashboard for a brief second before it returns "no compatible streams" error. On the server side, I can see the transcode request receive and is serviced to the client. But for some reason, the client is switching to Direct Play in this case. It is also true that when I startup the movie by selecting that second audio track on startup rather then switching to it during playback, the video starts with "Direct Play" as reported in the emby dashboard (I obviously can't see the same in stats for nerds since I can't get to playback to get to that option). I can see the request in the server for transcoding, and I see ffmpeg is triggered and starts to transcode. From the backend server, the linux, mac and windows playback requests all show up identical with transcoding invoked and stream delivered to the client. But it seems on Windows/Mac with chrome, it stumbles and gets confused and thinks it is Direct Play. This seems to be happening only when tested on Chrome on Windows and Mac. I am to understand correclty that VC1 should trigger transcode on these two platforms, correct? I also tested on emby for roku and it works as expected (like the linux chromium test) -- it transcodes and switching audio tracks works. I'm going to test on mobile chrome and then post the server logs. Is there anything on the client end that I can capture for the bug report? Edited June 29, 2018 by ddurdle Link to comment Share on other sites More sharing options...
Luke 37024 Posted June 29, 2018 Share Posted June 29, 2018 Server log is enough, thanks. Link to comment Share on other sites More sharing options...
ddurdle 75 Posted August 5, 2018 Author Share Posted August 5, 2018 I upgraded to 3.5.2 on a test server and it is working correctly. Transcode is automatically triggering with chrome based on the user's playback preference and likewise if the audio codec is not supported (on 3.3.x, DTS wouldn't trigger transcode, so there would be no audio playback unless you toggle the transcode by force). Link to comment Share on other sites More sharing options...
Luke 37024 Posted August 5, 2018 Share Posted August 5, 2018 Thanks for the feedback ! 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