Question : why is microsoft locking input source files after encoding is finished and not the output files?

[revan654]

Question : why is microsoft locking input source files after encoding is finished and not the output files?

[fmohican]

Hi, as fair as I know, staxrip ins't locked any file after encode is done.

This is strange fmohican. Example: I have a job list with 5 jobs, using 5 different source files, when the jobs are all finished, I can NOT delete any of the source files if Staxrip is open. I get error "file is in use in staxrip". But all the output files (in the temp folder) can be deleted. If I want to delete a source file of a job that has finished, I need to wait that ALL jobs are finished, so I can quit staxrip, and finally delete the source files.

Revan said it is due to how dotnet 4.7.2 controls the files. Would that mean that the only workaround is to add an option to delete SOURCE files to the recycle bin, so that the source file will be moved by the staxrip process itself ? (dangerous, no ?)

Or wait that dotnet changes this behaviour (if it will happen...)

(I am running Windows 10 updated to latest, and UAC is set to the minimum.)

[Revan654]

to prevent crashing, If VB reads a null value it crashes the software.

Dotnet 4.8 is set to be released in 2019.

[grerppy]

I've just tried your latest beta (2.0.0.0 beta 2) using dotnet 4.8 and I'm still having issues with the files being locked. Is there any workaround or solution? Thanks.

[fmohican]

@Revan654 isn't any workaround we can do to fix this problem?