Gang… I need to clarify.
Debug logging ON
Verbose Loggon ON
The transcoder team needs both
@ChuckPA Just tell them to limit the ffmpeg transcode speed for the MPEG Dash endpoint
I think it’s clearer than logfiles, and I think they can understand that 
The transcoder engineers want the logfiles because there’s more involved than just the DASH endpoint. They want to see the complete picture
@ChuckPA said:
The transcoder engineers want the logfiles because there’s more involved than just the DASH endpoint. They want to see the complete picture
I will make the logs they need tomorrow when it is quiet on my server, normally around 18:30 paris time, if someone else can deliver them faster, feel free to ofcourse 
Thanks. All contributions greatly appreciated. We’re testing on our end too.
@ChuckPA Here we go again!
Thanks!
Send directly to the Transcoder team lead.
I haven’t gotten around it today unfortunately… Do you still need more logs @chuckpa ? If so, I can capture some on saturday and upload
I’ve given the team two sets of logs. I"ve not heard back but, given how things normally go, I would have heard by now if it wasn’t the right data 
Any news? o:)
For fun I tried that “other” server and guess what… transcoder does not throttle when using web browser… they are also using ffmpeg, perhaps it’s related
Hi ChuckPA, any news would be appreciated. This seems to be a MAJOR problem…
Imagine 4 concurrent web streams transcoding entirely at once… This must be causing some stability issues.
It’s only going to cause issues for your machine if it can’t handle 4 concurrent sessions 
(i know… it’s not funny but trying to find some humor)
Regarding ‘news’, yes. they are working on it. When will we see it. Not sure. There are a bunch of intertwined issues with the recent change. This is, unfortunately, only one of them. I can only speculate they will ‘hit them all’ at once.
@DuffHQ said:
Any news? o:)For fun I tried that “other” server and guess what… transcoder does not throttle when using web browser… they are also using ffmpeg, perhaps it’s related
The “other” server doesn’t have that type throttle at all. It does a ‘full length’ transcode / remux for everything. It does break the output into 'buckets" but doesn’t start playing any until it’s done with the transcode/remux
I’m lucky I found this thread, its been driving me crazy for a few weeks trying to figure out what was going on. Hoping for a version soon that fixes it
Have any of you had the opportunity to try out 1.8.2 ?
Not yet, didn’t see anything related in the changelog and I’ve just seen a deadlock issue I’ve been having has been identified so I’m waiting for that update before upgrading…
One thing you will want to pay attention to…
1.8.2 does not have HW transcoding enabled (if you’re using it from 1.8.1).
There is another update in about 2 weeks to bring it back (in-process changes)
Still seeing the same behavior with 1.8.2 and the plex.tv webapp even after the web app was updated to 3.20.3. Issue still hasn’t been resolved.
Version 1.8.2.4209
Same Issue
