|
madshi, could you add support for either arithmetic operators, or some more measures of throughput in the profile select rules? I ask because I'm pretty sure the amount of time it takes my GPU to apply a particular filter scales linearly with the amount of pixels it has to process. So if I know it can handle a particular profile for 720p30, I'd like to use that as an upper limit, so it uses the same profile up to 1280*720*30 = 27648000 pixels per second.
In a profile select rule, I imagine this would work like (srcWidth * srcHeight * deintFps <= 27648000), or (srcPixels * deintFps <= 27648000), or (srcThroughput <= 27648000), depending on what is available. Adding support for arithmetic operators (or at least multiplication) would generalize the rule selection nicely. In my case, I'd probably combine this with (srcWidth == targetWidth or srcHeight == targetHeight) to know when I only have to worry about chroma scaling.
|