I’m just wondering: has anyone else tried this tool? Did it work successfully for you? If there are any issues, please let me know so I can fix them. I tested it myself and it worked perfectly; I had even cropped the input video, and the tool handled the crop itself, completing the process successfully. By the way, I also got the CLI mode working—a feature Topaz had previously discontinued. This allows processing to run without launching the actual application, and batch processing is possible, too.
Topaz developers sometimes overlook crucial details simply because they are occupied with various other tasks; otherwise, their resources and expertise far exceed mine. I wonder if that tenfold speed increase seen in the cloud environment will also apply to local installations. I think it’s unlikely, but if it does happen, it would truly be a game-changer—especially since we could potentially boost speeds even further with custom settings.
If Topaz is smart, they’ll take a few notes from naxci work…by the way, the Adobe Creative Suite has been rebuildet (Artcraft) by using AI and offered as a free to use download
I am using your launcher to upscale 20 episodes TV drama. So far 2 episodes (1 hour for each one) have been completed and everything is good. It increased speed from factory default 0.57fps to around 0.78fps which is a huge boost!. Though I haven’t got a chance to test the new recovery feature yet.
BTW, I observed something interesting, the VRAM usage during VAE decoding reported by launcher can reach 15.9GB but when check task manager, it shows 15.6GB. I don’t know what is the difference about the data source and which one is more accurate.
Task Manager figures aren’t entirely accurate; the numbers shown within the application itself are more reliable. If you wish, you can also install nvitop to monitor GPU data. It would have been better to enable auto-backup so that backups are saved to a different drive; that is the better choice for long-running tasks. If Topaz closes for any reason, do not launch it again immediately. If you do, Topaz instantly deletes the unfinished file. Instead, open the recovery utility; it will locate the unfinished file using the logs and display the relevant information on the screen. This allows you to resume the interrupted task, but make sure not to launch the main Topaz application again until the process is complete. This is a fundamental issue Topaz needs to fix: the application deletes the unfinished file without question as soon as it starts. That is why I am able to resume the process without launching the main Topaz application; since it reads the logs, it continues the task using the same settings.
Thanks for your confirmation about the VRAM utilization. I have enabled the auto recovery feature and make sure it is saved to another partition. But I notice the temp file is not removed when the export job is finished. I have to manually remove the recovery temp file for now. Is this design intent?
That’s right, the temporary files aren’t deleted—that’s part of the process; you have to delete them yourself if they aren’t needed. Actually, I could implement automatic deletion in the next version once the process finishes normally.
