Jump to content

Transcoding Throttle issue


Shidapu

Recommended Posts

Shidapu

Heya, just wanted to say big thank you for the update, it's awesome!

But my users are having 1 issue with the throttling feature, and it makes their streams freeze for a second every now and then, about 2-3 times per movie.

 

So i have disabled it for now, but you guys should have a look at it. <3

Link to comment
Share on other sites

Do you use hardware acceleration?

 

Which clients are used? Always the same of different ones?

 

You can see all details on the dashoard where the green bar is showing the playback position for a user session and the orange bar shows the range of the video that has been transcoded.

Also there are some figures showing the amount of time that the transoder is ahead of the playback position.

 

From there you might be able to see what's happening.

 

 

@@Luke - Independent of the actual problem here: we should make this more configurable: a: length of the ahead buffer - b: throttling strength

  • Like 1
Link to comment
Share on other sites

Shidapu

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks !

 

@@softworkz

 

 

Do you use hardware acceleration?

 

Which clients are used? Always the same of different ones?

 

You can see all details on the dashoard where the green bar is showing the playback position for a user session and the orange bar shows the range of the video that has been transcoded.

Also there are some figures showing the amount of time that the transoder is ahead of the playback position.

 

From there you might be able to see what's happening.

 

 

@@Luke - Independent of the actual problem here: we should make this more configurable: a: length of the ahead buffer - b: throttling strength

 

Heya, sorry for the late answer. Been working night shifts.

Well here comes some info then.

 

I use Hardware acceleration, and it looks like this:

https://i.imgur.com/I7u61YT.png & https://i.imgur.com/J7pCOTA.png

 

And the movie that was playing at that time of the happening:

https://i.imgur.com/zZKZ3si.png

 

When i was watching from the dashboard, i noticed the fps go from 140 down to 32, while throttling.

The user said that the movie frooze for a second, and then started back up again, did this about 2-3 times.

 

And i guess you want logs, i hope this is the right one.

https://gamerzdot.com/log.txt

 

The clients range from all sorts of systems, AppleTV, AndroidTV, Chromecast, Web, Local, Phones.

 

System temperatures looks fine: https://i.imgur.com/kC4PrFU.png

Edited by Shidapu
Link to comment
Share on other sites

  • 3 weeks later...

When i was watching from the dashboard, i noticed the fps go from 140 down to 32, while throttling.

Actually, that's the nature of throttling. Obviously this is reducing the overall fps.

 

You can see all details on the dashoard where the green bar is showing the playback position for a user session and the orange bar shows the range of the video that has been transcoded.

Also there are some figures showing the amount of time that the transoder is ahead of the playback position.

 

From there you might be able to see what's happening.

 

 

Link to comment
Share on other sites

@@softworkz he mentioned freezing. Any thoughts there?

 

I had written:

 

You can see all details on the dashoard where the green bar is showing the playback position for a user session and the orange bar shows the range of the video that has been transcoded.

Also there are some figures showing the amount of time that the transoder is ahead of the playback position.

But probably I hadn't explained it well enough.

 

From the symptoms it looks like this could be caused by an incorrect calculation of playback time and position. If there's a (slight) deviation between the playback position reported by the client and the position that ffmpeg is reporting, and that deviation is growing over time, this could lead to the symptoms reported here and elsewhere.

What could happen then, is that the only the calculated ahead buffer remains constant while the effective buffer is decreasing to zero length, which would mean that the server keeps throttling active because it thinks that the buffer is large enough while the actual playback position hits the end of the buffer.

 

For those reasons I said that users should watch all those values and also compare the timing values shown in the clients with those that are displayed on the server dashboard.

 

That's the only theory I'm having right now.

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...
  • 4 weeks later...

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...