On Sat, Nov 19, 2011 at 3:01 AM, Christophe Thommeret <[email protected]> wrote: > Le vendredi 18 novembre 2011 22:20:05, Christophe Thommeret a écrit : >> Hi Dan, >> >> I've looked at mlt's vdpau and i see the problem. A vdp decoder maintains a >> bunch of internal variables that are not exposed to the user through >> videosurfaces, so if you can't destroy and recreate without issues. >> I've fixed this by removing the global g_vdpau and adding vdpDevice and >> vdpDecoder to producer_avformat.vdpau struct. Transitions look good now. Do >> you have any other reproducible bug in mind ?
You might want to do some testing with real_time=2 or =3 (Processing threads setting in Kdenlive) if you have multiple cores. Other than that, I have no specific bugs to address. Do you know much about VA-API and how to fetched the decoded images from video memory using it? > Patch attached. > Seems stable here on vdpau feature set C gpu (Which are probably the most > exposed to the problem.) Thank you! Would you please try to update your patch against trunk? There was one small change in vdpau.c Nov 3 that broke a big hunk of the patch on vdpau.c. -- +-DRD-+ ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Mlt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mlt-devel
