On Thu, 4 May 2017 11:15:42 +0200 Hendrik Leppkes <[email protected]> wrote:
> On Thu, May 4, 2017 at 8:44 AM, wm4 <[email protected]> wrote: > > I want to make it non-mandatory to set a mutex in the D3D11 device > > context, and replacing it with user callbacks seems like the best > > solution. This is preparation for it. Also makes the code slightly more > > readable. > > > > With recent frame-mt hwaccel changes, a user that needs this locking > could just do it externally around the decode function. Maybe we > should just get rid of it in the "new" d3d11 hwaccel? Yeah, I'm not sure how this should be handled, or if this sort of locking is even required. Note that for sane refcounting and hwframes functionality in a multithreaded setting there would need to be a locking mechanism in the hwcontext - but only if this kind of locking is needed at all. It's not clear to me whether it's needed. It could be cargo-cult. _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
