Topaz Video AI v3.0.0

You know timelines don’t actually mean anything here, right? This is still BETA in the truest sense of the word.

What does the input file look like on playback through a video player application? And what is the input file format?

2 Likes

An initial release is inevitably destined to be the first public beta.

3 Likes

Minor interface issue that will need correcting:

When downloading a model for the first time, the status jumps between ‘downloading model’ and ‘loading model’ which makes it appear as if things are broken. Please correct so status remains as ‘downloading model’ until the download completes and then changes to ‘loading model’ and ‘running model’. Also perhaps keep the ‘running model’ text on the progress bar for the entirety of the processing (it currently disappears and only shows the timer/countdown/ETA).

1 Like

I installed it, but it don’t open at all. 2.6.4 still open and Gigapixel, Noise and Sharpen also do. Not sure if the requirements changed so my laptop is no longer compatible or is some kind of bug. Using an Asus laptop with Windows 11 and NVIDIA GeForce RTX 3050.

Found a micro bug: scale always gets set to 0 resulting in the wrong model being used.
For example: Running standard NTSC AR 4:3 DVD on Artemis High Quality to FHD 1920x1080.
The generated command has this: veai_up=model=ahq-12:scale=0:w=1920:h=1080
But when I change the command to contain this veai_up=model=ahq-12:scale=2.25:w=1920:h=1080, the correct model is used and the processing runs just as fast as, and the results look like they do, in 2.6.4.

I know I said scale always get set to 0, well I’ve only tested this one situation.

1 Like

Cant import videos from another pc on my local network on windows like before, so I’m copying my files to my computer before importing them, anyways great update!

That’s been my experience as well. I was going to make a post like yours in fact… I still might, but I’m waiting for 2.6.4 to finish a job on Artemis LQ Strong Dehalo v2. I looked at the same frames in 3.0, on the same model, with the same settings (confirmed same file names for models in logs), and the results are even more different than your screenshots (2.6.4 being the superior result). And it takes significantly longer.

It clearly isn’t the same model… the model file names do in fact have different checksums for the same file name.

This is clearly not ready for public release! :confused:

4 Likes

Please don’t cross post the same comment in multiple topics - once is enough.

First I was pretty excited about the new release but now that I tried it with a GaiaHQ upscale, I am afraid I will have to keep 2.6.4 running after all. I can’t really put my finger on it but with this version GaiaHQ looks awful. There is maybe less “Acid-Rain” but I get plenty of artefacts which makes it look more like a Dione upscale, which were not present before.

I can only speculate that this stems from how Pixel-Ratio is handled now. In the old version I got a 1:1 output when I used a source with 8:9 ratio. That is now flipped into the opposite. I can now choose between stretching the image out of proportion or keeping the crappie ratio from my source. I actually found it pretty handy that VEAI corrects for that, so I only needed to care for deinterlacing. Or rather I didn’t need to introduce another algorithm into the mix which potentially corrupts my source-material.

3 Likes

The following files have been uploaded
BBM_STD037.Title1_922839696_ddv3.mp4

Macbook Pro 14 (M1 Pro 16GB)
input file
.mkv 69:30 (DVD source) trim 30:55 to 32:55 (2min)
output file
2x upscale, interlaced Dione DV 2x FPS H265main mp4
output video length 32:14 (Actual Length 2min)

Awesome stuff! I hope Face Enhancement for video is coming soon.

5 Likes

Really disappointed by the fact that there is no software H264 and H265 option. Why!!!

What would be disk space and time efficient work flow now if I don’t want to use hardware encoding?

My goal is to upscale 1080p movies to 4K and encoded using H265 with the ability to adjust encoding setting to get the best balance between quality and space for the final output file.

5 Likes

Ok, I give up - where is the upscale option?
Nevermind, found it. :slight_smile:

I’ve been having fun experimenting with this new app, but like others, I think I’ll go back for a little while until some of these issues get ironed out. The deal breaker for me is that it seems to have lost the ability to accept AVISynth scripts as input, which means that I now have to create huge intermediary files. Was that deliberate, or is it a bug?

4 Likes

I keep running into errors processing a Blu-ray compatible h.264 file:

This one is related to an ffmpeg command

-vsync is deprecated. Use -fps_mode
Passing a number to -vsync is deprecated, use a string argument as described in the manual.
Could not find codec parameters for stream 1 (Attachment: none): unknown codec
Could not find codec parameters for stream 2 (Attachment: none): unknown codec
Could not find codec parameters for stream 3 (Attachment: none): unknown codec

Processing just stops and the error message can be revealed by clicking on the red “x” next to the clip.

This is on an RX6900XTX with latest AMD GPU drivers, Windows 10. Proteus relative to auto, 100% (denoise/deblock). ProRes output.

Some times, the computer just hard resets instead.

2022-10-20-12-41-51-Main.tzlog (188.0 KB)
2022-10-20-12-37-35-Main.tzlog (89.1 KB)

I have disabled “allow recovery” and am now getting these messages:

