Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DPIR + OV_GPU + tiles => vspipe freeze #50

Open
Selur opened this issue May 7, 2023 · 2 comments
Open

DPIR + OV_GPU + tiles => vspipe freeze #50

Selur opened this issue May 7, 2023 · 2 comments

Comments

@Selur
Copy link

Selur commented May 7, 2023

When using:

clip = vsmlrt.DPIR(clip,model=1,strength=5,tiles=8,backend=Backend.OV_GPU(fp16=True)) # model=1 <> denoise, model=3 <> deblocking

vsviewer simply freezes at the end of the processing. (save if I open the script in a viewer and try to close it)
Other backends work fine only when OV_GPU is used (fp16=True/False) the whole vspipe&co freeze at the end of the processing.

Is it a bug, or a known limitation, or am I missing something??

@WolframRhodium
Copy link
Contributor

What is the output of vspipe with -e 2?

@Selur
Copy link
Author

Selur commented May 8, 2023

Using: VSPipe.exe c:\Users\Selur\Desktop\test_1.vpy -e 2 -c y4m NUL --progress
with:

clip = vsmlrt.DPIR(clip,model=1,strength=5,tiles=2,backend=Backend.OV_GPU(fp16=False)) # model=1 <> denoise, model=3 <> deblocking

I get:

Script evaluation done in 2.42 seconds
Output 3 frames in 0.42 seconds (7.13 fps)

then it freezes, neither vspipe nor the gpu do seem to use any resources.
I have to kill vspipe over the taskmgr to stop it.
Same when using -i, I only get: Script evaluation done in 2.42 seconds
Strange thing is, yesterday it did return when I didn't use 'tiles=...' now it also freezes when use OV_GPU in general.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants