Summary: | Small resolution video tearing problem with open source radeon drivers | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Jānis Jansons <janhouse> | ||||||
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||
Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> | ||||||
Severity: | normal | ||||||||
Priority: | high | CC: | christopher.m.penalver, hramrach, tobias.pal | ||||||
Version: | git | ||||||||
Hardware: | x86-64 (AMD64) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Jānis Jansons
2009-08-14 19:18:48 UTC
'Tearing' is a term which refers to non-smooth animation due to parts of several source frames being visible in a single output frame, which isn't what this is about. This is a problem with the bicubic filter, you can work around it by disabling the bicubic filter with something like xvattr -a XV_BICUBIC -v 0 (In reply to comment #1) > 'Tearing' is a term which refers to non-smooth animation due to parts of > several source frames being visible in a single output frame, which isn't what > this is about. > > This is a problem with the bicubic filter, you can work around it by disabling > the bicubic filter with something like > > xvattr -a XV_BICUBIC -v 0 > Thank you Michel Dänzer. You helped solve me problem I had form months! :) There is a bug which needs to be fixed, disabling the bicubic filter is just a workaround. Created attachment 28864 [details] [review] Possible fix (In reply to comment #1) > 'Tearing' is a term which refers to non-smooth animation due to parts of > several source frames being visible in a single output frame, which isn't what > this is about. Actually I misinterpreted the problem - it does look like tearing. This probably means one of two things: * The textured video blit takes too long to finish before the next output frame is scanned out. or * The textured video blit doesn't finish before the next source frame is uploaded to VRAM. If it's the first case, it boils down to 'the GPU is too slow to handle bicubic filtering without tearing, you need to disable it'. If it's the second case though, this patch may fix the tearing, though it may introduce frame skips instead. Is this still an issue with a newer driver/kernel? Jānis Jansons, Ubuntu Jaunty reached EOL on October 23, 2010. For more on this, please see https://wiki.ubuntu.com/Releases . If this is reproducible on a supported release, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal: ubuntu-bug xorg Also, please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.