| What | Removed | Added |
|---|---|---|
| Resolution | --- | NOTOURBUG |
| Status | NEW | RESOLVED |
Comment # 1
on bug 105145
from Christian König
Yeah, that is a design issue with vlVaExportSurfaceHandle. E.g. vlVaExportSurfaceHandle can only export surfaces when they are in the progressive memory layout because VA-API doesn't supports interlaced layouts. To not run into issues with that limitation we reallocate the backing store for the surface and copy from the interlaced presentation to the progressive layout on the first vlVaExportSurfaceHandle. Now post processing is only possible if you got the interlaced format, cause otherwise extracting the odd/even fields costs to much time. What we could try to do is to reverse what is done in vlVaExportSurfaceHandle before post processing, e.g. copy from progressive to interlaced. But that usually means we lag for quite a number of frames (because of the extra copy) until all surfaces are in interlaced format again. Not sure what to do here except for fixing VA-API.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
