ffmpeg processes building up

[Blue407 0]

At what point do the ffmpeg processes for each streaming/transcoding session end?

 

I am currently doing some testing to my new server, iPhone and iPad client using web interface.

It seems to be that if I start playing a movie then go back and select another it carries on transcoding the original movie and starts a new session/process for the next one.

 

I killed a few off manually, but I;m guessing that these should stop automatically? When? how does it recognise a client is no longer watching?

 

Perhaps the user has to take more responsibility and end the movie first? obviously in a web browser its very easy to go to another page. I would guess with a proper client app this can be taken care of in the app. But of course Kids will be Kids and just do whats easiest...

[legallink 187]

Do you have transcoding throttling turned on or off?  I would turn it on, it will enable you, on the whole, to support more users.  As to the exact amount of time before a process shuts down, I'm not exactly sure, but I don't think it is more than a couple of minutes.  I would assume there is some potion built in there for latency, possible connection issues, etc., so that a user doesn't have to restart the process in the event of a sort term error.

[Deihmos 169]

At what point do the ffmpeg processes for each streaming/transcoding session end?

 

I am currently doing some testing to my new server, iPhone and iPad client using web interface.

It seems to be that if I start playing a movie then go back and select another it carries on transcoding the original movie and starts a new session/process for the next one.

 

I killed a few off manually, but I;m guessing that these should stop automatically? When? how does it recognise a client is no longer watching?

 

Perhaps the user has to take more responsibility and end the movie first? obviously in a web browser its very easy to go to another page. I would guess with a proper client app this can be taken care of in the app. But of course Kids will be Kids and just do whats easiest...

I see the same thing on ios. I have to kill them manually if you don't press done then return to the emby webpage. If you close safari without doing this ffmpeg will continue maybe until the video is fully converted.

Edited November 3, 2015 by Deihmos

[Blue407 0]

Any thoughts from the Dev team on this?

[Luke 42077]

it's a known issue if you stop playback before it has fully started, this will be resolved in a future release. or if you abruptly terminate an app during playback it's unable to notify the server. when this happens, it will eventually stop on the server after a timeout period. 

[tymanthius 18]

it's a known issue if you stop playback before it has fully started, this will be resolved in a future release. or if you abruptly terminate an app during playback it's unable to notify the server. when this happens, it will eventually stop on the server after a timeout period. 

 

How long is the timeout?

[Luke 42077]

it's a few minutes. best thing to do is try to stop the video using the functions in the app. the issue i mentioned above is known and will be resolved soon.

[revengineer 142]

I was watching TV through emby while on travel. The connection was not stable and I had to restart the program multiple times. When I returned to home there were 8 lingering ffmpeg processes, which never timed out over a 3-day period..

[Deihmos 169]

Any word on getting this resolved? With live tv ffmpeg never stops. I woke up one morning and it was still running from 8 hours before transcoding a live tv channel. 

[Luke 42077]

i'm unable to reproduce with the built in live tv but will keep testing.