#101 Trying to use 'Trim Files' puts RAM into cache until 100% is in use, OS and source SSD usage to 100%, then fails to convert

[L O' Brien]

I'm trying to trim the first 6 seconds and last 105 seconds from a number of files of varying lengths, as far as I can tell this can't be handled with arguments, but can with the 'Trim Files' feature. The problem there is that this seems to cause issues on my system.

When I input my values and then click 'Trim files' my memory usage slowly climbs towards 100%, and then starts moving the memory into 'Cached', at which point my computer is pretty much unresponsive and some background programs (Steam, Discord) can crash. My disk usage, on both my OS disk and the disk on which the source file is stored, also both climb to 100%.

After some time - sometimes ten minutes, sometimes more - the conversion will either start, or immediately say it fails. In my experience, I usually need to restart my whole system to get a working convert running, and at least the file is trimmed, but after that first one, any subsequent ones fail, even after restarting the program.

I have tested this on multiple 4K videos, a single 4K video, and a single 1080p video all with the same result. Is there something I have configured wrong?

I could, admittedly, use -ss and -t to handle this on the parameters but because the files are variable length, I would have to get each time code for each file and do them one at a time rather than queue them up like Trim can, when it's worked for me.

[Abel]

Hi, I'm not sure about the cause. Could you try using directly variables in parameters to emulate your trimming, adding either in pre-input or in parameters:

-ss 6 -to %fdur-105

Since now file duration variable admits operators.