puithove 209 Posted December 27, 2016 Share Posted December 27, 2016 I'm continuing to setup an xbox to stream remotely. The other day the ET app was mostly working. Now suddenly it will not playback anything transcoded. Anything that can direct play plays fine. I had the UWP app installed also on my tablet. I launched it there and saw that it was working fine (in the same remote location with the xbox). The app showed as an update available - I downloaded the update, then it was doing the same thing as the xbox. So seems that something in the last update has broken things. Back at home, I'm able to reproduce the issue using the UWP app on my tablet, while on my local network. To reproduce (and these are the steps you'll see in the logs I posted): Use UWP app (either xbox or Windows 10 pc) Set bandwidth limit to force transcoding Browse to library content (movie or tv) - that is playable via direct play, and is under the limit - play content *** in the log this is "Ace Ventura" - played this for just a few seconds before stopping it - played fine *** Browse to library content that must be transcoded - play content *** in the log I waited several seconds before starting this second one - it is "Aliens" - did not play, just black screen in UWP app - had to kill the app *** What you will see: In the UWP app, once you hit Play, the screen goes black - no UI whatsoever - the info pane doesn't even come on the screen. At this point the app is hung. It does not respond to any input - so can not stop playback and back out. I have to quit the app by closing the window on Win10 or by hitting the xbox button and quit app on the xbox On the server dashboard, it shows the item is transcoding, but the timer never starts counting Transcode log progresses normally. Server log shows a websocket error right at the time that playback tries to start, every time. Dashboard: server-63618420345.txt ffmpeg-transcode-99acf9c5-194f-4105-9bac-b25d515f1f3a.txt Link to comment Share on other sites More sharing options...
puithove 209 Posted December 27, 2016 Author Share Posted December 27, 2016 I should also mention that without changing anything on the server side, I'm able to repeat the above steps in "Ember for Emby" and everything plays fine - transcoded and all. Link to comment Share on other sites More sharing options...
puithove 209 Posted December 27, 2016 Author Share Posted December 27, 2016 Oddly enough, LiveTV seems to transcode and play just fine. Link to comment Share on other sites More sharing options...
sualfred 677 Posted December 27, 2016 Share Posted December 27, 2016 (edited) Try switching to ffmpeg 3.1.6. This works on my side with the UWP app and software transcoding. Only HW accerlation failes -> The current version (1.1.47) has an issue with VAAPI transcoded videos, wich ends up in a black screen w. sound. Edited December 27, 2016 by sualfred Link to comment Share on other sites More sharing options...
Luke 37994 Posted December 27, 2016 Share Posted December 27, 2016 Yes there was a regression introduced in ffmpeg 3.2 that is affecting us. We have notified ffmpeg about it. Thanks. Link to comment Share on other sites More sharing options...
puithove 209 Posted December 27, 2016 Author Share Posted December 27, 2016 Ah, ok. That does appear to fix it. Thanks! Link to comment Share on other sites More sharing options...
SikSlayer 217 Posted December 28, 2016 Share Posted December 28, 2016 Where can I get this version of ffmpeg? I've had some issues I can't nail down enough to report on that I suspect may be the fault of ffmpeg. Link to comment Share on other sites More sharing options...
Luke 37994 Posted December 28, 2016 Share Posted December 28, 2016 Where can I get this version of ffmpeg? I've had some issues I can't nail down enough to report on that I suspect may be the fault of ffmpeg. The best thing to do is start by providing the information requested in how to report a media playback issue. thanks ! Link to comment Share on other sites More sharing options...
puithove 209 Posted January 13, 2017 Author Share Posted January 13, 2017 Yes there was a regression introduced in ffmpeg 3.2 that is affecting us. We have notified ffmpeg about it. Thanks. Was there any word back on a fix, or at least acknowledgement of an issue? There are some package dependencies on the specific ffmpeg version for my distro, so it's holding up other updates by having to roll this back. It's making me consider having to switch over to a docker container for Emby so it can have its own dependencies. Link to comment Share on other sites More sharing options...
Solution Luke 37994 Posted January 13, 2017 Solution Share Posted January 13, 2017 Yes, we submitted a patch, it was accepted and merged in. But I have no information on ffmpeg release schedules. thanks. 1 Link to comment Share on other sites More sharing options...
puithove 209 Posted January 14, 2017 Author Share Posted January 14, 2017 Yes, we submitted a patch, it was accepted and merged in. But I have no information on ffmpeg release schedules. thanks. That's what I needed though, thanks. Link to comment Share on other sites More sharing options...
Luke 37994 Posted January 14, 2017 Share Posted January 14, 2017 It might already be in the nightlies here: https://www.johnvansickle.com/ffmpeg/ Link to comment Share on other sites More sharing options...
puithove 209 Posted January 27, 2017 Author Share Posted January 27, 2017 FYI - I didn't want to wait any longer so I built my own from git master - what should become 3.2.3 - and it appears to be working well. Just wanted to pass that along. Link to comment Share on other sites More sharing options...
Luke 37994 Posted January 27, 2017 Share Posted January 27, 2017 Thanks for reporting. 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