<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [VP2] Chroma planes are vertically stretched during VDPAU playback" href="https://bugs.freedesktop.org/show_bug.cgi?id=82255#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [VP2] Chroma planes are vertically stretched during VDPAU playback" href="https://bugs.freedesktop.org/show_bug.cgi?id=82255">bug 82255</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>The source data is messed up. Just look at the luma/chroma planes that you captured. The overall image is 1280x544. Which means that each field is 1280x272. And chroma would be 640x136 These look great: gm display -size 1280x272 gray:sv0-texture0 gm display -size 1280x272 gray:sv0-texture1 These... don't: gm display -size 640x136 gray:sv1-texture0 gm display -size 640x136 gray:sv1-texture1 Note that texture1 has *some* stuff in it... and trying to display it as gm display -size 1280x68 gray:sv1-texture1 Shows *some* stuff, but not that much. Of course, vdpau *generally speaking* works on vp2, so it's highly unlikely that the decoding step is entirely broken. It must be some bit of sampler view setup, I guess. I'm also guessing that you somehow messed up capturing the contents of the chroma since it should have had 2 components, not 1 (which is probably why the 1280 stride works out for the chroma image that has something in it).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>