It seems to me that as of right now, if I want to be on the safe size, I need to dedicate a hefty amount of space to my transcoding-temp directory for emby:
I should have enough space available to store the full size of the source file for whatever show(s) are being watched at that moment, plus a small buffer.
In other words, if there are three 4K remuxes playing at the same time, 80GB each, and they're all transcoding at once, then I need at least 240GB of transcoding space available.
No idea what the requirement would be for live tv, I don't have that feature.
I say this from observation when my Apple TVth gen is a client. It seems to be able to direct stream a Blu-ray or DVD rip except it doesn't like the mkv format. The resulting transcode file seems to roughly match the file size of the original movie. And then it's deleted when I stop watching the show.
Also, it seems that if I run out of disk space, the whole movie (and sometimes the server) just stops with an out of disk space condition, there's no auto-pruning while the show is playing.
Does this mean that transcoding to RAM is a bad idea unless I have tremendous amounts of RAM?
So in other words, if I'm running in a virtual machine, I can't use the default folder with my piddly small storage dedicated to that VM. I need to specify something with more serious space capability.
Did I get that right?
Edited by markkundinger, 08 November 2019 - 06:28 PM.