AV1 inputs cannot be previewed or exported

Topaz Video Bugs and Issues
1

I’ve originally noticed this problem in the previous Video AI app, and it is still happening in the new one. The video opens fine and can be scrubbed through, but trying to render a preview or export fails. The error in the log is always the same:

2025-09-23 05-23-04.981 Thread: 51672 Info FF Process Output: 3 e[48;5;0me[38;5;0m[av1 @ 0000019BFC7DA6C0] e[0me[48;5;0me[38;5;0mYour platform doesn't support hardware accelerated AV1 decoding.

e[0me[48;5;0me[38;5;0m[av1 @ 0000019BFC7DA6C0] e[0me[48;5;0me[38;5;0mFailed to get pixel format.

e[0me[48;5;0me[38;5;0m[av1 @ 0000019BFC7DA6C0] e[0me[48;5;0me[38;5;0mGet current frame error

e[0me[48;5;0me[38;5;0m[vist#0:0/av1 @ 0000019BFA095840] e[0me[48;5;0me[38;5;0m[dec:av1 @ 0000019BFC765A80] e[0me[48;5;0me[38;5;0mError submitting packet to decoder: Function not implemented

There are three problems with this:

  • It worked just fine a month or two ago (the same files that I previously converted are no longer usable)
  • Even if that was the case, it should surely fall back to use software decoding
  • This system has a RTX 5090 with latest drivers which does support AV1 hardware decoding
3 Likes
2

This is still an issue in the new update.

3

Maybe it renders not an the 5090 anymore, on the cpu or onboard gpu, there were such cases already.

4

It’s definitely rendering on the 5090 when I use a H264 input.

5

I’ve got the same issue on a 5080, with the same error message. AV1 input does not work.

1 Like
6

The support suggested converting the video to H264 before processing it. I mean… I guess? That doesn’t solve the bug though!

1 Like
7

Definitely not. Every encode changes the source. Plus it takes extra time out of the workflow.

8

Google Gemini read Topaz Video’s support log and reported that a memory access violation occurred, indicating that the GPU’s decoding capabilities were not being recognized correctly.

  • Product: Topaz Video 1.0.2
  • GPU: RTX 5090
9

This is STILL BROKEN in version 1.0.3. Unbelievable.

2 Likes
11

AV1 encode/decode workflows have been broken and the devs are working on a full patch to get them back as soon as they can. This stemmed from a change in FFMPEG side of things.

4 Likes
12

Still broken in 1.0.4.

14

I hope this gets fixed. I just tried to upscale an av1 youtube video I downloaded and I got this error.

15

Good news, they have in fact fixed the issue, the support provided me with a test build and I can confirm it works properly again on my computer. They said it’d be in the next release. I am not sure whether I can share this test build, however.

16

I’ve tried the beta too. There are still issues.

Failed to decode frame: Corrupt frame detected

Topaz Video cannot decode videos encoded by Topaz Video or the Nvidia App. I’m using a 5090 and encountering problems, but when I asked my friend using a 5080 to test it, he said it worked fine without any issues.

In this case, re-encoding the problematic video file to AV1 using Handbrake allows Topaz Video to decode it correctly. Of course, it must be re-encoded to AV1 with Handbrake for Topaz Video to decode it.

Additionally, when uploading Topaz Video-encoded files to YouTube, there’s an issue where HDR isn’t recognized. In this case, using YouTube’s trim feature to cut out a few frames forces a full re-encoding, resolving the HDR recognition problem.

A number of encoding-related issues keep pointing to the frames.

I’m not an expert, so this is just speculation.

17

Interesting, I didn’t try to process the same video multiple times.