ffmpeg issue

[jasonmcroy 316]

I am running server Version 3.0.5724.3.

 

I have had an issue where sometimes ffmpeg isn't stopping by itself sometimes. It seems random and I am not sure what device may be causing it since I have used my Shield TV device and my Samsung tablet with the Emby app today while watching football and moving around to various rooms in my house.

 

The last device I used was the Samsung tablet, so maybe that it what app was using ffmpeg. I had to kill it manually in the task manager to get it to stop.

 

I noticed this a couple of different times in the last 5 days and it seems only related to watching Live TV.

 

Here is my latest log:

 

server-63577706908.txt

 

transcode-52b56beb-41c8-4c77-8498-196459fd432e.txt

 

Update with more data:

 

I just looked in my transcoding folder and it is full of images. Based on the image it has to be the app on my Samsung tablet. I had to delete those files manually as well.

Edited September 13, 2015 by jasonmcroy

[Jen25 34]

i've had this problem for a while now also.  nice to see you're getting the usual amount of help around here.

[chef 3810]

Maybe they need to build the version of ffmpeg.exe with the name "ffmpeg(transcode).exe"

 

Then use that version when transcoding, and when it fails, they can search the processes for that version name to stop it from running.

 

Rouge ffmpeg processes are not as bad as they use to be.

 

It is used many times through out emby, but transcoding glitches seems to be the only time it will continue to run when it is not needed.

 

In particular, when sending a stream to my Xbox one, if for some reason the DLNA server doesn't initiate the stream properly, ffmpeg will remain alive in processes. But it doesn't happen very often anymore.

Edited October 29, 2015 by chef

[ebr 16187]

This can currently happen if you stop playing something before it actually starts.  That happens most with Live TV because it takes a while to start those streams so it is more likely that you may back out of it before it has actually started.  Also, if you have a sketchy signal (like me) then the stream may never start which then hangs up ffmpeg and a tuner when you back out.

 

We are looking into it.

[mupet0000 0]

Hi,

 

I just wanted to add that I'm running Emby on my QNAP NAS and just had ffmpeg hang using all CPU. I started a stream on my phone at 720p 10mbps and changed it to 720p 4mbps, but the video just stopped playing and it went back to the video info page. At that point, there were two ffmpeg processes running which never stopped and I had to manually kill them. Babysitting Emby is not fun, is this still being looked into? Otherwise I have to keep checking for rogue ffmpeg processes eating up my CPU time.

[Luke 42083]

Hi,

 

I just wanted to add that I'm running Emby on my QNAP NAS and just had ffmpeg hang using all CPU. I started a stream on my phone at 720p 10mbps and changed it to 720p 4mbps, but the video just stopped playing and it went back to the video info page. At that point, there were two ffmpeg processes running which never stopped and I had to manually kill them. Babysitting Emby is not fun, is this still being looked into? Otherwise I have to keep checking for rogue ffmpeg processes eating up my CPU time.

 

HI, welcome. The next release is going to help with the issue of ffmpeg processes left running. A lot of work has been done to make sure it no longer happens. Thanks.