Recordings fail for lack of space when transcoder temp folder is a Ram Disk

Server Version#: 1.18.5.2309
Windows 10, 16GB system ram.
HD Homerun Connect (dual tuner, no HW encoder)

Recently I set my transcode temp directory to a Ram Disk of 8GB, primarily to save wear and tear on the SSD that Plex is installed to.

I later found that scheduled recordings of 2+ hour programs would fail.

I know that when recording a program it uses the transcode temp folder so that you can restart the program from the beginning while its still recording. Problem is it seems to check if it has enough disk space to hold the entire program in the transcode temp folder, and if it doesn’t think it has enough, doesn’t even start the recording at all.

Just seems to me that when you have a recording, especially one that is scheduled, the priority would be record the program, and timeshift if possible, but don’t cancel just because you can’t timeshift it fully.

Is there anything I can do (short of allocating all available memory to the ramdisk) that will allow me to continue to use a ramdisk of that size, and still get my 2hr+ recordings?

If not, a couple ideas:
When scheduling, have an option to not permit timeshift while recording a program. (99% of the time I’d choose this anyway)

Just start the recording, and when the transcoder temp disk gets to a certain level of fullness, start eliminating the oldest transcode segments. Maybe allow this as an option when scheduling as well.

Or let us set a global limit for all timeshifting.

Thank you

You need more ram before you should use ram drive.

64 gig ram/32 gig ram drive is a good minimum.

Even with 32 gig ram drive, dvr can error out with multiple long recordings going on.

The machine I run plex on is old and cannot be upgraded with more memory.

I really don’t see why 8gb shouldn’t be enough. The recording itself is being made to the .grab folder. The transcoder temp is just to be able to watch what is currently recording.

In any case, I think I found a workaround. Set the ramdisk to 32GB, dynamically allocated.
In most cases, it shouldn’t ever have to page because I’ll have a good 10-12gb free, which is more than enough for a 2hr HD program.

Thank you

The coming 1.18.7 version of PMS might bring some improvement for this issue.

1 Like

Well I witnessed the same when I had one single recording with a final file size of 2.84 GB while I have 16 GB in my system (I don’t have a “fixed” RAM-disk, but with Unraid the whole OS only lives in the RAM).
So I also didn’t get why my recording failed. I switched back to using my SSD as a temp drive as the speed of the SSD is sufficient in my view.

Good to hear. Thank you

I had to do the same. But, I would like to be capable to use the RAM to avoid wearing my SSD.

I’m also having this problem. Can’t record games because there’s not enough space to transcode it. It would be nice to have an option for a different transcode directory for LiveTV or maybe for recordings have it transcode directly to its series folder. Both would be ideal so we have the option to set the directories for actual recording and the temporary recording from watching live.

I agree

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.