Fails to import correctly Topaz VAI generated mp4 (both AVC and HEVC)

andreas-georgiou wrote on 8/20/2025, 10:22 AM

When importing Topaz Video AI generated MP4 either H264 (AVC) or H265 (HEVC) Vegas pro 22 (B250) reads the frame rate as 12,800.00 and as such when added to timeline only adds the first few seconds. see attached screengrabs

Also a template of 240fps is somehow loaded, complete mess preventing editing Topaz VAI V 6.2.2 2025 generated files.

any thoughts help?

Comments

VEGASDerek wrote on 8/20/2025, 10:24 AM

Please provide a Media Info readout of some of this media which Vegas is having problems importing.

3POINT wrote on 8/20/2025, 10:24 AM

What does Mediainfo say about those MP4's?

3POINT wrote on 8/20/2025, 10:25 AM

Derek was a split second faster...😁

andreas-georgiou wrote on 8/20/2025, 10:27 AM

andreas-georgiou wrote on 8/20/2025, 10:33 AM

andreas-georgiou wrote on 8/20/2025, 10:34 AM

rgr wrote on 8/20/2025, 11:45 AM

Use Media Info program. Topaz generates such rubbish files.

1. Run VirtualDub in copy mode – it should help.
2. Use ProRes in Topaz – but it seems to have bugs too.
3. It's generally best to export to FFV1 in Topaz and recompress to ProRes/H26x in ffmpeg.

J-Toresen wrote on 8/20/2025, 1:01 PM

@andreas-georgiou

The Picel aspect ratio is not correct. I should be 1,0 for progressive videos.

jt

andreas-georgiou wrote on 8/20/2025, 2:58 PM

j-T Thanks, they only play properly with VLC media player others fail to play the files also, Pixel aspect ratio would change the size of the image?

I need to run Topaz AI as the footage is AVI 3/4 aspect interlaced it does a very good job in cleaning it up, de-interlacing, de-noising, upscaling etc.

rgr Thanks, I have tried intermediate conversions to correct it but I loose quality.

 

The big question is why is Vegas reading the file as 12,800 fps and when is set to set project to the media settings it comes up with such a weird template?

its only the last few updates that have broken their render codecs I think as it used to work fine in the past despite all the bugs i reported to them.

 

The guys (not sure if there is a team?) are very responsive but they are constantly messing around with the UI breaking parts of functionality instead of focusing on what is important to users IMHO

3POINT wrote on 8/20/2025, 3:15 PM

@andreas-georgiou I would use Topaz to cleanup the final edit made with Vegas and not trying first to cleanup the footage with Topaz and than start editing that footage. With other words, I would use Topaz at the end of the editing stage and not at the beginning.

andreas-georgiou wrote on 8/20/2025, 3:34 PM

Thanks 3POINT, I usually do that, but even then clients cannot play the mp4's on their devices as they do not play in a number of windows players including cyberlink media player, power DVD etc. they play fine if one installs VLC free player very odd, so the bugs are in the exported files and not Vegas me thinks.

So my thoughts were that I could import to Vegas then export from vegas as their codec seem more universally playable nowadays...

J-Toresen wrote on 8/20/2025, 3:51 PM

@andreas-georgiou

I think you should present the problem in the Topaz Video forum.

jt

J-Toresen wrote on 8/20/2025, 3:58 PM

@andreas-georgiou

You have three fundamentally different problems.

1. Convert 4:3 video to 16:9 format. In this case, you need to crop the 4:3 video.

2. Deinterlace interlaced video.

3 Upscale cropped video to 1920x1080 size.

Jøran

 

andreas-georgiou wrote on 8/20/2025, 4:28 PM

 

J-Toresen, thats the beauty of topaz, it upscales to fhd maintaining aspect ratio, it de-interlaces, it de-noises, improves resolution! (like magic) but sucks at exporting in a universally playable format, most windows and smart devices refuse to play it although the free vlc player has no issues (go figure)

andreas-georgiou wrote on 8/20/2025, 4:40 PM

