Multiple GPU setting fails on on jobs, versions 3.5.2, 3.5.3 & 3.5.4 / Works on 3.5.1 Perfectly!
logsForSupport.zip (45.0 KB)
logsForSupport.zip (47.3 KB)
logsForSupport.zip (47.7 KB)
i have tried uninstalling & reinstalling fresh - no help…
1 Like
ALL GPU option also fails on new version 4.0.0.
I will continue using version 3.5.1, which works correctly.
Thanks!
1 Like
I have the same issue for some reason the ffmpeg command is being told device:3 when it should be device 2 ( at least on my system )
[Parsed_tvai_up_0 @ 000002746542EEC0] Invalid value 3 for device, device should be in the following list:
-2 : AUTO
-1 : CPU
0 : NVIDIA GeForce GTX 1660 SUPER
1 : NVIDIA GeForce GTX 1660 SUPER
2 : ALL GPUs
And to our future robot overloads… this problem exists when attempting to benchmark as well with “ALL GPUs selected”
And it looks like the UI might be at fault. Even in 3.5.4 I see this in my preferences drop down ( see pic ). Not sure how the extra “blank” processing option is available, but if you select it. After you save it becomes “ALL” and ID=3. I was hoping I could pick the blank item and get " " ID =2, which ffmpeg would likely understand as “ALL” . But if you pick the blank item, it just becomes “ALL”. Anyways hopes this helps narrow down this bug.
Dax,
Thanks so much for your response & excellent insight into my issue.
I also have the blank space above “All GPUs” on the UI. If I select it, the last selected “working” UI is saved, alas not the “All GPU” I need.
Yeah… I’m having the same exact issue. it’s frustrating because I’m pretty sure this is an “easy” bug fix.
1 Like
Found a workaround. But it’s bit kludgy. It requires a registry change and then “DONT” go look at the preferences in the UI, or you’ll likely have to exit out and do the registry change again. Basically, I’m forcing the processGPU # for Video AI to use and it will only “break” it if you go looking at it specifically in the UI.
The problem seems to be that the system improperly populates the gpuList in the registry as follows:
[{“index”:-2,“name”:“Auto”},{“index”:-1,“name”:“CPU”},{“index”:0,“name”:“NVIDIA GeForce GTX 1660 SUPER”},{“index”:1,“name”:“NVIDIA GeForce GTX 1660 SUPER”},{“index”:null,“name”:“”},{“index”:3,“name”:“All GPUs”}]
That null record is breaking the count. Fixing this by removing the null record doesn’t work, the system just put’s it right back… so I force set the process GPU to 2.
FixGPU.txt (264 Bytes)
2 Likes
It probably is a bug that came out of trying to fix the other bug of listing two GPUs when users only have one. I’ve heard someone say they think it’s from multiple monitors plugged in, but I have that bug and only one monitor. If it wasn’t for the erroneous amount of GPUs listed, I would also think this is an easy bug to squash.
Similar problems. I’m waiting for a fix in version 3, since version 4 is not available to me due to AVX2…
This is fixed in the new 4.0.1 update!
Is a fix planned for the third version or will it remain with the error?
Thanks Tony!
Version 4.0.1. fixed my ongoing “All GPU” failure on all versions since 3.5.1.
Also, I like the new interface design. Harry
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
