| >The only video filter I have sometimes used is deinterlacing I don't know about anything else, but ffmpeg has some deinterlacing filters that run on the GPU. So your one example is a bad one. >Anyway, discussing about this is besides the point, and forgive me from the rant above. Next time can you please not post the rant? It's not interesting to parse through all that just to get to the point. It's also extremely uninteresting to have this conversation like "well I haven't personally used that so it must not be important". VLC and ffmpeg are used by millions (billions?) of people, so can we at least agree that neither of our own very particular and personal use cases are that important? >But the entire point of TFA is to (dynamically) go back to a model where the GPU is _not_ in the middle. No? Overlays are entirely driven by the GPU. The entire reason these are performant is because it's zero-copy from a GPU buffer to an overlay. >And that model -- sans GPU -- happens to match what Xv was doing and is actually faster and less power consuming than to always blindly use the GPU which is where we are now post-Xv. I have no idea what you're talking about. XV (with a driver that supports it) uses the GPU to do the overlays. If you aren't using any filters, this should have the same power consumption as XV. |