Hi, this report was created with the help of ChatGPT…
Subject: Topaz Video 1.7.0 – HEVC enhancement failure caused by hardware decoding regression
Hello Topaz Support,
I have identified a reproducible problem with Topaz Video 1.7.0 which does not occur in version 1.6.1.
System
-
CPU: Intel Core i9-13900K
-
GPU: NVIDIA RTX 3090 (24 GB)
-
Source: HEVC/H.265 MKV, 1280×720, Main 10, 23.98 fps, yuv420p10le
-
Source encoder: Lavc 62.32.100 hevc_nvenc
-
Same source file and same enhancement settings were used for both tests.
Problem
The exact same video and enhancement successfully completes in Topaz Video 1.6.1, but fails in 1.7.0.
Comparing the two generated FFmpeg commands reveals a significant change in the video decoding path.
Topaz Video 1.6.1:
The source HEVC video is decoded using the normal software decoder:
Stream #0:0 (hevc) -> tvai_up
There is no -hwaccel option and no hwdownload stage.
The decoded frames are then passed to the Topaz AI processing (tvai_up) and subsequently encoded using hevc_nvenc.
Topaz Video 1.7.0:
The command now includes:
-hwaccel cuvid
and the filter chain includes:
hwdownload,format=nv12,format=rgb48le,tvai_up=...
The 1.7.0 log subsequently reports:
Error creating a MFX session: -9
with:
[hevc_qsv]
followed by:
Error initializing an MFX session
and:
Error decoding header
The process eventually fails with:
Invalid output format nv12 for hwframe download.
and:
Error reinitializing filters!
Important observation
Although the system uses an NVIDIA RTX 3090 for Topaz processing, the 1.7.0 log shows an attempt to initialise Intel QSV/MFX (hevc_qsv) during the hardware-decoding process.
This does not occur in 1.6.1.
The source file itself is demonstrably valid because the exact same file completes successfully using 1.6.1.
Conclusion
The evidence strongly suggests a regression in Topaz Video 1.7.0’s hardware video decoding / FFmpeg hardware-frame handling.
In simplified form:
1.6.1
HEVC → software decode → Topaz AI (RTX 3090) → NVENC → successful
1.7.0
HEVC → hardware decode/CUVID → QSV/MFX initialisation failure → hwdownload failure → enhancement aborts
I have attached the .tzlog files from both the successful 1.6.1 run and the failed 1.7.0 run for comparison.
Please could this be passed to the development team for investigation?
If possible, an option to disable hardware video decoding and revert to the 1.6.1-style software decoding path would also provide a useful workaround.
Thank you.
Kind regards,
Andrew
2026-08-14-10-40-46-Main_1.7.0.tzlog (216.2 KB)
2026-08-14-11-04-53-Main_1.6.1.tzlog (1.6 MB)