Hi,
That’s a lot to take in, okay, let’s take it one step at a time.
But I see you’ve at least identified the exact same problem as I have …
… Well, that puts my mind at ease—I was starting to think no one here understood my problem 
That said, I really appreciate these “crash recovery features,” because it’s just unbearable that Topaz ends up deleting a 10- or 30-hour job itself because it’s too clueless to write the final file.
This has happened multiple times with Apollo—and not just to me:
But we should tell TOPAZ that it would be enough to read every 30 or 60 minutes to create this crash backup file, and not every 30 seconds !!
(After all, this error is nothing more than a reading terror attack)
Nevertheless, I have to say that I don’t understand why it has to be read over and over again in such a completely stupid way; it would be enough for me if TOPAZ were smart enough, in the event of a crash, not to drag the file written by FFMPEG.exe (with all the numbers, without a file header) down with it !
→ You can create the file header yourself in Bandicut, for example…
Haha, funny—I was wondering about that too… so I always ended up closing the app in the Task Manager
Best regards
