Internal record-keeping gone wrong?

Topaz Video Bugs and Issues
1

(Topaz Video, version 7.1.0)

Weird anomaly that doesn’t seem to be affecting my render, but is perhaps worth mentioning.

Project - local process with Starlight Precise 2.6, 640 x 480p 29.97fps input, 3X output

Description of weirdness:

  • After creating several tests of SLP options in a project that had 3 source files, I settled on a rendering strategy and removed the previously-opened and tested source files using “Close all inputs” on the Sources tab. Then I added a new file which was to be used for the actual production project.
  • This new file was opened and appeared on the timeline. I made no timeline selection, as the entire file was to be rendered.
  • Starlight Precise was set as the enhancement model, with 3X scaling and sharpness set to 2

I selected Export, entered my encoding preferences, and started the job. It’s now been running for about 22 hours, is halfway finished and looks great in the export preview window.

But if I exit the export window and go back to the project window with the timeline, a DIFFERENT file appears on the timeline and in its preview window.

Here are some screenshots, starting with the Sources window with the correct - and only! - file selected.

World Peace file ID
World Peace file ID693×217 28.8 KB

Here’s a shot of the export preview window, showing the same frame.

World Peace preview window
World Peace preview window693×547 217 KB

Finally, here’s what the project preview window and timeline now have loaded, somehow…

Morgus girl on timeline ID
Morgus girl on timeline ID838×637 255 KB

This is one of the files that I ran a very short test of prior to deleting all of the other source files with the Close all files command, and then adding the file that was to be used for the ‘real thing’ project.

It looks like something wasn’t scrubbed after the Close all files command, which would be a housekeeping issue of some kind, I’d think. Not reporting ‘bug’, per se, but it is very strange.

2

Can you grab the logs from the app and send in for further review of this situation? help@topazlabs.com

To gather logs, please select Help > Logging > Get Logs for Support and attach the zip file to your reply.

Here is a video to help with the steps of how to collect the logs.

3

Hi Kyle,

I’ve attached the logs file to this email.

A quick note to wrap up my tale of two computers & GPUs from a month ago:

  • The problem with my RTX 5070 Ti machine turned out to be the CPU. ASUS checked out the motherboard and claimed that they ‘fixed it’, but there’s really no indication that there was anything wrong with it. It still wouldn’t post after it was returned to me. Bench testing with another CPU proved that the original had failed. I fought with AMD for a week over the warranty and finally prevailed. Got shipping confirmation of a replacement just this morning.
  • My backup machine with the Radeon 7900-XT demonstrated enough problems and unusably-slow performance with Starlight models, that I’ve privately concluded that AMD isn’t ready for primetime with Starlight, and probably never will be with the current architecture. (strictly one old-guy’s opinion…)

I’m delighted to be back in the water with the 5070 Ti machine and just completed the first 30-minute video restoration with SLP 2.6 at 3X. Results are very good and the time to render entirely reasonable, considering what it’s done for me.

Thanks for your continued support. You guys have really stepped up the game this year!

Regards,
Chuck

(attachments)

logsForSupport.zip (1.63 MB)

4

Thanks, Chuck. I’ll get these over to the team for further review and see what is going on here with the video not showing correctly.

5

Update. Although the issue was real, I don’t think it’s necessarily worth the team’s time pursuing the wild geese.

After the render finished, I closed the project and the app, then restarted Topaz Video and reopened the project. The correct video now appears on the timeline. There was a system restart and some other playing around, too, but I’d guess some internal record-keeping had been incompletely updated or something.

6

Understood, Chuck. I will keep an eye out if we see the situation continue or pop up again for a further look into it.