Topaz Video AI Performance Alpha 3.2.0.2.a

Hi All,

Here is an early version of app that should improve performance for all machines. The degree of performance increase will vary. This version should also allow for better support running multiple filters and multiple processes.

Download: Win | Mac | Mac Update

Please upload problem videos and logs here: Submit Files

Changes from 3.2.0.1.a

  • Speed up for Apollo
  • Speed up for Stabilization
  • Using single process is faster for non Nvidia GPUs
  • GUI updates from 3.1.9 and beyond

Known Issues:

  • Proteus Auto will not work, use Proteus with manual settings

Thank you for testing

PS: Since this is an alpha version, it will not interfere with Beta or Release versions on the machine.

4 Likes

This version is not always faster than the latest official build:

3.2.0.2.a
image

3.1.9
fed8039ea40d0f21c9cc6f94afa4c4da118185fe

1 Like

Apollo is faster though, and that’s part of what was done in this release.

3.2.0.2.a

Topaz Video AI Alpha  v3.2.0.2.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: 0.95 instances: 0
Input Resolution: 1920x1080
Benchmark Results
Artemis		1X: 24.16 fps 	2X: 10.76 fps 	4X: 2.84 fps 	
Proteus		1X: 19.21 fps 	2X: 9.4 fps 	4X: 2.76 fps 	
Gaia		1X: 12.3 fps 	2X: 8.04 fps 	4X: 3.57 fps 	
4X Slowmo		Apollo: 24.32 fps 	Chronos: 27.28 fps 	Chronos Fast: 29.91 fps 	

3.1.9

Topaz Video AI  v3.1.9
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: 1
Input Resolution: 1920x1080
Benchmark Results
Artemis		1X: 19.99 fps 	2X: 7.05 fps 	4X: 2.09 fps 	
Proteus		1X: 14.37 fps 	2X: 6.31 fps 	4X: 1.9 fps 	
Gaia		1X: 13.33 fps 	2X: 7.71 fps 	4X: 3.03 fps 	
4X Slowmo		Apollo: 19.07 fps 	Chronos: 24.63 fps 	Chronos Fast: 25.9 fps 	

1 Like

Apollo is slower in the 3.2.0.2.a (1.06 fps) compared to the 3.1.9 (1.14 fps) on my AMD Ryzen 7 5800U. Also Chronos is slower but Chronos fast is faster.

Your own benchmark screenshots show it’s faster (9.71 fps in Alpha, 8.64 in 3.1.9). I’m confused.

I was speaking about the AMD comparison I made. Should have posted the right screenshots tough. :slight_smile:

I wanted to notify the developers that the automatic update of this Alpha version is still not working properly: I now have version 3.2.0.1.a… and if I try from the programme to search for other, more recent versions, it tells me that the one I have is the latest version available, whereas this new version 3.2.0.2 has been released!
Can you solve it? thanks!
ps. i also note that the download of new updates made directly from the program is VERY slow, compared to the automatic update of PhotoAI which instead downloads updates much faster!

1 Like
Topaz Video AI Alpha  v3.2.0.2.a
System Information
OS: Windows v11.2009
CPU: AMD Ryzen Threadripper 3960X 24-Core Processor   127.88 GB
GPU: AMD Radeon PRO W6800  29.618 GB
Processing Settings: device: -2 vram: 1 instances: 0
Input Resolution: 1920x1080
Benchmark Results
Artemis		1X: 10 fps 	2X: 5.86 fps 	4X: 1.93 fps 	
Proteus		1X: 9.48 fps 	2X: 5.85 fps 	4X: 1.91 fps 	
Gaia		1X: 4.73 fps 	2X: 3.18 fps 	4X: 2.15 fps 	
4X Slowmo		Apollo: 12.59 fps 	Chronos: 5.51 fps 	Chronos Fast: 10.1 fps 	

