Incorrect progress bar-bug in GUI TopazVideo 1.1.1 and 1.2

Useless progress bar in the GUI when using stabilization:

The GUI displays the work steps, duration, and fps…
initially, in the first step (file analysis), it shows 0/2, but it should show 1/2 …

Furthermore, the previous steps should not now occupy fixed portions of the size/length of the progress bar.
This unnecessarily reduces the display accuracy of this short bar.
The progress bar should display each step separately from 0 to 100% graphically.

… Just a side note.

The problem is the time and fps information

In the first step, these are correct.
Not so in the second.

  • At the beginning of the second step, the actual rendering, the GUI also displays the correct value for a moment/ 1 second, e.g., 2.1 fps and 30 minutes (4k).
  • But after a second, the display jumps, showing a “dream value” of several thousand fps and a remain time of a few seconds or minutes.
  • This error now remains in the calculation and is only gradually ‘offset’ by the actual rendering time.
  • Until shortly before the end, when the value is reasonably realistic again, you have no usable display.
  • I have now experienced this over several days without exception.

Adidition:

As I have just discovered during a test, this error of a completely incorrect, i.e. unusable progress bar also occurs in other models when you pause the process and then continue.

Once you continue, the progress bar only shows nonsense.

Just checked: this error does not occur in ‘VideoAI7’, neither in Stabilization nor in other models.

Kind regards

1 Like

Thank you for sharing these findings, we will get them shared over to the devs for review to see what is going on.

1 Like

I regret to say, as a new Topaz Video user, that I am experiencing the exact same thing. The TopazVideo status bar lacks utility. This is very disappointing.

Hi,

Topaz’s AI models are fantastic…
now they just need someone to lovingly take care of the GUI and, more generally, the integration of the computing process into the computer hierarchy …

(see the pointless terror of reading when generating ProRes or … AVID codecs…)

I guess that’s easier said than done :slight_smile:

kind regards