Transcoding issue

[Gabi92 0]

14 hours ago, Luke said:

Is there a ramdisk involved?

The ram disk is not part of the machine ram, it´s host ram and now it´s disabled.

 

13 hours ago, isamudaison said:

If you're dead-set on using a RAM disk, I've had success with the following:

- Allocate 40GB

- A cron job that runs every hour (here is my specific cron job):

0 * * * * bash /home/isamudaison/clean-emby-transcode >> /home/isamudaison/log/clean-emby.log 2>&1

This executes the clean-emby-transcode script and outputs to a log file specified

Here is the `clean-emby-transcode` script:

#!/bin/bash
docker exec emby sh -c 'find /transcode/transcoding-temp/ -mmin +360 -delete -print'

This deletes any file modified over 360 min in the past (assuming a docker container that uses the specified path).

This falls apart if someone leaves a live tv stream transcoding forever (event shows like super bowl/oscars/whatever), I suspect 80GB would be an ideal size for a RAMdisk.

Finally i´ll be using a disk with around 110 GiB dedicated for transcode but i think this option will be handy in order to avoid space issues in case all of the ppl are playing the biggest movies.

Also now, i´m facing some issues related to the transcode but not related to the space :).

I´ve attached the log so you can see it, let me know if it´s better to open a new post to split the topics.

Thank you everyone

embyserver.txt ffmpeg-transcode-e2c08962-b666-4131-a7a9-b23b5f17b0ee_1.txt ffmpeg-transcode-0f0d7b7a-4125-429f-aa05-7ee531c14b02_1.txt

[Luke 42077]

@Gabi92 can you please describe the issue? Thanks.