Topaz should not delete temporary output files on failure

Currently, Topaz Video deletes all temporary output files when a failure happens, for any reason. This breaks any ability for retry from checkpoint to work correctly. I just lost 6 hours of GPU time, and more importantly the amount that added onto my electric bill, because of this.

1 Like

It seems this may be a result of the “Enable Externally Previewable Exports” option. That same option is also what causes all exports to require DOUBLE the amount of disk space due to requiring writing to a temp file first, as well as the unnecessary overhead of copying everything an extra time.

That option is ON by default. I can’t see that it does anything useful, and has only downsides. I turned it off and my life is happier now, or at least my usage of Topaz is.

1 Like

I just had the same thing happen on the latest version of Video AI.

Except the process completed successfully, except Topaz in all its stupidity and haste, writes a temporary file, finished the export with adequate space, then only to wake up after running it overnight to find a log that it attempted to then write ANOTHER copy via an ffmpeg prompt to a new file name and it ran out of space while doing so!

This is so stupid. Why not just rename the completed .MOV file. If it’s completed it won’t be truncated or have an error. Ridiculous.

Not to mention that I had terrabytes of space with full read/write access on other drives yet Topax claimed they were “read only” when querying them in the log to write the files to as a “last resort”.

Such garbage and a utterly stupid flaw in the logic of the software.

I lost 12 hours of processing time under high GPU load for a file successfully completed, and Topaz deleted BOTH the temporary file and the new file it attempted to copy to a new MOV simply to change the file name (idiotic).

I have to say on all fronts, from a function, logic and workflow standpoint. This software has gotten worse with EVERY iteration since 2.6.4.

2.6.4 never deleted temporary files even if they failed, you could recover them with a untruc x64.

No preview loop, can’t generate a specific amount of frames on output, now this.

Gets worse and worse. Only thing the new versions of this software are good for are much hardware optimization, worse yet, one model I often rely on outputs in poorer quality than it does in 2.6.4.

Thanks for discovering and tracking down the cause of the issue BTW.

Totally agree, this option should be disabled by default, especially since it was or was not a part of legacy versions of Topaz Video AI/Video Enhance AI.

It also lacks logic. Say if the output successfully completed, it shouldn’t need to re-copy the asset. At that stage it simply needs to rename the “temporary” file which would cease being temporary upon 100% completion. Especially if you aren’t muxing/copying any audio over such as in my case and I’d imagine yours and the majority of most users using the software as part of a professional or hobbyist workflow.

1 Like

Unfortunate update, it seems like turning off “Enable Externally Previewable Exports” did not actually fix the deleting outputs issue. Although I’d still heavily advocate for disabling that option as the default, but even with that option off, the new Topaz UI is still automatically deleting all outputs on any failure.

This is something that has been requested to the devs to see if there is an option to keep the temp files still without losing them on a failure. The crash recovery and preview options have made it difficult at this time but if they can work out a way we will see if it can be added into the app in the future.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.