Video AI v5.2.1: AI Processor preference not working

In preferences under the Processing section, the AI Processor setting keeps reverting to auto and the program will use my CPU instead of GPU. No matter how many times I select my GPU and save the setting it reverts to auto. I am on the latest version and have tried reinstalling the program to no avail.

logsForSupport.zip (501.8 KB)

System specs:
i9 10900k
RTX 3090 FE
64GB DDR4-3600 RAM

2 Likes

I have noticed this problem specifically during batch processing. Despite having 5.2.1 configured specifically to use the GPU via the AI Processor setting, the program will revert to Auto at some point during the batch process - invariably picking the CPU as the AI Processor.

I have to stop the batch process and close all files, delete the current project, restart the program, and change the AI Processor selection to “fix” the problem.

This behavior is happening on two separate machines

  • Threadripper 3970x & RTX 2080TI
  • Threadripper PRO 7985WX & RTX 4090
1 Like

Same problem here. I start the batch processing in the evening and let it run overnight. On the 3rd or 4th video, 5.2.1 switches from the GPU to the CPU as the AI processor. Instead of 16-18 fps, the video is processed at 0.5 fps.
Setting the AI processor in the Preferences doesn’t work. I select my RTX 4090 as the AI processor in the settings and save the settings. If I then open the settings again, the AI processor is back to Auto.

System specs:
i9 14900K
RTX 4090
96GB DDR5-6000 RAM

1 Like

Have you tried the 5.2.2.0.b version? Topaz Video AI 5.2.1 - #147 by tony.topazlabs

I just tried it on v5.2.2.0.b and it still happens. I have reverted to v5.1.4 and am no longer having the issue. I guess I’ll be using this version until it gets fixed in a future update.

Hello, thanks for testing that.

Could we take a look at your system’s hardware information for more details?

How To Obtain Your System Profile (Windows)

You can securely submit your file(s) to our Dropbox using the link below. Please be sure to send me a note to let me know you sent something.

Submit to Dropbox

1 Like

Same problem here. Sometimes it even switches to CPU on the first processing video, sometimes after 2 - 4 in batch processing. It seems random and maybe it could take even longer in batch processing, but chances are that it will happen eventually.

7950X3D
RTX 4090
64 GB DDR5-6000
Win 11 Pro 23H2

In this small sample size, we have the common denominator of the NVidia GPUs and a variety of CPUs and RAM. My guess is that a look into the source code is more promising than gathering more detailed system information.

Hello, I have the same problem. I am single file processing video files and it keeps resetting the AI processor to “auto”. I continually change it to NVIDIA GeForce RTX 4070 Ti and it resets to auto when I start processing a file. My hardware is:
i9-13900K
98 GB RAM
NVIDIA GeForce RTX 4070 Ti

I am running version 5.2.1

Thank you

Hi Marc and all

I can’t be certain but I’m fairly sure this might have something to do with the “device=-2” parameter which is now being used constantly in the ffmpeg command line. -2 equates to “Auto”. In turn, I can only assume this is due to the new so-called “Pro” version for multiple GPU processing. So with their usual way of doing things, and without telling us, Topaz has decided that “Auto” is good enough the the rest of us. How wrong that is. I’ll be going into further detail in a separate post.

It is still possible to override this using the command line. I find it best to use “device=0” on my Mac Studio M1.

Thanks.

Andy

Update - On further experimentation on my old Intel Macbook Pro, I found that whenever other changes are made in the UI - e.g. change of crop dimension or model, the AI Processor then reverts back to “Auto”, even though I previously set it to “AMD Radeon Pro…”. This is a absolutely a bug.

(The AI Processor option was removed some time ago for Apple Silicon Macs so presumably “Auto” is now being used by default in this case.)

Thanks.

Andy

Latest update has fixed this issue. Big thank you to the staff!

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