In a recent PMS update a “feature” was added that would check the available space in the Transcoder Temporary Directory to make sure it is at least the same size as the video file being transcoded. The problem with this is I use a RAMDisk, 6GBs, as my temp folder as I want to create as little wear on my System SSD and my Storage HDDs as possible. That amount of space has always been more than enough, I previously ran tests with 12Mbps encodes (which I rarely use anything that high quality when transcoding is needed) and they have never used up all of the space. My movies are also very large files, that is the whole point of using PMS, being able to keep very high quality, large original video files and let PMS transcode it to something smaller on the fly when it is needed.
I need a way to disable this check. I don’t care if the devs think it is better to have such a check, if I run into issues I will work with it on my end to correct it. Or at least make it so if you select a lower quality, one that can be calculated with bitrateXlength that wont fill the disk then allow it to play. Currently you can’t even get to the point where you can select the stream quality, you just instantly get an (Very Vague) error when attempting to play the video. Not to mention my server doesn’t even break 40% CPU usage when it is transcoding at 12Mbps so I have the encode settings maxed which also allow for smaller file sizes.
And I am sorry to bring this up in this topic but this issue has been the most nagging one to me lately. I really love the work all of the devs do on Plex, it is a fantastic piece of software, I wouldn’t keep using it if it wasn’t. But every time I even think “maybe it is time I pay for a life-time Plex Pass” one issue or another comes up and it just makes me think I’ll be wasting my money when a completely experience breaking bug comes around and I can no longer use the software at all.
@CharredChar said:
In a recent PMS update a “feature” was added that would check the available space in the Transcoder Temporary Directory to make sure it is at least the same size as the video file being transcoded. The problem with this is I use a RAMDisk, 6GBs, as my temp folder as I want to create as little wear on my System SSD and my Storage HDDs as possible. That amount of space has always been more than enough, I previously ran tests with 12Mbps encodes (which I rarely use anything that high quality when transcoding is needed) and they have never used up all of the space. My movies are also very large files, that is the whole point of using PMS, being able to keep very high quality, large original video files and let PMS transcode it to something smaller on the fly when it is needed.
I need a way to disable this check. I don’t care if the devs think it is better to have such a check, if I run into issues I will work with it on my end to correct it. Or at least make it so if you select a lower quality, one that can be calculated with bitrateXlength that wont fill the disk then allow it to play. Currently you can’t even get to the point where you can select the stream quality, you just instantly get an (Very Vague) error when attempting to play the video. Not to mention my server doesn’t even break 40% CPU usage when it is transcoding at 12Mbps so I have the encode settings maxed which also allow for smaller file sizes.
And I am sorry to bring this up in this topic but this issue has been the most nagging one to me lately. I really love the work all of the devs do on Plex, it is a fantastic piece of software, I wouldn’t keep using it if it wasn’t. But every time I even think “maybe it is time I pay for a life-time Plex Pass” one issue or another comes up and it just makes me think I’ll be wasting my money when a completely experience breaking bug comes around and I can no longer use the software at all.
Not possible and I do not like this change either.
@starbetrayer said:
Not possible and I do not like this change either.
By “not possible” do you mean you happen to know for a fact devs are unwilling to revert this change?
I agree with OP. How about controlling that check via an advanced setting? or even an install-time argument, SOMEthing, ANYthing! I understand the argument for the “greater good” of a quality product to the masses, but it’s one thing to make it default (for uninterested tweakers) and another to remove it entirely. I don’t like it and have been running older versions because of this one feature.
I run virtualized, on a NUC, which has limitations all over the place. I happen to have RAM to spare (most days), hence tmpfs. Am I an edge case? FWIW I happen to NOT share the SSD wear-leveling concern that I’ve heard among alot of complaints, rather my struggle is born of limitations
@starbetrayer said:
Not possible and I do not like this change either.
By “not possible” do you mean you happen to know for a fact devs are unwilling to revert this change?
I agree with OP. How about controlling that check via an advanced setting? or even an install-time argument, SOMEthing, ANYthing! I understand the argument for the “greater good” of a quality product to the masses, but it’s one thing to make it default (for uninterested tweakers) and another to remove it entirely. I don’t like it and have been running older versions because of this one feature.
I run virtualized, on a NUC, which has limitations all over the place. I happen to have RAM to spare (most days), hence tmpfs. Am I an edge case? FWIW I happen to NOT share the SSD wear-leveling concern that I’ve heard among alot of complaints, rather my struggle is born of limitations
I was in the conversation with elan concerning this when the change was first introduced as the first behaviour was bugs not able to read file. I run PMS virtualized in an ESXi VM and was pretty pissed off about the change as well. I had to increase the size of the VM significantly to make everything work (size of biggest file + 100 MB).
The devs did not want to revert back at the time.
OttoKerner, I thank you for the response that I have marked as (currently) an answer, being that the Devs are actually looking into it, hopefully because enough people see it as a problem.
Honestly, I feel the best solution would be a check mark under “Transcoder temporary directory” of “Ignore Free Space Check”, considering just to change the temp folder you need to show advance settings it should be all that is needed to keep the average Joe from screwing things up.
I ended up “fixing” the issue by purchasing an additional 64GBs of RAM and using that as a RAM Disk, thanks a lot Plex Devs for creating the need for me to buy more memory.
No, it’s not reverted (Win10 Plex v1.16.3.1433).
Tried yesterday a live-tv dvr of a 20min HD episode on a 3GB RAM-Disk.
Got an error about not enough space…
Changed the temp folder to a HDD and all worked - the folder on the HDD never exceeded 150MB while recording/transcoding.
