Software: FC8 x86_64, 8.2 fglrx
Hardware: 690G/X1200 IGP
Since XV will never be supported on Avivo cards, and
since TexturedVideo is not yet supported on Avivo cards (in the x86_64 architecture) ...
I use GL for rendering video. However, I see bizarre corruption which consists of disjoint vertical bands which have disjoint pieces of the image. I have observed this behavior mplayer, xine, and in other opengl applications, including games and rendering the interface for mythtv.
Here's the kicker: Thing work properly about 20% of the time. I can start (e.g.) mplayer, and see a corrupted, unwatchable video. Kill it, restart with the exact same command, and things work just fine! There is no obvious pattern (it can take 10 or 12 times to get it started properly, or it can work correctly twice in a row). This same behavior is seen with other applications and non-full screen applications.
The "multiple of 64" virtual screen size workaround is irrelevant. Images can work, or not work, regardless of whether the image size is a multiple of 64.
Anyone one else run into this? Could it be an interaction between various loaded X modules or enabled extensions?
Hardware: 690G/X1200 IGP
Since XV will never be supported on Avivo cards, and
since TexturedVideo is not yet supported on Avivo cards (in the x86_64 architecture) ...
I use GL for rendering video. However, I see bizarre corruption which consists of disjoint vertical bands which have disjoint pieces of the image. I have observed this behavior mplayer, xine, and in other opengl applications, including games and rendering the interface for mythtv.
Here's the kicker: Thing work properly about 20% of the time. I can start (e.g.) mplayer, and see a corrupted, unwatchable video. Kill it, restart with the exact same command, and things work just fine! There is no obvious pattern (it can take 10 or 12 times to get it started properly, or it can work correctly twice in a row). This same behavior is seen with other applications and non-full screen applications.
The "multiple of 64" virtual screen size workaround is irrelevant. Images can work, or not work, regardless of whether the image size is a multiple of 64.
Anyone one else run into this? Could it be an interaction between various loaded X modules or enabled extensions?
Comment