Topaz Video AI Beta 3.2.0.0.b

Hello everyone!

We have another beta release for y’all’s testing.

Downloads
Windows
Mac (DMG) | Mac (PKG)

Changelog:

  • Performance improvements
  • New updated Chronos Model
  • Fixes issues with processing on Intel A770 use latest driver
  • Fixes processing failures on Intel Mac (machine crashes still waiting on Apple)
  • Redesigned login dialog
  • GUI fixes for software updates
  • Parameter values are retained when switching scales
  • Support for smaller patch updates on windows
  • Misc updates

Known Issues

  • Stabilization may fail sometimes
  • Users with upgrade subscriptions close to expiration may experience login-related issues

Thanks for testing

Please upload problem videos and logs here: Submit files

5 Likes

Hi, does it have scene detection?

1 Like
Topaz Video AI Beta  v3.2.0.0.b
System Information
OS: Windows v11.2009
CPU: AMD Ryzen 9 7950X 16-Core Processor              63.139 GB
GPU: NVIDIA GeForce RTX 4090  23.59 GB
GPU: AMD Radeon(TM) Graphics  0.47446 GB
Processing Settings: device: 0 vram: 1 instances: 1
Input Resolution: 1920x1080
Benchmark Results
Artemis		1X: 38.61 fps 	2X: 16.74 fps 	4X: 4.61 fps 	
Proteus		1X: 32.84 fps 	2X: 14.56 fps 	4X: 4.44 fps 	
Gaia		1X: 15.18 fps 	2X: 9.91 fps 	4X: 4.88 fps 	
4X Slowmo		Apollo: 28.6 fps 	Chronos: 15.46 fps 	Chronos v2: 31.88 fps 	Chronos Fast: 36.03 fps 	

I only have Chronos and Apollo available on the interpolation dropdown menu, Chronos fast is missing and there def isn’t a Chronos v2.

image

1 Like

In addition to the missing Chronos models, there’s a major performance issue with this build.

Using a 1440x1080 input, upscaling to 1920x1080 with letterboxing, and FPS conversion using Chronos from 23.976 to 59.94, plus Proteus Auto, I get about 3.3 fps. In the 3.2.0.4 alpha, I get about 11.3 fps.

My system info is in the benchmark I posted above.

1 Like

The chronos model with the beta is different than the alpha. The alpha and all other versions use chronos v2.

1 Like

Is this the source of the almost 4x performance hit?

Edit: looks like it is, I ran the same processing job as mentioned above with interpolation off and the alpha and beta were about the same speed. So the new Chronos model in this build is causing about a 3.5x performance drop.

So other than incurring a massive performance hit, what does the new Chronos model do? :grin:

1 Like

640x480 > 1280x960, 25fps > 50fps.
chronos + proteus auto = 59 seconds (preview 2 seconds)

640x480 > 1280x960, 25fps > 50fps.
appolo + proteus auto = 1m14 (2 seconds preview)

appolo is slower for me so, and from what I see it retains more detail. on the other hand for the previewed ones, around 47% of the first images are frozen.

All modes except Artemis 1x are faster than v.3.1.9. Can’t tell about the Apollo and Chronos modes because the benchmark of those never finished. :eyes:

I would like to draw your attention onto how data on screen are displayed today and 35 years ago when I was programming for the ATARI ST…

today:

35 years ago:

Unbenannt-1

35 years ago I was able to print all sorts of data nicely sorted in clean rows and collumns without any hassle by using the PRINT @ command. I am not sure what you are using today but it looks awful.

1 Like

I would like to comment that the flickering issue with Apollo on macOS with noisy videos is still present in this version.

I have not re-uploaded the files. So please re-use the files I already provided to the dropbox.

I know this can be a bit hard for some AI tasks, but I would like to see a description on what has been changed/improved when a model gets updated.

For example, this is what I would want from release notes:

  • Updated X model
    • Performance is expected to be improved/decreased/the same compared to the previous version.
    • In our testing we noticed a significant improvement in scenes with Y attribute
  • We have removed Chronos fast from the GUI because of reasons A and B