I am in discussions with topaz Suport team, send log files etc they are investigating, but not absolutely sure it’s not a vegas issue too? Why does mp4 properties clearly show fps as 25 yet vegas imports the file but somehow thinks it’s 12,800 fps? And when added to timeline only adds a fraction of 1 sec instead of 1.5 hours of video I think there is also a vegas issue somewhere in the depths of its algorithms

andreas-georgiou wrote on 8/20/2025, 4:42 PM

A free video VLC player plays the video flawlessly at the correct frame rate etc yet expensive all singing dancing players like cyber link etc do not load or play the topaz exported video

Last changed by andreas-georgiou on 8/20/2025, 4:43 PM, changed a total of 2 times.

System details

Vegas pro 22 build 250

Windows 11 pro ver. 23H2 64 bit

CPU Intel i7-10700k

MEM 64GB

GPU gigabyte aorus  GeForce RTX2070 super Manually disabled OC.

andyrpsmith wrote on 8/20/2025, 5:06 PM

Looking through these posts I see a few have asked for media info from this free utility below but it has not been given. Here is the link to the utility:

https://mediaarea.net/en/MediaInfo/Download

Down load the utility and post the output on this forum to provide a comprehensive readout of the media information that Topaz is generating. It may help solve the problem.

(Intel 3rd gen i5@4.1GHz, 32GB RAM, SSD, 1080Ti GPU, Windows 10) Not now used with Vegas.

13th gen i913900K - water cooled, 96GB RAM, 4TB M2 drive, 4TB games SSD, 2TB video SSD, GPU RTX 4080 Super, Windows 11 pro

andreas-georgiou wrote on 8/21/2025, 7:11 AM

Thanks for the link andyrpsmith! got the mediainfo from Microsoft store so here are the two exports for AVC and HEVC renders.

--------------------------AVC-------------------

General
Complete name             : G:\temp\Yiota_Guy_Wedding1-4_1_iris3.mp4
Format                    : MPEG-4
Format profile            : Base Media
File size                 : 8.73 GiB
Duration                  : 1 h 18 min
Overall bit rate mode     : Variable
Overall bit rate          : 16.0 Mb/s
videoai                   : Enhanced using iris-3; mode: auto; revert compression at 0; recover details at 0; sharpen at 0; reduce noise at 0; dehalo at 0; anti-alias/deblur at 0; focus fix Off; and recover original detail at 20. Changed resolution to 1920x1080
encoder                   : Lavf61.9.100

Video
ID                        : 1
Format                    : AVC
Format/Info               : Advanced Video Codec
Format profile            : High
Format level              : 4
Format settings, CABAC    : Yes
Format settings, Referenc : 3 frames
Codec ID                  : avc1
Duration                  : 1 h 18 min
Bit rate mode             : Variable
Bit rate                  : 15.7 Mb/s
Maximum bit rate          : 16.0 Mb/s
Width                     : 1 920 pixels
Height                    : 1 080 pixels
Display aspect ratio      : 1.896
Frame rate mode           : Constant
Frame rate                : 25.000 FPS
Color space               : YUV
Chroma subsampling        : 4:2:0
Bit depth                 : 8 bits
Scan type                 : Progressive
Bits/(Pixel*Frame)        : 0.302
Stream size               : 8.55 GiB (98%)
Color range               : Limited
Codec configuration box   : avcC

Audio
ID                        : 2
Format                    : AAC LC
Format/Info               : Advanced Audio Codec
Codec ID                  : mp4a-40-2
Duration                  : 1 h 18 min
Bit rate mode             : Constant
Bit rate                  : 320 kb/s
Channel(s)                : 2 channels
Channel layout            : L R
Sampling rate             : 48.0 kHz
Frame rate                : 46.875 FPS (1024 SPF)
Compression mode          : Lossy
Stream size               : 179 MiB (2%)
Default                   : Yes
Alternate group           : 1
 

==================================HEVC=================================

General
Complete name             : G:\temp\Yiota_Guy_Wedding1-4_prob4.mp4
Format                    : MPEG-4
Format profile            : Base Media
File size                 : 8.57 GiB
Duration                  : 1 h 18 min
Overall bit rate          : 15.7 Mb/s
videoai                   : Enhanced using prob-4; mode: auto; revert compression at 0; recover details at 0; sharpen at 0; reduce noise at 0; dehalo at 0; anti-alias/deblur at 0; focus fix Off; and recover original detail at 20. Changed resolution to 1920x1080
encoder                   : Lavf61.9.100

