ONNXRuntime Error about qualityscaler HOT 3 CLOSED

Hi my friend,

after some research about this error, seems to be a communication error between DirectX and GPU, typically happens with some video games as well.

The only solution seems to update GPU drivers. (I suggest using DDU to uninstall the previous drivers cleanly).

Also, some other solution could be to install PREREQUISITES libraries:

1. (If not already installed) install Visual-C-Runtimes:

   • https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/

2. (If not already installed) install Directx:

   • https://www.microsoft.com/it-it/download/details.aspx?id=35

Please, let me know if this solution fix the problem :)

.
.
.
.

For the question of "which GPU is that Performance and which Power saving".
Typically, GPU High Performance is GPU 0 visible in the Task Manager, while GPU Power Saving is GPU 1 in the Task Manager; but these indices may reverse if the PC is plugged in.

from qualityscaler.

Thanks for the quick response.

I performed all the installs and updates noted.

• Running 3.4 resulted in the same error.
• Monitoring the task manager GPU graphs, "High Performance" activates GPU 1 on my machine which is the NVIDIA.
• • Found 3.1 on my cloud backup, ran it and it also had the same error. Assuming possibly that my NVIDIA is borked.
• Switching to the "Power Saving" activated Intel Iris GPU 0 and I did not see the same error.
• However, I am now seeing consistent cases where not all extracted frames are upscaled which eventually causes a file not found error when combining upscaled frames at the end of the process.
• • I am currently attempting this on a local drive. All my previous uses have been to files on an external drive.
• • My standard image format selection has been jpg. If the error happens again on the local drive, I will try again with png to see if that makes a difference.
• • if problem continues, will communicate via separate thread to avoid conflating two separate issues.

If there is a way to get more detailed logs, let me know.

from qualityscaler.

Testing the same files on the local drive and with my original settings completed with out a problem. So I believe both the original GPU error and later failure to generate all upscaled frames could be contention issues writing to the external drive. While the external drive worked fine with QualityScaler for many months, as we all know, drives can have performance issues as they age.

Closing this as it is now looking like it is not a QualityScaler issue.

Thanks for the handy tool.

from qualityscaler.