totem-gstreamer should use bilinear filtering when scaling without Xv
Bug #66666 reported by
David Gerber
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gstreamer0.10 (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: totem-gstreamer
I have a setup where Xv doesn't work. I know, that's something else to fix. autovideosink is able to chose ximagesink properly on such a setup, but there's no way to instruct videoscale to use bilinear filtering.
My suggestion would be to have totem-gstreamer insert videoscale in the pipeline (if not already done) and tell it to use method=1 which is bilinear filtering. Nearest neighboor is simply too ugly.
If bilinear filtering CPU consumption is an issue, make it optional through a gconf key or so. Or make a smart assumption regarding the host's CPU speed.
To post a comment you must log in.
Thanks for your bug. That looks like an upstream gstreamer wishlist, reassigning, if anybody familiar with those details want to forward it he's welcome