Video
ID                        : 1
Format                    : HEVC
Format/Info               : High Efficiency Video Coding
Format profile            : Main
Format level              : 4
Format tier               : Main
Codec ID                  : hvc1
Duration                  : 1 h 18 min
Bit rate                  : 15.4 Mb/s
Width                     : 1 920 pixels
Height                    : 1 080 pixels
Display aspect ratio      : 1.896
Frame rate mode           : Constant
Frame rate                : 25.000 FPS
Color space               : YUV
Chroma subsampling        : 4:2:0
Bit depth                 : 8 bits
Scan type                 : Interlaced
Scan order                : Bottom Field First
Bits/(Pixel*Frame)        : 0.297
Stream size               : 8.39 GiB (98%)
Color range               : Limited
Codec configuration box   : hvcC

Audio
ID                        : 2
Format                    : AAC LC
Format/Info               : Advanced Audio Codec
Codec ID                  : mp4a-40-2
Duration                  : 1 h 18 min
Bit rate mode             : Constant
Bit rate                  : 320 kb/s
Channel(s)                : 2 channels
Channel layout            : L R
Sampling rate             : 48.0 kHz
Frame rate                : 46.875 FPS (1024 SPF)
Compression mode          : Lossy
Stream size               : 179 MiB (2%)
Default                   : Yes
Alternate group           : 1
 

Last changed by andreas-georgiou on 8/21/2025, 7:26 AM, changed a total of 1 times.

System details

Vegas pro 22 build 250

Windows 11 pro ver. 23H2 64 bit

CPU Intel i7-10700k

MEM 64GB

GPU gigabyte aorus  GeForce RTX2070 super Manually disabled OC.

andyrpsmith wrote on 8/21/2025, 7:25 AM

Great well done, I know the users on this forum will likely know what is going on and may be able to determine which parameters maybe causing the incompatibility.

Steve_Rhoden wrote on 8/21/2025, 7:30 AM

@andreas-georgiou You can try just dropping those Topaz Video into Shutter Encoder then easily export it as MP4..... It's MP4 outputs are compatible with everything.

andreas-georgiou wrote on 8/21/2025, 7:38 AM

does using shutterencoder to convert loose quality?

3POINT wrote on 8/21/2025, 8:25 AM

does using shutterencoder to convert loose quality?

When shutter Encoder does re-encoding, yes, like any other re-encoding software (also Vegas). When shutter Encoder only needs to rewrap or to conform, than no.

rgr wrote on 8/21/2025, 8:51 AM

J-Toresen, thats the beauty of topaz, it upscales to fhd maintaining aspect ratio, it de-interlaces, it de-noises, improves resolution! (like magic)

Well, it doesn't do magic.
1. Deinterlace is mediocre compared to QTGMC.
2. Denoising is simply really poor quality, especially compared to Neat Video.

3. Upscale -- for the Proteus filter, it uses the standard Lanczos filter from ffmpeg, available everywhere for free :) There are better tools (the two images at the bottom are Topaz).
https://forum.videohelp.com/attachment.php?attachmentid=61319&d=1634438832

or

https://imgsli.com/MjkwNDU3 (clouds)

but sucks at exporting in a universally playable format, most windows and smart devices refuse to play it although the free vlc player has no issues (go figure)

In addition, exporting from Topaz often results in color distortion, e.g. exporting to ProRes often results in saving the file in BT601, even though the source was in BT709.

My advice -- stay away from this unless you are a real expert or keep the originals.

The minimum you need to do is deinterlacing and denoising in another program. Topaz can do some upscaling and sharpening if needed, and it might not ruin too much.

 

3POINT wrote on 8/21/2025, 9:04 AM

@andreas-georgiou What I see in your Mediainfo is that the result is still recognized as interlaced. IMO HEVC cannot be interlaced, must be progressive. Probably that's why it's not recognized by Vegas.