4 commits

Author	SHA1	Message	Date
Seungha Yang	824b0ce0f4	Revert "d3d11: Enable native multi-thread protection layer and make use of it" ... This reverts commit 872b7f503c. Native multi-thread protection layer seems to be consuming more CPU resource than application side protection approach in some cases Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/merge_requests/2095>	2021-03-20 17:53:58 +09:00
Seungha Yang	872b7f503c	d3d11: Enable native multi-thread protection layer and make use of it ... ... instead of our own GRecMutex locking. In this way, any other Direct3D11 client (MediaFoundation for example) can safely call any Direct3D11 API even when we are sharing our Direct3D11 device with others. Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/merge_requests/2092>	2021-03-18 16:37:37 +00:00
Seungha Yang	615f52f2f7	d3d11device: Hold ID3D11VideoDevice and ID3D11VideoContext object ... ... instead of QueryInterface-ing per elements. Note that ID3D11VideoDevice and ID3D11VideoContext objects might not be available if device doesn't support video interface. So GstD3D11Device object will create those objects only when requested. Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/merge_requests/2079>	2021-03-14 14:44:55 +09:00
Seungha Yang	5b3e316039	d3d11: Port to C++ ... Direct3D11 objects are COM, and most COM C APIs are verbose (C++ is a little better). So, by using C++ APIs, we can make code shorter and more readable. Moreover, "ComPtr" helper class (which is C++ only) can be utilized, that is very helpful for avoiding error-prone COM refcounting issue/leak. Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/merge_requests/2077>	2021-03-14 13:05:22 +09:00

Renamed from sys/d3d11/gstd3d11videoprocessor.c (Browse further)