Topaz Video AI Beta v3.3.4.0.b

[jacob.muchow]

Hello everyone,

We have another beta available for your testing.

Downloads:

• Windows
• Mac - DMG | PKG
• Ubuntu 22.04

Changelog from 3.3.3:

• Adds option to export settings allowing a custom start frame number to be set for image sequence exports.
• Adds a new preference for default start frame number when exporting an image sequence and not matching the input (ex. if you want first frame to be 0000.png vs. 0001.png or 0042.png)
• Adds “.3gp” as an available file type when importing videos through the file opener.
• Fixes bug causing image sequences to be re-exported with start frame off by one when matching start frame from import.
• Fixes color space issues when importing image sequences and exporting as video. Color space will be converted to BT709 when input color space is RGB & exporting to YUV pixel format.

Known Issues:

• Videos with mismatched metadata and streams will display incorrect duration
• Frame number preview length may shorten on app restart
• Export settings from old presets might not be applied correctly. Try creating a new preset if this happens to you.

---

Please upload problem videos and logs here: Submit Files.

[UHD4KUser]

I’ll repeat what I said before, as I still see these issues in v3.3.4.0.b

I hope v1 of Iris is either being adjusted or v2 is in the works due to the issues reported, and hopefully noticed by the dev team:

Topaz Video AI Beta v3.3.2.0.b

Regrettably still seeing the ghosting/blending issues I’ve mentioned about Iris v1 in previous versions since the model was released. I really hope the devs are paying attention to this and other issues with Iris v1 and are actively working on it. Original frame: [image] After Iris V1: [image] As you can see the black areas in-between the blue lines are now blue-ish, and the black area on the white portion to the upper left has a greenish tint to it. Iris v1 or v2 needs to not have frame bl…

Topaz Video AI Beta v3.3.2.0.b

Yes, it doesn’t fix it or make it any better. I believe it’s an inherient problem with the Iris and the Proteus models. Here’s an example of the ghosting issue: Original frame: [image] Iris v1: [image] Proteus v3: [image] The pink section goes across the screen from right to left, and the video with Iris v1 leaves a “trail” whereas the original does not. The ghosting is less, but not 100% gone with Proteus v3 (note the light grey object, which has some pink tint to it), and unlike Iris v…

Topaz Video AI Beta v3.3.2.0.b