2022-10-20-13-15-15-Main.tzlog (2.6 MB)

Last message repeated 3 times
unknown SEI type 7
Finished processing frame prob-3 1 21.856000 21.856000
nal_unit_type: 6(SEI), nal_ref_idc: 0
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 0
Finished processing frame prob-3 1 21.898000 21.898000
nal_unit_type: 6(SEI), nal_ref_idc: 0

Last message repeated 1 times
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 2

Last message repeated 3 times
unknown SEI type 7
Finished processing frame prob-3 1 21.939000 21.939000
nal_unit_type: 6(SEI), nal_ref_idc: 0
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 0
Finished processing frame prob-3 1 21.981000 21.981000
nal_unit_type: 7(SPS), nal_ref_idc: 3
nal_unit_type: 8(PPS), nal_ref_idc: 3
nal_unit_type: 6(SEI), nal_ref_idc: 0

Last message repeated 3 times
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 2

Finished processing frame prob-3 1 27.277000 27.277000

unknown SEI type 7
nal_unit_type: 6(SEI), nal_ref_idc: 0
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 0
Finished processing frame prob-3 1 27.319000 27.319000
nal_unit_type: 6(SEI), nal_ref_idc: 0
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 0
Finished processing frame prob-3 1 27.361000 27.361000
nal_unit_type: 6(SEI), nal_ref_idc: 0

Last message repeated 1 times
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 2

Last message repeated 3 times
unknown SEI type 7
Finished processing frame prob-3 1 27.402000 27.402000
nal_unit_type: 6(SEI), nal_ref_idc: 0
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 1
Finished processing frame prob-3 1 27.444000 27.444000
unknown SEI type 7
nal_unit_type: 6(SEI), nal_ref_idc: 0
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 0
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 2

unknown SEI type 7
Finished processing frame prob-3 1 115.658000 115.658000
nal_unit_type: 6(SEI), nal_ref_idc: 0
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 0
Finished processing frame prob-3 1 115.699000 115.699000
nal_unit_type: 7(SPS), nal_ref_idc: 3
nal_unit_type: 8(PPS), nal_ref_idc: 3
nal_unit_type: 6(SEI), nal_ref_idc: 0

Last message repeated 3 times

nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 2
Finished processing frame prob-3 1 115.741000 115.741000
nal_unit_type: 6(SEI), nal_ref_idc: 0
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 2
Finished processing frame prob-3 1 115.783000 115.783000
nal_unit_type: 6(SEI), nal_ref_idc: 0
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 1
Finished processing frame prob-3 1 115.825000 115.825000
nal_unit_type: 6(SEI), nal_ref_idc: 0
nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 0

1 Like

Just installed the new Video AI. It is a big upgrade. Congrats and it looks promising.

I was disappointed, though, that apparently I am not able to output as mp4 from the h264 and h265 encoders. It mentions a command error. The previous version was able to do this without any issue (at least to H264).

This is the message that I get when I click on the command error:

  • Some parameter(s) may not be supported by the codec. Check FFmpeg command.
  • Current container (file extension) is not be supported by the codec. Try changing the file extension.
4 Likes

This is a huge step backwards, I sure hope I can uninstall this and get the old Video Enhance back. First and foremost, mp4 files produced by Video AI CANNOT be used in Premiere Pro, the most widely used video editor in the world!!! This is a show stopper and makes Video AI totally USELESS to me!!! In addition, anything to do with cropping is plain old wrong. It says it is producing 16:9, but the result is NOT 16:9!!! As someone else said, what’s amazing is that Topaz is releasing it with so many bugs.

7 Likes

I’ve been having lots of fun with this release.
Trying out new models and commands. This is my kind of tool!
I’ve only been using the GUI to get starting points on commands for new models, and previews.

With time, this can become a really great tool for everyone, and not just people like me who love creating batch files and scripts.

Thank you everyone at Topaz Labs! Keep on keeping on!

1 Like

It’s finally here!

Some notes/suggestions.

  • Would like to have punctuation on preset titles. I tend to do version numbers as I’m working on tuning upscales (v1.0 etc). Right now I’m doing v10, v11 etc.
  • Preview while ‘exporting’ doesn’t seem to really work terribly well, I’m assuming this is being worked on.
  • I wish it wouldn’t play the upscaled video over and over when it finishes exporting.
  • It would be nice in the GUI to be able to set the CQ when encoding x264/x265. All we get is bitrate auto? If we can’t set the CQ, at least set it on your end at 17 or less. (Really should be around 15 since for most of us the VEAI/VAI output is intermediate.)
  • This was a bug in VEAI as well, even if you ‘close all inputs’ the application still holds handles open for exported and imported videos preventing renaming, moving, etc.
  • “Grain” doesn’t look quite as good as it did with 2.6.4. (And there we had separate controls for amount and size. This just has one slider.)
  • I’m not sure if you can do this and I haven’t found it yet but it would be cool if the GUI could let us open/close the ffmpeg output window.
2 Likes