I covered the openVINO runtime dlls,Run the program again，Intel GPU called,But a few seconds later,flash once blank screen,after that,unknow error.
I was getting the same issues using my A770 (export stopping after less than a minute, unknown error). I tried replacing the OpenVINO files and that appears to work.
1 Like
I’ll have to revise that statement. After letting it run the full course, it failed again “unknown error”.
Hello, back again! I missed one thing which causes issues with Photo’s sharpening and probably causes the unknown error in VEAI. Unfortunately I can’t edit the post anymore…
Rename openvino_tensorflow_frontend.dll from the downloaded Vino toolkit to openvino_tensorflow_fe.dll This should replace the existing openvino_tensorflow_fe.dll.
As for the video, I’ve noticed some failures too… I get a blackscreen then failure occasionally when I’m using the GPU for something else (e.g.: watching a VLC video). Unfortunately I don’t use VEAI as much as I do the Photo AI so there might be some combination that I don’t know about. I’ll try running a longer clip through VEAI tonight and report back if it succeeds 
Edit: things like youtube also use the GPU. One option is to disable hardware acceleration in Chrome. Kinda sucks that we have to jump through these hoops but that’s what we get for trying something new 
Edit 2: Woohooo! I got a video to finish exporting. Set the max processes to 1. It looks like there’s some funniness going on with having multiple GPU processes running at the same time. Maybe some context switching bug? 
1 Like
Sorta success… I get unknown error with motion deblur and stabilization turned on. Normal video enhance seems to work ok on the two videos I’ve tested it on. I guess we’ll just have to wait for Topaz to fix the issues.
I’ve attached a failure log to this post.
2023-03-11-03-04-31-Main.tzlog (890.7 KB)
Good morning! Would you mind reaching out to me via support with your Dxdiag and your logs?
Oh hey! sorry I read this, but it completely slipped my mind. I don’t think this is necessary anymore. The newest Intel drivers fixes this issue. 
1 Like
Please let me know if we need to spin off a different thread for my issue due to the version.
As of Intel ARC drivers past 4125, VEAI 2.6.4 has the same issues noted above. Regardless of selection, rendering falls back to the CPU and doesn’t appear to utilize the GPU whatsoever.
If I apply the openvino patching noted above, VEAI 2.6.4 will close without error when attempting to preview or run any model. 2.6.4 appears to use openvino 2022.1.0.0 and I’m trying to use it with 2022.3.0.9052.
Topaz Video Enhance AI.exe.2452.zip (4.3 MB)
2023-04-04-06-33-46-Main.tzlog (86.0 KB)
2023-04-04-06-33-46-Qml.tzlog (8.8 KB)
It looks like it’s closing due to C0000419 FAST_FAIL_INVALID_ARG, but I can’t diagnose much further past this.
IMMEDIATE EDIT
For those of you with older VEAI versions, it seems to be fixed by only updating the following files:
- openvino.dll
- openvino_c.dll
- openvino_intel_gpu_plugin.dll
You can leave the other openvino files as-is. This increased my Proteus rate from 0.96/s to 0.15/s on the A770 on driver 4255.
2nd Edit
There is an incompatibility with the calls to openvino_ir_frontend.dll in the latest openvino release and VEAI 2.6.4 that causes the crash. If you copy all the files EXCEPT the ir_frontend DLL, the optimizations will return.
Hey @XBrav, if you can copy and paste this into a new thread on the Video AI forum that would be perfect 
Hi!,
Any updates on this issue? Today I tried and noticed upon exporting Topaz Labs Video AI v3.2.2 generates Unknown Error following a black screen.
Meaning I can’t use my Intel Arc A770 16GB GPU to render in Video AI. CPU processing takes ages…
With driver 4382, VEAI 2.9.
What I don’t understand is, okay, FFMPEG has some error that it hits while encoding upscaled video. Why then does VEAI just abandon the export and not try again? Or at least save what’s already been done so at least you can piece together footage that’s been upscaled. Saving progress has been a feature that has been asked for for a very long time. Wouldn’t that solve this issue?
I just posted on my bug report on Intel’s forums asking for an update. Hopefully we will get a fix from them soon.
I’ve been using Topaz for a while and I’d like to thank you for the solution of deleting the keys from the registry folder, it worked really well.
I had an RX 590 OC and was able to render videos at 2 fps.
I switched to an RX 6700 XT and it continued rendering at 2.1 fps, reaching temperatures of 82º or more.
After deleting the folder’s registry keys, my card doesn’t go above 70 degrees and I can hit 11 fps.
Topaz Labs and Intel are working on improving performance and stability with ARC graphics cards. For now, we recommend using this specific driver version for ARC GPUs, along with version 3.1.9 of Topaz Video AI.
Topaz Labs and Intel are working on improving performance and stability with ARC graphics cards. For now, we recommend using this specific driver version for ARC GPUs, along with version 3.1.9 of Topaz Video AI.
I just wanted to check if there has been progress getting more recent versions of VEAI to work with the most recent Arc driver released last month?
I was planning to include VEAI 3.4.2 internal benchmark results for the Arc A770 both with Rebar enabled and disabled, alongside several other GPUs in an upcoming video series this month but so far can only get the application to run with Rebar disabled in the BIOS.
Unfortunately, from the information I have it seems that the Intel drivers are the problem and not our software running them.
The most stable Intel Arc driver that we have found so far is this one:
https://downloadmirror.intel.com/781650/gfx_win_101.2125.exe
I’m a little confused: after trying everything I could think of to install the driver you linked to, I finally read the readme for it and realized the file you linked me to was for Intel iGPUs, not Intel Arc discrete GPUs. That’s why it would not install on my Intel Arc A770 16GB discrete GPU even after I uninstalled my current driver.
Did you send me a different driver or is there a non-obvious way to install the driver you sent even though it is designed for different hardware ?
The driver you sent me, 101.2125, released for the iGPU line in June at around the same time as 101.4499 released for the Intel Arc discrete GPUs. Is that the link you were trying to send me?
I have put in a support ticket to Intel as per your suggestion but I want to make sure that I am starting with the version people had the most success with to get the ball rolling.
I got a new link that should work. Try this one:
deleting it also fixed it for me, thank you!
