Originally Posted by Stephen Warren
Any problem that appears in both Xv and VDPAU is most likely unrelated to the driver; the two driver code-bases are entirely separate. Perhaps an incorrectly encoded file, a corrupted file, or a HW issue?
I'm not sure if it was also with XV, but I thought so (was very late and I felt like braindead
But nevertheless, why would it be unlikely to be a driver issue? XV and VDPAU are HW accelerated, right? If some algorithm or timing is wrong, it could miscalculate the pixelvalues and probably set the alpha values wrong because of overflows?!
Since I have no clue about the Nvidia driver and the HW acceleration via VDPAU/XV I can just guess. If this also happens with XV, and the code bases are seperate, what could affect both? Just timings of memory/GPU/bus? Some filters/videomixers in the GPU?
I wonder why it only happens on bigger dark areas like shadows. But maybe it also happens on bright areas. Since the underlying window is white, it would not be visible.
I need to check that, but at the moment I reverted to 256.53 to see if this issue still appears.
But of course it could be an HW issue. If it is, there should be a workaround. As far as I understand, mostly the ION has this issue?!
File should be ok, was playing fine with X11 video output. Also my Laptop plays it correctly.
I'm also not able to check it, since I do not have the hardware at the moment, could take some time.