On 06.11.2013 15:08, Christian König wrote:
We need to take/release the driver lock around this as well.
I've fixed this and pushed the result upstream. Any idea when your
deinterlacer is ready to hit the list as a patch?
Thanks for fixing this up.
The simple temporal deinterlacer should be almost good to go, I think.
It's not perfect (no deinterlacer is), but usually much better than bob.
In some cases motion is misdetected and combing remains; but I have not
seen any motion adaptive deinterlacer without such issues so far.
I would love to still see the deinterlacer in Mesa 10.0, but I don't
know if this is a realistic goal.
Best regards
Grigori
Thanks for the help,
Christian.
Am 06.11.2013 00:35, schrieb Grigori Goronzy:
Otherwise OutputSurface interop has funny results sometimes.
This fixes interop with the mpv media player.
---
src/gallium/state_trackers/vdpau/output.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/gallium/state_trackers/vdpau/output.c
b/src/gallium/state_trackers/vdpau/output.c
index def01c8..76c7312 100644
--- a/src/gallium/state_trackers/vdpau/output.c
+++ b/src/gallium/state_trackers/vdpau/output.c
@@ -734,5 +734,6 @@ struct pipe_resource
*vlVdpOutputSurfaceGallium(VdpOutputSurface surface)
if (!vlsurface || !vlsurface->surface)
return NULL;
+ vlVdpResolveDelayedRendering(vlsurface->device, NULL, NULL);
return vlsurface->surface->texture;
}
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
