Topaz Video AI 6.2

Hi everyone, today’s 6.2 release for Video AI includes improvements to EXR handling, RTX 5000 series optimization, and support for Google and Apple single sign-on.

6.2.0


Changelog:

  • Login flow updated.
  • TensorRT 10 update for 5000 series NVIDIA GPUs.
  • Improved export error messaging.
  • Disabled app actions on Welcome screen.
  • Fixed EXR to TIFF conversion sometimes rendering invalid TIFFs.
  • Fixed FPS counter in Cloud export view.
  • Pass crop to fit properly in cloud.
  • Fixed opening area for preset dialog.
  • Scale CPU usage utilization reduced for 2x/4x outputs.
8 Likes

Thanks. Short tested in V6.2 frame interpolations with different output codec and models. Input test-file was 25fps h264 mp4, produced no VFR. Output was set to 50fps, everything fine. Then I took FFV1 source and did Aion 50fps and MediaInfo shows VFR. The same file with MKVToolnix remuxed into MKV container and Mediainfos says it’s constant framerate, as it should be.

So TVAI produces no VFR but something happens wrong with container tags, pending on input file codec/format. It’s not a big problem, but when other programs reads out fps from container, worse things could happen. To reproduce import ffv1 source into TVAI, do frame interpolation and check result with MediaInfo.

Left shows VFR with crazy max fps, on the right the same video after remuxed into mkv shows CFR

4 Likes

This is a brand new video by ArtIsRight.

Topaz Video AI Test | Mac Studio M3 Ultra, M4 Max, & Mac mini M4 Pro

4 Likes

I can’t get the preview system to work at all :frowning:

It adds entries into the preview menu and they all complete to 100% and “done”, but nothing ever changes on the screen to the right (Where the preview always was in earlier versions)

And when I click “Show in explorer” nothing happens.

I can’t even clear the cue (All entries just remain)

I’m on windows11 and RTX5080.

Same here the preview doesn’t work at all for me whatever I try to do - importing tiff sequence. I’m on a 4090

I was 15 updates behind. Time to roll the dice. If things go weird I’ll fully uninstall and reinstall from scratch.

Edit: I’m getting around 15-18 fps with a 5090 using Rhea from a 480p video to 4k.

2 Likes

Preview still doesn’t work with ProRes 422 HQ, unfortunately. I’m not sure if this is a known issue; it could just be a personal problem.

Also, the timeline scrubber isn’t aligned with the increments and has weird, glitchy movement when you hold the left click on it.

Also also, preview doesn’t work in general sometimes. ProRes, H.265, H.264, doesn’t matter; it turns green on the bar, but then it just turns gray again as if I never even clicked preview. It might be a problem with my footage. I export with ProRes 4444 XQ; I’ll try with ProRes 422 HQ. It happens when I export with AVI as well. However it does work when I use the “Render In > Out.”

1 Like

Same problem here and not only with ProRes; Preview V6.2 seems generally broken. They gets generated, but not shown into TVAI. You have to open TVAI preview folder and play the preview files in your player.

2 Likes

Some good news: The benchmark for 6.2 says that Nyx runs at like 6.4 fps on my system, where it was running at like 9.8 fps. Processing real videos, it would usually get around 9.3 fps. I just did a test and it was able to get 9.6 fps, so 6.2 has not regressed like I was worried about.

3 Likes

Interesting video. Is the presenter correct that TVAI for macOS isn’t utilising the hardware encoder/decoder engine? This would seem to be a bit of an oversight if true and could make a huge difference to throughput.

I can see it being something that you have to pay Apple to get access to development resources for—something no one in the ffmpeg development community is going to do.

Quite a difference in performance for some models…

Topaz Video AI  v6.2.0
System Information
OS: Windows v10.22
CPU: Intel(R) Core(TM) i9-14900K  127.8 GB
GPU: NVIDIA GeForce RTX 4090  23.576 GB
GPU: Intel(R) UHD Graphics 770  0.125 GB
Processing Settings
device: 0 vram: 1 instances: 0
Input Resolution: 1920x1080
Benchmark Results
Artemis		1X: 	37.87 fps 	2X: 	18.42 fps 	4X: 	04.82 fps 	
Iris		1X: 	34.54 fps 	2X: 	18.13 fps 	4X: 	05.06 fps 	
Proteus		1X: 	43.99 fps 	2X: 	19.32 fps 	4X: 	05.37 fps 	
Gaia		1X: 	14.75 fps 	2X: 	10.92 fps 	4X: 	04.77 fps 	
Nyx		1X: 	13.06 fps 	2X: 	09.00 fps 	
Nyx Fast		1X: 	31.00 fps 	
Rhea		4X: 	04.59 fps 	
RXL		4X: 	04.44 fps 	
Hyperion HDR		1X: 	28.99 fps 	
4X Slowmo		Apollo: 	38.63 fps 	APFast: 	65.99 fps 	Chronos: 	27.94 fps 	CHFast: 	41.11 fps 	
16X Slowmo		Aion: 	35.72 fps 	

Topaz Video AI  v6.0.2
System Information
OS: Windows v10.22
CPU: Intel(R) Core(TM) i9-14900K  127.8 GB
GPU: NVIDIA GeForce RTX 4090  23.576 GB
GPU: Intel(R) UHD Graphics 770  0.125 GB
Processing Settings
device: 0 vram: 1 instances: 0
Input Resolution: 1920x1080
Benchmark Results
Artemis		1X: 	42.86 fps 	2X: 	18.81 fps 	4X: 	04.92 fps 	
Iris		1X: 	41.51 fps 	2X: 	20.88 fps 	4X: 	04.96 fps 	
Proteus		1X: 	40.20 fps 	2X: 	18.53 fps 	4X: 	05.22 fps 	
Gaia		1X: 	15.70 fps 	2X: 	11.21 fps 	4X: 	04.68 fps 	
Nyx		1X: 	17.94 fps 	2X: 	14.92 fps 	
Nyx Fast		1X: 	34.52 fps 	
Rhea		4X: 	04.42 fps 	
RXL		4X: 	04.50 fps 	
Hyperion HDR		1X: 	32.21 fps 	
4X Slowmo		Apollo: 	38.38 fps 	APFast: 	77.11 fps 	Chronos: 	33.24 fps 	CHFast: 	34.78 fps 	
16X Slowmo		Aion: 	35.28 fps  
5 Likes

proteus v4 Version deleted

The Apple Video Toolbox API gives direct access to the hardware encoders so I wouldn’t have thought this needed any great effort to implement.

When trying to download the stabilization model via the model manager, I get an error that says “Error: connection handling cancelled”. This happens when gpu (4090) and auto are selected for the device.
image

2 Likes

Never mind then. No idea why no one has bothered to put it in yet.

Exact same issue with the exact same GPU.

1 Like

Testing for MacOS seems vastly inexistent with Topaz software, also any kind of optimisation :cry:

Turn on the Advanced features option to have access to all of the iterations of the models.
image

1 Like

A quick look at the ffmpeg command line is enough to show that Video Toolbox is being used whenever possible for hardware encoding - h.264/5 (HEVC) and ProRes. Also, there is no additional GPU / CPU usage shown when those codecs are being used, which also indicates encoding is being done in hardware.

Thanks.

Andy