As reported in 3.3.1, I would like to report on the color alteration. The following is a comparison of the output as-is and the output through the TVAI filter (Iris) using FFMPEG’s built-in test image generation function. Premise The TVAI filter is internally processed in RGB, not YUV, so the test images are generated in RGB and saved as PNG (RGB). Since the TVAI filter refers to the previous and next frames for processing, about 30 frames are output, and the 15th frame (10 or more identical…

[martinsawicki]

The issues you are talking about are major model bugs.
These 3.x.x.x updates focus more on the functionality of the app.
Previously mentioned by one of the devs: these bugs will be fixed in major model updates in the future. Think they’re talking about TVEAI 4.x

[TicoRodriguez]

Proteus 3 black splotche blotting

Black splotche blotches occur in Proteus 3. DxDiag.txt (103.2 KB) I use CLI. "C:\Program Files\Topaz Labs LLC\Topaz Video AI\ffmpeg" -y -i %1 -sws_flags spline+accurate_rnd+full_chroma_int -filter_complex tvai_up=model=prob-3:scale=4:compression=0:details=0:noise=0:blur=0:halo=0:preblur=0 -an -c:v prores_ks -profile:v 3 -vendor apl0 -pix_fmt yuv422p10le "%~n1_xx.mov" [167org] [167] Several people have reported the same bug in the past.Seems to occur at 4x. https://community.topazlabs…

I would like to add this bug as well.
This bug has been occurring since v2.x, but has not yet been addressed.

It was wrongly hypothesized that it was GPU heating (≒user’s problem), but this was denied.
However, it has not been resolved yet.

[martinsawicki]

Updating the apps: Final or Beta doesn’t work for me.

Each time I do this loading a file fails. Doesn’t know any picture and can’t adjust anything. It does show the file in the inputs section. Uninstalling and reinstalling fresh fixes this.

Really annoyed with this to be honest

[j.norum]

Preview doesn’t immediately show the frames. Only after it process it. It shows up

[ida.topazlabs]

Hi there! I followed up with you on the original thread

[ida.topazlabs]

Processing will need to reach a certain point prior to the preview being displayed, however, if it is not showing until the very end make sure that live preview is enabled.

[myerpj]

I’m getting the first frame in preview, but then no other frames, and obviously it’s not playing. Auto-Play preview is on. Moving the time indicator on the timeline does not change the frame.

[martinsawicki]

I also have the same issue. In the previous version it showed the frames already processed when you dragged, It doesnt in this. I have live preview enabled

[ida.topazlabs]

yikes! Can you share a quick screen recording? Logs, etc?

Oftentimes it is easiest to share a screen recording for issues like this to quickly show me exactly what is happening. I use Loom for screen recordings since this is a free and easy to use app.

[jo.vo]

The “fill all RAM + swap before encoding” bug on the Apple silicon architecture is still there:

(happens only with the Iris model and only when actually upscaling and Ram usage set to 100% in settings).

[UHD4KUser]

Yes but I and others have found that if you don’t remind them, they’re less likely to fix the issues. Issues like these have been a problem with Proteus as well, and that’s not been fixed…

[martinsawicki]

I mean… three people said it. When you hit preview. You only see the 1st generated frame. After the preview is done rendering you can hit play and it plays fine.

Previously you could skip forward frames while it was rendering…

Dunno if it has to do with the output format or not. But it worked on PNG and ProRes in the previous BETA

just try it yourself

[jo.vo]

I can skip through frames while the preview is still rendered? ProRes 422 Proxy.

[ida.topazlabs]

It does not happen to me This is why I asked you for the information requested.

[d.raebiger (DReffects)]

I am having trouble with both moving the program window over different screens (cannot grab the menu bar) and audio export. “auto” mode sometimes work, sometimes does not (for the same clip)

[martinsawicki]

I uploaded a 7min screenrecording of 3.3.3 and 3.3.4.0b with the same video and previewing. Now I got a processing error too (didn’t happen before). Might be cus I had them both open at the same time.

I added logs too.

[jo.vo]

Upscaling from SD sources on Apple Silicon still is much faster when setting RAM to 10%:

Topaz Video AI Beta  v3.3.4.0.b
System Information
OS: Mac v13.04
CPU: Apple M2 Ultra  64 GB
GPU: Apple M2 Ultra  48 GB
Processing Settings
device: 0 vram: 0.1 instances: 1
Input Resolution: 720x480
Benchmark Results
Artemis		1X: 	60.25 fps 	2X: 	37.08 fps 	4X: 	14.90 fps 	
Proteus		1X: 	63.64 fps 	2X: 	35.13 fps 	4X: 	11.47 fps 	
Gaia		1X: 	29.58 fps 	2X: 	17.86 fps 	4X: 	12.82 fps 	
4X Slowmo		Apollo: 	63.65 fps 	APFast: 	196.90 fps 	Chronos: 	19.84 fps 	CHFast: 	29.02 fps 	

Versus at 100%:

Topaz Video AI Beta  v3.3.4.0.b
System Information
OS: Mac v13.04
CPU: Apple M2 Ultra  64 GB
GPU: Apple M2 Ultra  48 GB
Processing Settings
device: 0 vram: 1 instances: 1
Input Resolution: 720x480
Benchmark Results
Artemis		1X: 	34.88 fps 	2X: 	27.95 fps 	4X: 	08.70 fps 	
Proteus		1X: 	34.68 fps 	2X: 	21.74 fps 	4X: 	06.75 fps 	
Gaia		1X: 	25.88 fps 	2X: 	18.60 fps 	4X: 	12.12 fps 	
4X Slowmo		Apollo: 	56.31 fps 	APFast: 	149.89 fps 	Chronos: 	12.22 fps 	CHFast: 	16.67 fps 	

[martinsawicki]

Weird. Guess that architecture is a hard nut to crack…