I’m trying to configure Plex MX (Windows) to use a RAMDISK for transcoding. The RAMDISK is created using Windows Scheduler. The problem is that Plex MS starts up too quickly and tries to find the RAMDISK which isn’t initialized yet and throws an error:
Error creating directory M:: boost::filesystem::create_directories: The system cannot find the path specified: “M:”
How do I get PlexMS to delay launching to make time to find the RAMDISK after its initialized? Frankly I’m not sure how anyone managed to accomplish getting PlexMS to use a RAMDISK given this race condition.
May I ask why do you feel need to use RamDisk for transcoder?
@“Bartlomiej Baraniec” said:
May I ask why do you feel need to use RamDisk for transcoder?
This is a heated debate around here and other forums. Suffice it to say that I have heaps of RAM in my VM setup (48GB) and I’m trying to solve an issue of transcoding “buffering”. It’s contentious as to whether a RAMDISK is faster and alleviates any of the bottlenecks of which the main one is undoubtedly CPU. I’ve allocated the bulk of my CPU resources (dual Xeons) to this VM already but the problem still occurs - mainly with an “Opera” Plex client in a TiVo box in another city. I don’t want to get this thread too off topic. I’ll start another thread with my specific client issue once I get this RAMDISK running.
I was using imdisk to create my RAMdisk and Task Scheduler to launch imdisk at system startup but this did not work (long story). So it turns out that running my cmd script manually created the RAMdisk and PlexMS could use it but using Task Scheduler to launch the script was not working and therefore PlexMS couldn’t find the (non-existing) RAMdisk. I’ve switched to SoftPerfect RAM Disk which starts up automatically and now Plex MS is happy.
That’s several hours of finagling I’ll never get back, phew! Now I can continue testing/debugging my real issue: an “Opera” Plex client in a TiVo box in another city constantly buffering (and hence not playing back smoothly).