5 Likes
Topaz Video AI Alpha  v3.2.0.4.a
System Information
OS: Windows v10.2009
CPU: Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz  63.89 GB
GPU: NVIDIA GeForce RTX 4090  23.59 GB
Processing Settings: device: 0 vram: 1 instances: 0
Input Resolution: 1920x1080
Benchmark Results
Artemis		1X: 26.69 fps 	2X: 10.26 fps 	4X: 2.98 fps 	
Proteus		1X: 20.28 fps 	2X: 9.54 fps 	4X: 2.87 fps 	
Gaia		1X: 12.18 fps 	2X: 8.1 fps 	4X: 3.59 fps 	
4X Slowmo		Apollo: 17.28 fps 	Chronos: 25.74 fps 	Chronos Fast: 26.1 fps 	

Topaz Video AI  v3.1.10
System Information
OS: Windows v10.2009
CPU: Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz  63.89 GB
GPU: NVIDIA GeForce RTX 4090  23.59 GB
Processing Settings: device: 0 vram: 1 instances: 1
Input Resolution: 1920x1080
Benchmark Results
Artemis		1X: 19.45 fps 	2X: 7.14 fps 	4X: 1.92 fps 	
Proteus		1X: 14.85 fps 	2X: 6.13 fps 	4X: 1.88 fps 	
Gaia		1X: 13.02 fps 	2X: 7.84 fps 	4X: 2.97 fps 	
4X Slowmo		Apollo: 17.23 fps 	Chronos: 24.41 fps 	Chronos Fast: 25.96 fps 	

Topaz Video AI Beta  v3.2.0.0.b
System Information
OS: Windows v10.2009
CPU: Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz  63.89 GB
GPU: NVIDIA GeForce RTX 4090  23.59 GB
Processing Settings: device: 0 vram: 0.95 instances: 0
Input Resolution: 1920x1080
Benchmark Results
Artemis		1X: 25.96 fps 	2X: 10.81 fps 	4X: 2.83 fps 	
Proteus		1X: 20.22 fps 	2X: 9.48 fps 	4X: 2.91 fps 	
Gaia		1X: 12.28 fps 	2X: 8.33 fps 	4X: 3.7 fps 	
4X Slowmo		Apollo: 22.96 fps 	Chronos: 8.61 fps 	Chronos v2: 27.09 fps 	Chronos Fast: 26.3 fps 	

Agreed. How are we supposed to ‘test’ if we don’t even know what the changes are.

Either way, this new Chronos is so slow there’s no point in playing with it further, especially when they won’t tell us how it differs from the other Chronos models.

1 Like

Please make “Export As …” as the default option. I too often forget to switch it and end up exporting to where I don’t want it to. Also this version again shows blotchy parts maybe because of the motion deblur option. The new Chronos delivers a flickering by inserting black frames.

https://youtu.be/P060Fr2rddo

Hi Greg.
I installed it, updated the license and did not download the models.
I attach a screen photo and registration.
Greetings
Processing: logsForSupport.tar.gz…Processing: 2023-04-01-22-35-11-Main.tzlog…

Uploading: logsForSupport.tar.gz…
Processing: 2023-04-01-22-35-11-Main.tzlog…
Uploading: image.png…

Also, consistent naming schemes would be nice for the future.

For example, in the benchmark tool, the new Chronos is called Chronos while the old Chronos is called Chronos v2. This implies that the old Chronos is actually the new one when in reality it isn’t.

For me personally, the new Chronos should be called Chronos v3 so we know it’s newer than the old one (and it is chr-3 that in the command line, but not in the GUI)

4 Likes

the old chronos got a higher version number? I thought chronos v2 is the new one. :frowning_with_open_mouth:

The OLD Chronos is called Chronos v2 and it uses the code name chr-2 in the command line.
The NEW Chronos is called Chronos v3 and it uses the code name chr-3 in the command line.

The NEW Chronos is available in the GUI under the name Chronos.
You can not select to use the OLD Chronos from the GUI.

The OLD Chronos is in the benchmark, it is called Chronos v2
The NEW Chronos is in the benchmark, it is called Chronos.

In what Scenario should the new chronos (should be called v3 or v3a if experimental) be used over apollo?

1 Like