Topaz Video AI Beta 5.3.3.2.b

Hello everyone,

Today we are publishing a new beta update to Video AI, version 5.3.3.2.b.


New in 5.3.3.2.b:

  • Fixed issue where AV1 was available for cards not supporting it.
  • Fixed incorrect end trim marker when placed on the frame before last.
  • Removed autozoom of timeline on rendering a preview.
  • Modified “Reset timeline zoom” button functionality to match with the older versions.

5.3.3.2.b

New in 5.3.3.0.b:

  • Updated batch processing
    • Updated flow
      • If you dont change settings with multiple sources selected, batch processing will use each videos unique settings.
      • If you do change settings with multiple sources selected, batch processing will propagate the changes you made to every input video.
    • Fixed multiple resolutions and model settings applying across wrong videos.
  • Added feature to recommend models based on input video height.
  • Enabled selection of recommended models automatically when enabling Enhancement filter.
  • Fixed playhead centering issue when quickly playing and pausing videos.
  • Fixed playhead disappearing when going out of visible timeline range.
  • Fixed bug where timeline is missing a major tick.
  • End major tick now only visible if minor ticks follow.
  • Fixed timeline padding issue.
  • Fixed several issues with the Sources hovertip of input items.
  • FPS in Sources hovertip now will update with changes in input settings for image sequences.
  • Fixed precision for FPS field.
  • Fixed AV1 option appearing for certain AMD GPUs that do not support AV1.
12 Likes

VERY cool!

I really like the long list of fixes :slight_smile:

I’m dying to try it, even if it means suspending my current encodings ^^

  • No FFV1 fix however :frowning:
2 Likes

what issue was there with FFV1?

@tony.topazlabs You can use FFProbe to Identify the video
properties to make options for the command line.Color Overides Produce Resolutions Errors.

2 Likes

I meant FFV1 8K output YUV 4:2:0 10b, it produces errors either “Resolution error” or simply “Error”
This is an issue with a constant that has been set 10 years a ago

I sent some explanations here

I know ther’s a .json file to configure the encoder, but thing the patch should be done by topaz in some definitive ways, so the info hasn’t to be grabbed here and there from the forum

Since the latest GUI changes I can not figure out what the original pixel width and height of the source video is. Except in the Preview info line. But it is nowhere shown in the resize output resolution dialog. Why does the Enhancement dialog always revert back to Proteus? What is this icon for:
image

Isn’t it recommended model for upgrading video stream ?
I did notice that it changes depending of the resolution and quality of my file (suggested Nyx and Gaia)

When I load a certain preset for use with Iris it seems to show Proteus either selected or only suggested. This looks confusing to me.

Is this the same issue I noticed? I set a video to Rhea, set all the sliders, ran a preview, and when I clicked the original video again after having clicked the preview, the enhancement was back on Proteus but the sliders were where I had set them with Rhea.

1 Like

Yes, that sounds like the same issue I noticed!

Found a new candidate to push the Sharpness to 100% (and Recover detail to 50) with Rhea
All other are estimate and they are very low.

image
RXL still still does weird things frame to frame. It looks like it intends to do some motion compensation with a great failure.

In fact, it looks like all VC-1 are great candidates

Giving it to my Ada with Hyperion overlay 8K ouput. To me, this model change the app. and my mind, there so few tuning.


1 Like

do you find those settings to retain more details?
is that your current default settings when you attempt to upscale?

My base is taken from a recent movie where I found these settings almost by chance.

So it became a base for all my “upgrades”. For the current test, much older, the movie being 95% of the time in dark scene, the real lack of details due to age and compression does not give such a good result, but, it is still clearly better than any other model, and I repeat the quality is constant, there are no rotten teeth or disgusting eyes.
So this time I used Rhea

The hair is also excellently restored. We can even see the eyelashes and eyebrows!

1080p source

8K Rhea + Theia + Hyperion (HDR badly set, too much expo.)

EDIT : Just noticed that 1080p is max pic on forum …

i know there’s very few mosquitos here and there, but they are very small, like 5 pixels, in a 8K frame, with a downscale and some SSIM compression, it will be done.
Moreover when animated your much rather take care of sharp edges than tracking a mosquito, I can’t see them, and I am not very tolerant toward this ^^

2 Likes

When I import a video in old TV aspect ratio 4:3 and choose 1280 x 720 output format the new image gets distorded:

When I just keep the Original aspect ratio instead it’s correct:

normally it should just add black bars when the aspect ration changes but the image itself should be still fine!

Is it a new behaviour with the beta ? if not I suspect bad handling of metas, metas that does not exist in such old gen video.
I did realize it with the patch I’m coding, in fact there were almost nothing ratified as a norms in MPEG1/2 gen.

do you actually own an 8K TV that you feel the need to upscale to that high resolution?

No, but I have a video projector, SXRD matrix with an X1 processor forming an image of 300x170cm, on which we see the slightest defect, so yes 8K is very useful to me. If it’s not 8K, I can still go up to 4096x2160p higher than UHD 3840x2160p, so I can “pick” pixels from the movies by removing the black bars

As I said, I’m currently testing either 8K downscaled by the X1, or 8K that I’m going to re-encode in 4K in Lanczos/Callmut

Only a “last gen” console is able to generate an optimal image for me, either RGB (detected in BT.2020) 4K HDR 60fps YUV 4:2:2 or 30fps YUV 4:4:4 and again the visual difference is clear and sharp compared to the “classic”
Sadly Sony removed the 4096x2160p in order to be fully compatible with UHD, but it does not matter as I don’t use it to play videos

1 Like

@tony.topazlabs : I’m aware that there is a dedicated Linux build thread, but it’s going ignored for a long time now, despite various friendly nudges and attempts to establish proof of life. I feel sufficiently frustrated as a result to ask here - is there any plan to resume Linux builds, or is that exercise now paused/abandoned?

1 Like

the trim function is so laggy that I it is impossible to set the input and output mark. :neutral_face:

The application leaves a lot of data trash behind after finishing its work and closing. Look at all those temporary video files. :neutral_face:

Some videos can not be processed dropping an error. It is the same with version 5.3.2. Here are the log files. logsForSupport.zip (1.7 MB)