I finally cleared enough room to set up a virtual machine with Filmulator. However, when I reach the Filmulator tab and attempt to load an image, I get:
matrix::set_size memory could not be alloc'd
Segmentation fault
Working in a VM, which takes resources, on a system only 4 GB of ram will likely strain most raw processing programs. For instance, RawTherwpee has a page dedicated to running with 4 GB or less of ram.
I am lucky, my edit machine was recently upgraded to 32 GB ram.
I’ll see if I can make a low-RAM setting that doesn’t cache the images. It will be very slow when making any slider changes though, since it will have to recompute from the start every time if it doesn’t cache the images.
No, I got my info from running my backup file, which is necessary to run when you have a 4 TB pc. The backup file for my pc is in D:\ - there should be no other file (besides C:) …but there is currently a file V:\ that’s inundated in with D:. I’ve almost eliminated it, but it’s still there, as you can see. The V:\ file showed up when I downloaded Filmulator.
Okay, that is probably what I accidently did…do you have any idea how to get it out? What I mean is, when I try to search for the V:\ file to delete it, my pc is telling me there is no such thing…yet obviously there is.
Honestly, I have no idea what the robocopy command is…I am by no means a pc tech, I just noted that the V:\ drive showed up and was really trying to take over the D drive. Is robocopy a bug?