Roku - Multiple ffmpeg processes?

[MSattler 390]

Roku 2 XS 2.15

Server Version Version 3.0.5808.0

 

I had one user watching a movie via FireTV App with no issues.

 

Roku user is watching a movie.

 

I had 2 ffmpeg processes.

 

The Roku user stopped a movie, and then started/stopped 3-4 movies.  I then had the FireTV App user complain, and when I looked at the house I have 6 ffmpeg processes running.

 

Is there a known issue with ffmpeg processes not being killed if someome hits start/stop really fast?

 

I don't have a Roku in front of me so it is hard for me to test.

 

Thanks!

[MrWebsmith 598]

i also have remote/wan users with rokus connecting and i have seen this also.. i will try to collect logs and screenshots the next time this happens... usually i notice multiple ffmpeg processes and in order to get the emby server to respond again i need to quit process on a couple of those rogues..

[MSattler 390]

i also have remote/wan users with rokus connecting and i have seen this also.. i will try to collect logs and screenshots the next time this happens... usually i notice multiple ffmpeg processes and in order to get the emby server to respond again i need to quit process on a couple of those rogues..

 

Yup same here, not sure how we can grab the logs from the Roku, however from what I see in the Admin panel the server is just doing what it is supposed to do.  Is it possible that there may need to be a request limit implemented in the server side, to check to see if an existing ffmpeg instance exists before allowing the creation of another?

 

@@ebr This is another instance where it would be nice to know which ffmpeg process is being used by which client so I could blow away the rogue processes.

 

Thanks!

[Jen25 34]

seen it here also.

 

 

@@ebr This is another instance where it would be nice to know which ffmpeg process is being used by which client so I could blow away the rogue processes.

 

 

 

i usually just kill them all.  i've never had a problem (the show actually being watched has never stopped), i'm assuming for the instance where mb is actually using ffmpeg it will restart and continue using it.

Edited January 18, 2016 by dnicks

[BAS 225]

I think I solved this on @@MrWebsmith server by changing the playback/transcoding tab in server to be set to auto cpu and auto cores, he had it on intel quicksync and a specific core amount. I think auto on both has prevented this from happening anymore, or at least at a much less frequent pace. Also another thing we tested on his end, is to make sure you set some sort of outgoing max playback per streaming users, found in playback/streaming tab of server. Regardless if you have enough upload to give, the user who is connecting might not have enough download, and you would be maxing their internet out and possibly causing disconnects. These are a few things I helped smith with, guess he can let you know if those changes have made a difference. 

 

My server was already set like the above and I have multiple external roku users and haven't seen a rogue process in a long time. Smith and I also have enable throttling unchecked in playback/transcoding tab in server.

Edited February 21, 2016 by BAS

[MSattler 390]

I think I solved this on @@MrWebsmith server by changing the playback/transcoding tab in server to be set to auto cpu and auto cores, he had it on intel quicksync and a specific core amount. I think auto on both has prevented this from happening anymore, or at least at a much less frequent pace. Also another thing we tested on his end, is to make sure you set some sort of outgoing max playback per streaming users, found in playback/streaming tab of server. Regardless if you have enough upload to give, the user who is connecting might not have enough download, and you would be maxing their internet out and possibly causing disconnects. These are a few things I helped smith with, guess he can let you know if those changes have made a difference. 

 

My server was already set like the above and I have multiple external roku users and haven't seen a rogue process in a long time. Smith and I also have enable throttling unchecked in playback/transcoding tab in server.

 

 

Hmmm, I've always ran auto auto for both, and never used quicksync and still ran into the issue.  The latest beta server builds seemed to have helped with it and I don't see it as often.   I leave my max playback set to 25Mbps, since I've got a huge pipe.  <That's what she said>

[BAS 225]

Max playing internally is fine, the limit in the server would be for those streaming externally and perhaps maxing their bandwidth plan on their end. I've havent had a rogue from a local user in a long long time, mine always seemed to be from an external roku user. I'll keep an eye out here, just thought I would share my settings.