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

DLISR: Function does not take argument(s) named device_id #4

Open
Ichunjo opened this issue Aug 15, 2021 · 2 comments
Open

DLISR: Function does not take argument(s) named device_id #4

Ichunjo opened this issue Aug 15, 2021 · 2 comments

Comments

@Ichunjo
Copy link

Ichunjo commented Aug 15, 2021

upscale = core.akarin.DLISR(clip.resize.Bicubic(format=vs.RGBS), 2, device_id=0)
vapoursynth.Error: DLISR: Function does not take argument(s) named device_id

It's also not recognised by vsrepo stubgen so I guess it's a different version of what the README says.

if relevant:

print(
    core.akarin.list_functions(), '\n',
    core.akarin.get_functions(), '\n',
)
DLISR(clip:clip; scale:int:opt)
Expr(clips:clip[]; expr:data[]; format:int:opt; opt:int:opt; boundary:int:opt)
Version()

 {'DLISR': 'clip:clip;scale:int:opt', 'Expr': 'clips:clip[];expr:data[];format:int:opt;opt:int:opt;boundary:int:opt;', 'Version': ''}

DLVFX doesn't seem to be compiled with this version
Version() {'expr_backend': b'llvm', 'expr_features': [b'x.property', b'sin', b'cos', b'%', b'N', b'X', b'Y', b'pi', b'width', b'height', b'trunc', b'round', b'floor', b'@', b'!', b'x[x,y]', b'x[x,y]:m'], 'version': b'v0.70-0-g85a4077'}

@AkarinVS
Copy link
Owner

AkarinVS commented Aug 16, 2021 via email

@AkarinVS
Copy link
Owner

AkarinVS commented Aug 27, 2021

I tested the code, and unfortunately, it doesn't work.

I also can't make the filter interoperate with other CUDA filters, so I've updated the docs to reflect these findings.

Based on experience with users of DLISR, the recommended way is this that you use a separate vspipe stage with DLISR alone (perhaps with bm3dcpu to clean up the input).
Also, as it's extremely slow, it's beneficial to save the y4m output as a file for future processing.

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