Topaz Video AI  v3.1.9
System Information
OS: Windows v11.2009
CPU: AMD Ryzen Threadripper 3960X 24-Core Processor   127.88 GB
GPU: AMD Radeon PRO W6800  29.956 GB
Processing Settings: device: -2 vram: 1 instances: 1
Input Resolution: 1920x1080
Benchmark Results
Artemis		1X: 6.51 fps 	2X: 4.57 fps 	4X: 1.52 fps 	
Proteus		1X: 6.83 fps 	2X: 4.39 fps 	4X: 1.56 fps 	
Gaia		1X: 4.15 fps 	2X: 3.25 fps 	4X: 2.04 fps 	
4X Slowmo		Apollo: 12.57 fps 	Chronos: 5.79 fps 	Chronos Fast: 7.25 fps 	

Topaz Video AI Alpha  v3.2.0.2.a
System Information
OS: Windows v11.2009
CPU: AMD Ryzen Threadripper 3960X 24-Core Processor   127.88 GB
GPU: AMD Radeon PRO W6800  29.618 GB
Processing Settings: device: -2 vram: 1 instances: 0
Input Resolution: 768x576
Benchmark Results
Artemis		1X: 33.86 fps 	2X: 21.54 fps 	4X: 6.99 fps 	
Proteus		1X: 31.38 fps 	2X: 20.59 fps 	4X: 6.99 fps 	
Gaia		1X: 16.1 fps 	2X: 10.86 fps 	4X: 7.56 fps 	
4X Slowmo		Apollo: 39.37 fps 	Chronos: 16.33 fps 	Chronos Fast: 27.37 fps 	

Let’s talk about quality, let’s take denoising.

I have learned something new by being involved in astrophotography.


In astrophotography, multiple images of the same celestial object are often taken in succession. This is done to reduce noise and other disturbances that may be caused by the camera. When these images are then stacked, the signals from the celestial objects are combined and amplified, while the noise is reduced.

Stacking images can reveal fine details of celestial objects that would otherwise be obscured by noise or other disturbances. Additionally, weak signals that would otherwise be undetectable can be amplified.

Stacking images is typically done with specialized software that automatically aligns and combines the images. The individual images are shifted so that the celestial objects are precisely aligned in all images. Then, the stacked image is optimized using special algorithms to achieve the best possible result.


Stacking images helps to reduce noise, enhance details, and reveal faint features that may not be visible in a single exposure. Stacking software uses algorithms to analyze each image and determine which pixels contain signal and which ones contain noise. The final stacked image will have a higher signal-to-noise ratio than the individual frames, making it easier to see faint structures in the object being imaged.


This means that these images or this output is actually exactly the one you want to have for training.


I wanted to evaluate this today by doing an astro-processing with a normal object (village from some distance).

At night but also during the day.


In relation to the topic, I noticed that, for example, artemis makes the dark areas lighter when denoising and everything disappears somewhat in the average.

Based on my old knowledge, this is not bad, but now I know that it can be done differently.



Single ISO 200 image (30 seconds of Exposure) - Unprocessed but Profiled by Adobe Camera RAW.



Full Astro-Processed image. (124 Stacked images with data (so-called lights), 130 Bias (Sensor Readout noise images), 50 Flat images (Without data, to calculate out the lens darkening, and the matching dark flats (50 images) (to get the readout noise from the flats)

There are also darks, which are made with the same exposure time as the lights, but no light falls on the sensor.

All in all, quite an effort for a single image.

Processed with Siril-Beta and Photoshop (32bit to 16bit conversion + Streching (Editing)), denoised with NoiseXterminator ← Astro AI denoiser.


I must emphasize that I am still in an early stage.



This is the output from stacking (32 bit).



This is a undenoised ISO 200 images, but its processed.


denoiseraw
Denoise-RAW


DxO
DxO - (XD)


Both DxO and DenoiseRAW are not suitable for any kind of Astro-Processing workflow.



Averaged output from Artemis low.
The dark area is no longer dark, the image (Video) becomes flat.

2 Likes

Post updated.

Updatet once again.

Sorry for Spamming.

you could just edit the original post with a notification about the updates. :slight_smile:

Unfortunately, I can’t do much about the integrated graphics performance. Looking at the RTX performance still hopefully Gaia should also be faster.

1 Like

New Alpha is available with support for all models.

2 Likes