Topaz Video AI 6.2.2 2025 generated MP4 files fail to load into Vegas pro 22 (b250)

MP4 files generated by Topaz video AI fail to add correctly after importing into Vegas pro 22 build 250. It reads the frame rate as 12,800.000 and only adds a microscopic part of the start of the video to the timeline

Could it be that some metadata or frame rates are not specified in the created files?

Device name DESKTOP-P3MO9IM
Processor Intel(R) Core™ i7-10700K CPU @ 3.80GHz (3.79 GHz)
Installed RAM 64.0 GB
GPU Nvidia Aorus rtx2070 super

|System type|64-bit operating system, x64-based processor|

Edition Windows 11 Pro
Version 24H2
Installed on ‎05/‎12/‎2024
OS build 26100.4946
Experience Windows Feature Experience Pack 1000.26100.197.0

logsForSupport.zip (14.3 MB)




Looking at your screenshots you shared, it looks like the file is being shown as 25fps outside of Vegas, but 12,800 inside correct?

What were the export settings from Video AI? Looking through the logs I am not seeing the file referenced in the screenshots to check.

Thanks for as usual prompt response, appreciated.
yes the original AVI and exported fps are 25, when imported to vegas it shows astronomically strange import settings. Topaz VAI codec settings as per attachment, tried both H264 as well as H265

There were more users on the Vegas forum complaining about buggy Topaz VAI exports and suggested various intermediate conversions …

The exports also fail to play in various windows players apart from VLC this i did report previously I think. Each time I try to use VAI it gets very frustrating as the UI is changing and functionality of some parts is braking with each update, that’s why I rarely use it now and have stopped updating which is sad as it is a very good concept.

Please focus on getting highly efficient and universally playable export codecs (very important to users)
also preview is broken i think as after rendering the selected segment it now stutters when previewed as if it is trying to re-render in real time very strange, it was working great in earlier versions, what have they broken?

Some additional info
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

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

Hi Kyle, any updates please?

I have not been able to reproduce this issue yet on my end and the team has it on their list for investigation but I do not have an update back from them at this time.

Let me check in and see where this stands, we did have some users report that they have seen users that reported using a constant bit rate amount helped in some situations but not all.

Don’t know why I’ve not seen this post before, but it’s of extreme interest to me. I’ve just finished a very lengthy series of 3X upscales with Starlight Mini - sorry, not on AI 6, but AI 7 - that took nearly a month of 24/7 operation. I broke the original video 5-minute segments to guard against one failure taking out everything previously finished.

As the segments finished processing, I’d load them into Vegas Pro on a different computer to check on the results, and I saw some very odd things happening. The first thing I noticed was odd waveforms on the audio of the first two or three segments. The left channel was pretty well maxed-out, amplitude-wise. When played, it sounded like loud white or pink noise. The right channel looked to be essentially flat, but when played, was clearly the wrong speed, sounding like 2 or more times the correct playback pitch, and maybe speed, too, but I really didn’t try to evaluate it. It was just clearly messed-up! Subsequent files turned out ok, audio-wise.

Then the weirdness kicked it up a notch. The experiment just mentioned was done with Vegas Pro 19. These files couldn’t be imported into Vegas Pro 21 and 22. There were some very strange, outrageously high framerates showing in the import panel and Vegas said ‘Uh, uh - not gonna do it…’

So I opened the project in Vegas Pro 19, where the video was ok, but the audio was messed up, and saved it under a new name on a network drive, where I could load try to load it into VP22 on my newest, most capable computer, which had been tied up with Starlight Renders for so long. It wouldn’t load into 22. So I did what seemed to be logical: I tried to load this VP19 file into VP19 on this second computer. It would not recognize the video files, just as they had been shutout on VP21 and VP22 on the other computer, but worked ok on VP19.

I’ve looked at these files with MediaInfo and can’t really see what the issue is, although I’m far from expert in figuring these things out.

My purpose in documenting this is not to seek a solution from Topaz on this specific issue, only to to send along the idea that there are some strange things going on at times. For the record, I currently have good video files from my Starlight Mini mp4 files, and have them all on the timeline along with the original audio file from the single, large source file. So I can finish the project from here, but it sure would be nice to know why VP19 behaved differently on one computer than the other. (I looked at preferences, which appear to be identical. Codecs, given that they’re loaded by Magix upon installation, should be the same as well.)

You did not say what codec and file type you were using for the final file - MP4, MOV etc?

At the onset of the project, I had only a modest amount of experience with Video AI, and basically accepted the default encoder and container settings. So the output format was AVC/H.264 .MP4.

The files all played without problem in VLC, but exhibited the cited problems with the 3 versions of Vegas Pro, with the radical exception of behaving differently in VP19 on two different computers that had that version installed.

Tried both h264 and h265 xxx.mp4 sound=convert

1 Like

I used ‘Copy’, which had always worked ok in previous tests. But it might be worth giving ‘Convert’ a try…

I usually use sound=copy but some cases the sound is MP3 or some other format so had to convert.

The rendered files play fine in VLC but not in any of the other 5 apps I usually have and not sure if it will play on smart TV’s and phones which makes the renders useless, for a very expensive program (same money gets you vegas pro a fully fledged video editing software) Topaz I find sadly very buggy

Just for the record, even though the thread has drifted away from the original topic, I would like to report that selecting Convert under Codec settings/Audio mode, rather than Save has corrected the problems I was having with various versions of Vegas Pro not recognizing audio in the MP4 files that Video AI was writing.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.