disabling transcode throttling breaks transcoding... sometimes

[draic 0]

I have a weird bug with emby 4 and transcoding. I leave throttling off as I have more than enough resources, but it now happened twice that when the server starts with throttling disabled, every actual request for transcoding from a client will simply time out. The server claims the client has started playback, but the client times out. The trick is to enable throttling, save, disable and save again. Throttling is now still disabled, but this time all clients will start playback like normal. I had this weird problem now twice, but the server does not always get stuck when started with these settings. No idea what I could provide to pinpoint the issue, but wanted to report it nonetheless. 

[Luke 42085]

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

[Luke 42085]

@@softworkz

[draic 0]

The logs are giving errors, claiming no space left on the device. The path is set to a cache drive with ~200gb free space... so no idea what embys issue is/was. Also simply flipping throttling just let it work again. 

transcodelog.txt

Log.txt

[Luke 42085]

How big is the file you're playing?

[draic 0]

1550mb

[Luke 42085]

Ok well this is the transcoding temp folder:

/transcode/transcoding-temp

Are you sure the drive that it's on has 200gb of space available?

[draic 0]

180gb at the moment, I just checked (emby runs in a docker and that path was set up just for the transcoding files; same setup for half a year atleast). And also with throttling turned on and off again, it now is transcoding and I do not get these errors.I have not touched anything on the underlying system or files. So I believe there is a error happening while ffmpeg is writing the files which has nothing to do with my actual disc space, but some other problem? Maybe it was a fluke, but it occurred twice now and both times flipping the throttle option has fixed it instantly. I didn't see the disk space error before I got it working, so in case it happens again, I will definitely inspect the folder and what is actually written, but I see no way how emby could have filled up the space.

 

As I said, it is currently working, just wanted to report the behavior. Otherwise the new update has only been a big improvement here

Edited January 19, 2019 by draic

[Luke 42085]

Ok thanks for the info. The issue is not so much about throttle on/off, it's ffmpeg thinks you're running out of disk space. This could still happen with the throttle turned on, it's just a lot less likely.