I don’t know if people are still having this problem, but I was recently able to discover a fix that has been working for me. It’s basically the same as what gargamel314 above suggested but with some slight differences. Not sure if it’s a combination of the updates or anything I did, but I do know my issues with the program are resolved and my conversions are proceeding as they used to. So, here are the steps I went through:
Updated Intel Arc drivers to current (31.0.101.4255)
Updated Topaz Video AI to current (v3.1.10)
Preferences/Output and turn Video Export to Without Preview
Preferences/Application - Auto-Play Preview to Disabled, AND
Preferences/Application - Allow Anonymous Data Collection - Unchecked
Not sure exactly which one of these things fixed the problem, but I’m very glad to have the program working again. Hope this helps.
nope, that was not effective. It still came back unknown error. It’s some kind of error with FFMPEG. I’m attaching my Windows Error logs if anyone is interested. Also, here’s the critical section of my VEAI logs:
2023-03-26 22-15-44.988 Thread: 21136 Info OUT: 3 2023-03-26 22-15-44,988 Thread: 8128 Critical OpenVino inference failed: clFinish
2023-03-26 22-15-44,988 Thread: 8128 Critical Error debug information
2023-03-26 22-15-44,988 Thread: 8128 Critical Unable to run model with index 0 it had error:
2023-03-26 22-15-44,988 Thread: 8128 Critical Caught exception in tile processing thread and stopped it msg: unable to run model with index 0 1
2023-03-26 22-15-55.810 Thread: 18436 Warning Device loss detected in Present()
2023-03-26 22-15-55.810 Thread: 18436 Warning Graphics device lost, cleaning up scenegraph and releasing RHI
2023-03-26 22-15-55.977 Thread: 21136 Debug passProcDone 0 3 3 -1073740791 1
2023-03-26 22-15-55.978 Thread: 21136 Info EXITED: 3 -1073740791 1
2023-03-26 22-15-55.979 Thread: 21136 Info ~TProcess(): destroyed
I’m not sure if this is a intel driver issue since my RTX3090 also is not being used (neither its huge amount of memory) during the export.
It there a way to redirect it to pytorch? It seems faster.
Hi everyone! We are looking into this issue and we believe that the next major release will resolve this. For now, I am going to mark this as resolved and when the build is released if anyone runs into this, please reply here. Thanks!
soooo… so far. I’ve reinstalled Video AI, I’m on the most recent update, and I reinstalled the Intel Drivers to the most recent version. Still fails after about 6 minutes into upscaling.
No VEAI fix applied. Completely new install of Video AI and drivers. Disabled Auto-Preview and collecting of anonymous data.
Disabled Auto-Preview and collecting of anonymous data -Here’s what I’ve testing and works:
Outputting Proteus Fine-Tune/Enhance in Auto for ProRest 422 HQ .mov also seems to work for all of these preview conditions.
Update 1:
Scratch that -
15sec Preview, 1080p to 4K Proteus Fine-Tune/Enhance in Auto for ProRest 422 HQ .mov fails after just about 2 minutes into the render. Should have taken about 3 1/2 minutes. (unknown error)
Update 2:
After 3 “reprocesses”, it was able get to 3 1/2 minutes @ 99% and fail. (unknown error)
Update 3:
15sec Preview, 1080p to 4K Proteus Fine-Tune/Enhance in Auto for H265 Main10 (INTEL). Completed in 4min.
@nicholas.ferrara Hi! Sorry for being MIA, I have been unexpectedly out of the office for the past couple of weeks.
Intel and our team have identified the issue and there is currently a driver fix that is in final stages of preparation for release. This bug affects Topaz Video AI as well as any other program that relies on the GPU to decode videos, including Davinci Resolve. We hope to see this fix go public as soon as possible and once again we thank you for your patience.
Interesting… I was experiencing multiple issues in DaVinci Resolve as well, I had assumed they had something to do with the Intel drivers, but I didn’t assume it was the same issue. Looking forward to the update, super impressed with the quick turn-around time and commitment from you and your team!
[If you are posting a new bug, please include the following]
The bug / behavior you have encountered
Sorry, I know you said you fixed this in version 3.2, but it’s even worse now than it was. In version 3.11 I was able to get some renders through using the latest Intel drivers (version 4255 and Beta version 4257) if I disabled interpolation during upscaling, or disabled enhancement during interpolation. With version 3.2, every render fails regardless of settings. Sometimes they don’t even make it through a 10s preview.
Your system profile
ASUS Strix Z690-A D4 Wifi
Intel i7-13700K
32GB G.Skill RipjawsV DDR-4000
Arc A770 LE 16GB at stock settings, WHQL driver version 4255
Samsung 980 Pro 1TB
Your log files (Help > Logging > Get Logs for Support) logsForSupport.tar.gz (601.7 KB)
Unfortunately, there are still many issues with the ARC GPUs that should be addressed by new driver updates from intel.
We are working closely with Intel get the issues resolved and have the app working reliably for long videos.
Intel is claiming that all issues are fixed in the latest beta drivers released last week.
Install the latest version of the app with the latest beta driver from intel.
Avoid using the intel encoders for output and let me know if you have any issues.
Let us know if you are still having issues with detailed logs for us to look at.
