AkarinVS
AkarinVS
Thanks for the report. I will take a look, but it will probably take some time.
I've committed support device_id to the repository but the code is not yet tested, so it's not released yet.
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...
Interesting. The handling of and/or/xor are almost exactly the same, so it's very unlikely there are bugs that only affect xor but not and/or (which are used much more often)....
Thanks for the request. I will do it once I find some free time.
how about adding a mechanism to compute a plane only as needed? Most filters are processing each plane separately, and if a filter is only used by a ShufflePlane that...
the PR looks good. thanks. which version of llvm are you using?
Definitely possible to extend the current design to support this case as well, but I'm worried about the inconsistency in API. for int/float frame properties, it's fair to limit `x.Prop`...
@NSQY I'm curious, what's the use case for accessing `_PictType` in `Select`?
Replacing `FrameEval` that creates new filter instances will definitely be out of scope for the plugin. However, I suggest that you use a previewer that can display user defined frame...