Hi. New Topaz Video AI user. Loving the software so far but ran into a major bug.
Was doing a multi-day render (upscaling a 1080p movie to 2160p). Halfway through the export I paused the render for a short while, then resumed. This seemed to work OK. Then, when the export was about 85% done, with about 9 hours remaining, I paused again. This time however when it resumed, it resumed around the halfway mark! Possibly close to where the first pause happened, or maybe shortly afterwards.
My export is now continuing, but it’s got 26 more hours to go now, rather than 9.
The processing times can change as the app is running, now that it has been a bit since you started it back up can you provide an update on the processing time and if it has completed or not?
1 hour, 42 minutes remaining. So the original estimate after I resumed seems like it was reasonably accurate. (Meaning I really did lose all those hours of rendering time.)
Just checked the final output file. The entire second half is missing! Basically everything after my first pause is completely gone. All the rendering from the last two days thrown away.
Also, the final output file was in the wrong directory (although named correctly). It ended up in the source directory, rather than the actual output directory I specified (“D:\VTemp”).
Hopefully the development team can pull something from the log files to see what happened. (Updated zip attached.) But in the meantime, pretty disappointed with the stability of this software.
This matches my experiences with the Pause option. I tend to just click the X on the top right of the window so it will continue next start. I might help you rendering your video if you don’t want to start again.
Oh so you’re saying shutting down the app while it’s rendering also works as a “pause”, and it will automatically resume when relaunched? And that works reliably? If so, that would be a reasonable work-around until pause/resume is fixed. Thanks!
As an experiment I started an 8-hour render. Exited the app after it was 25% done, then restarted it a few hours later. Then did it again (when it was around 60% done). Each time I restarted the app it looked like it was working and correctly resuming the render.
However the resulting file was corrupted. (Doesn’t play at all.) Not only that, but it wasn’t even in the correct destination folder! I found the file sitting in the source folder.
So the ability to stop and resume a render seems very broken, at least on my system with version 5.5.0. This is really disappointing as I can’t not touch my computer for days on end while it’s doing a long render. (I’m not in a rush for my output files so ideally I just want to schedule all rendering to happen during nighttime hours.)
I have log files if dev team wants to take a look. Let me know and I’ll upload them.
Alex, apologies for the delay in response on this. Yes, if you can upload the logs or send them to us directly and I can have the team take a look to understand what happened.
Hi Kyle, thanks for responding. I don’t think I have the logs from the very last session anymore, but the previous logs were posted above (two zip files).
I’ll also try v6 in the new year to see if it still has the problem.
Have the same bug. It was already on 6.0 version, I got back to 5.3.4 and it work flawlessly (but I had less fps with same kind of video). Now I have tried 6.1 and have few second cut off from the end of video (there is the audio, but no video). Seems I had to downgrade again. This is what we are paying for…
Unfortunately, I have something similar in version 6.0.1.
After exiting the program for the first time (without pressing pause) and restarting the program, the processing action was automatically resumed (I like it). After a few days of processing with pausing for night, I decided that something was taking too long and should have ended a long time ago, so I looked at his previous work and to my surprise it turned out that apart from the first part, all subsequent parts start with the same scene!!! So how was program supposed to finish his job???
I am reporting this to the authors of the program as a serious error.
