<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [gst-vaapi] H264 video playback regression between 5fe72d9 and 0.5.5" href="https://bugs.freedesktop.org/show_bug.cgi?id=67190#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [gst-vaapi] H264 video playback regression between 5fe72d9 and 0.5.5" href="https://bugs.freedesktop.org/show_bug.cgi?id=67190">bug 67190</a> from <a class="email" href="mailto:gb.devel@gmail.com" title="Gwenole Beauchesne <gb.devel@gmail.com>"> Gwenole Beauchesne</a> <pre>(In reply to <a href="show_bug.cgi?id=67190#c10">comment #10</a>) > Created <a href="attachment.cgi?id=83901" name="attach_83901" title="gst-launch debug output under wayland">attachment 83901</a> <a href="attachment.cgi?id=83901&action=edit" title="gst-launch debug output under wayland">[details]</a> > gst-launch debug output under wayland In gst-libs/gst/vaapi/gstvaapiwindow_wayland.c:302, around the "XXX: use VPP to support unusual source and destination rectangles" comment, you could #if 0 / #endif the if() block to unlock you temporarily. Though, this is not something I would push, a proper solution is needed, as indicated. :) (and this is what is to be available for the next release BTW). An alternative is to try something in vaapisink too, but this is more involved to validate because there are multiple combinations to consider and that also impact the X11 backend. One solution would be to use the cropped size to guess-estimate the window size. Though, this is also just a workaround because there are situations where vaapisink does not control the allocation (creation) of the window. So, we end up to need a generic solution in GstVaapiWindowWayland::render().</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>