MSattler 390 Posted March 11, 2016 Posted March 11, 2016 So this happened a couple times tonight. Playing back an episode via Roku and playback freezes. Stop, restart and it plays fine. Here is the log: http://pastebin.com/sJUS4pSw Do the ffmpeg process still throttle when using QuickSync? I thought it wasn't because with 3 streams going one froze, but I noticed the same show froze 3 times, perhaps it's something with that particular stream? Thanks!
MSattler 390 Posted March 11, 2016 Author Posted March 11, 2016 yea it does still throttle with quicksync Are the parse errors in that log potentially related to the freezes? I'll check the server log as well to see if there is anything there.
Luke 42083 Posted March 11, 2016 Posted March 11, 2016 no, my only guess is maybe the gpu just can't handle 3 simultaneous encodings.
MSattler 390 Posted March 11, 2016 Author Posted March 11, 2016 Are the parse errors in that log potentially related to the freezes? I'll check the server log as well to see if there is anything there. Found this in the server log, I can post the whole thing if you want. Am I reading this right as in the roku stopped playback? Right @ 10:26. Thanks! 2016-03-11 22:25:53.5444 Info HttpServer: HTTP Response 204 to 70.106.193.146. Time: 0ms. http://emby.marcusrocks.com:8096/emby/Sessions/Playing/Progress?itemId=9fbaebbe5ab25265ad1066498731bd02&PositionTicks=9260000000&isPaused=false&canSeek=true&PlayMethod=Transcode&QueueableMediaTypes=Video&MediaSourceId=9fbaebbe5ab25265ad1066498731bd02&PlaySessionId=53de8e2a64c64a10b33a06a18a9c2da2&AudioStreamIndex=1 2016-03-11 22:25:55.8390 Error SessionWebSocketListener: Unable to find session based on web socket message 2016-03-11 22:25:57.5579 Info HttpServer: HTTP POST http://emby.marcusrocks.com:8096/emby/Sessions/Playing/Progress?itemId=9fbaebbe5ab25265ad1066498731bd02&PositionTicks=9260000000&isPaused=false&canSeek=true&PlayMethod=Transcode&QueueableMediaTypes=Video&MediaSourceId=9fbaebbe5ab25265ad1066498731bd02&PlaySessionId=53de8e2a64c64a10b33a06a18a9c2da2&AudioStreamIndex=1. UserAgent: Roku/DVP-7.0 (047.00E09044A) 2016-03-11 22:25:57.5579 Info HttpServer: HTTP Response 204 to 70.106.193.146. Time: 0ms. http://emby.marcusrocks.com:8096/emby/Sessions/Playing/Progress?itemId=9fbaebbe5ab25265ad1066498731bd02&PositionTicks=9260000000&isPaused=false&canSeek=true&PlayMethod=Transcode&QueueableMediaTypes=Video&MediaSourceId=9fbaebbe5ab25265ad1066498731bd02&PlaySessionId=53de8e2a64c64a10b33a06a18a9c2da2&AudioStreamIndex=1 2016-03-11 22:25:58.0908 Info HttpServer: HTTP SUBSCRIBE http://192.168.1.125:8096/dlna/69251f6cc4ad96a5320ed9c78345f822/contentdirectory/events. UserAgent: 2016-03-11 22:25:58.0908 Info HttpServer: HTTP Response 200 to 192.168.1.29. Time: 0ms. http://192.168.1.125:8096/dlna/69251f6cc4ad96a5320ed9c78345f822/contentdirectory/events 2016-03-11 22:25:59.8254 Error SessionWebSocketListener: Unable to find session based on web socket message 2016-03-11 22:26:00.6848 Error NotFoundHttpHandler: [::ffff:192.168.1.125]:8096 Request not found: /web/index.html 2016-03-11 22:26:00.7786 Error NotFoundHttpHandler: [::ffff:192.168.1.125]:8920 Request not found: /web/index.html 2016-03-11 22:26:01.5443 Info HttpServer: HTTP POST http://emby.marcusrocks.com:8096/emby/Sessions/Playing/Progress?itemId=9fbaebbe5ab25265ad1066498731bd02&PositionTicks=9260000000&isPaused=false&canSeek=true&PlayMethod=Transcode&QueueableMediaTypes=Video&MediaSourceId=9fbaebbe5ab25265ad1066498731bd02&PlaySessionId=53de8e2a64c64a10b33a06a18a9c2da2&AudioStreamIndex=1. UserAgent: Roku/DVP-7.0 (047.00E09044A) 2016-03-11 22:26:01.5443 Info HttpServer: HTTP Response 204 to 70.106.193.146. Time: 0ms. http://emby.marcusrocks.com:8096/emby/Sessions/Playing/Progress?itemId=9fbaebbe5ab25265ad1066498731bd02&PositionTicks=9260000000&isPaused=false&canSeek=true&PlayMethod=Transcode&QueueableMediaTypes=Video&MediaSourceId=9fbaebbe5ab25265ad1066498731bd02&PlaySessionId=53de8e2a64c64a10b33a06a18a9c2da2&AudioStreamIndex=1 2016-03-11 22:26:03.8285 Error SessionWebSocketListener: Unable to find session based on web socket message 2016-03-11 22:26:04.7661 Info HttpServer: HTTP POST http://emby.marcusrocks.com:8096/emby/Sessions/Playing/Stopped?itemId=9fbaebbe5ab25265ad1066498731bd02&PositionTicks=9260000000&isPaused=false&canSeek=true&PlayMethod=Transcode&QueueableMediaTypes=Video&MediaSourceId=9fbaebbe5ab25265ad1066498731bd02&PlaySessionId=53de8e2a64c64a10b33a06a18a9c2da2&AudioStreamIndex=1. UserAgent: Roku/DVP-7.0 (047.00E09044A) 2016-03-11 22:26:04.7661 Info App: Killing ffmpeg process for B:\Users\Administrator\AppData\Roaming\Emby-Server\transcoding-temp\2b51fdc43e748dddded5c248399be353.m3u8 2016-03-11 22:26:04.8140 Info App: FFMpeg exited with code 0 2016-03-11 22:26:04.8140 Info App: Deleting partial stream file(s) B:\Users\Administrator\AppData\Roaming\Emby-Server\transcoding-temp\2b51fdc43e748dddded5c248399be353.m3u8
MSattler 390 Posted March 11, 2016 Author Posted March 11, 2016 no, my only guess is maybe the gpu just can't handle 3 simultaneous encodings. Potentially, but one of the transcodes was about 20 minutes ahead of playback...... which would make me think it would have paused to catch up the one behind the most. This is on a i7-6700 processor, if it cannot handle 3 simultaneous encodings... then really GPU transcoding is a bust in many use cases.
MSattler 390 Posted March 11, 2016 Author Posted March 11, 2016 Potentially, but one of the transcodes was about 20 minutes ahead of playback...... which would make me think it would have paused to catch up the one behind the most. This is on a i7-6700 processor, if it cannot handle 3 simultaneous encodings... then really GPU transcoding is a bust in many use cases. @@Luke the <ThrottleDelaySeconds>180</ThrottleDelaySeconds> config in the config file, does that mean after 180 seconds the ffmpeg pauses or is that the period of time it will pause? Trying to determine the logic we are using to pause ffmpeg, to see if it needs to be adapted for gpu transcoding use cases. Thanks!
Luke 42083 Posted March 11, 2016 Posted March 11, 2016 it means that it has to be ahead by that amount and yes, i see throttling in your log.
MSattler 390 Posted March 11, 2016 Author Posted March 11, 2016 it means that it has to be ahead by that amount and yes, i see throttling in your log. I found this, http://www.intel.com/content/dam/www/public/us/en/documents/white-papers/cloud-computing-quicksync-video-ffmpeg-white-paper.pdf and while I'm not using that Xeon processor I am using an i7 which is newer and should provide similar performance. They mention 9 h264_qsv encodes at once, at medium preset. I'm not sure how that compares to what Emby is using.
MSattler 390 Posted March 11, 2016 Author Posted March 11, 2016 (edited) So I turned off throttling and I think I am actually getting a better experience, not freezing. Will have to continue to test. With throttling off, if a client disconnects or stops playback the ffmpeg process still stops right? I'm thinking that perhaps it will work better because it will just speed through the transcoding. I'll have to keep playing around with it. Edited March 11, 2016 by MSattler 1
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