win-mf: Add Windows Media Foundation Capture Device and Intel NPU AI features #10471

thyintel · 2024-04-02T21:29:24Z

Description

PR is linked with: obsproject/obs-deps#242 (Requires wil headers to build)
Windows 11 is also required for this PR to build and Windows 11 SDK (10.0.22000.0).

This is a draft implementation of Intel AI features using the NPU(=”Intel AI Boost”) on Intel Core Ultra(a.k.a Meteor Lake).
It enables Background Blur(Standard and Portrait), Background Removal, Auto Framing and Eye Contact correction over new Microsoft Effect Package and Media Foundation.
Because this capture device is based on Media Foundation, we created separate “Video Capture Device 2”. We are thinking that it’s better to integrate it into the existing DShow based Video Capture Device in order to not to make end-users confused.
Thus, we need help for (1) overall design guidance how we can integrate - how we can kick off MF based device instead of DShow base, (2) Any missing features to get merged? Because we focus on prototyping new AI features, wondering if we’re missing something on the MF device.
BTW, this feature only works on OEM integrated web-cam, external USB camera is planned to be supported for the future, but not yet supported as of March 2024, no ETA announced.

Screen shots:
GPU 99%, NPU 30% over 3D Mark, w/ AI features are enabled

New UI for AI – Background Blur, Removal, Auto Framing, Eye Contact by NPU(=Intel AI Boost)
they only appear on MTL, otherwise this section would be skipped.

Motivation and Context

Utilize Intel NPU for OBS and be able to add AI capabilities in OBS for Intel devices.

How Has This Been Tested?

This has been tested on:

MTL system containing the Intel NPU
ADL system without NPU

Types of changes

New feature (non-breaking change which adds functionality)

Checklist:

[x ] My code has been run through clang-format.
[x ] I have read the contributing document.
[x ] My code is not on the master branch.
[x ] The code has been tested.
[x ] All commit messages are properly formatted and commits squashed where appropriate.
[x ] I have included updates to all appropriate documentation.

RytoEX

Please use a more descriptive commit message.

In C++ for variables/functions/identifiers that remain in C++, we prefer camelCase over snake_case.

Is it possible to, at minimum, split this into two commits, or perhaps two PRs:

Add Media Foundation
Add the NPU features

plugins/win-mf/CMakeLists.txt

cmake/Modules/FindWIL.cmake

cmake/finders/FindWIL.cmake

plugins/win-mf/cmake/windows/obs-module.rc.in

plugins/win-mf/win-mf.cpp

plugins/win-mf/plugin-macros.h.in

plugins/win-mf/mf-plugin.cpp

RytoEX · 2024-04-24T21:00:13Z

plugins/win-mf/data/placeholder.png is only used for the DirectShow-based Virtual Camera. It doesn't seem to have a purpose here?

RytoEX · 2024-05-16T17:56:04Z

The deps updated with obsproject/obs-deps#242 was merged, so this is no longer a draft, but it will need to be rebased.

WizardCM · 2024-06-16T00:41:13Z

So I was able to get this building with current deps, however it does not work on Windows 10. This is due to usage of IMFCameraControlMonitor. I assume this is expected, but I'm noting it for posterity.

10:31:38.979: Module '../../obs-plugins/64bit/win-mf.dll' not loaded

WizardCM · 2024-06-16T01:13:17Z

I launched this PR on a Windows 11 Insider build, and got a crash when adding the source.

Snippets:

11:04:53.494: Video Capture Device 2 - MF: DecodeDeviceId failed
11:04:53.494: Video Capture Device 2 - MF: Video configuration failed
11:04:53.501: User added source 'Video Capture Device 2 - MF' (MediaFoundationsource_input) to scene 'Scene'

win-mf.dll!PhysicalCamera::GetBlur+0x55
win-mf.dll!PhysicalCamera::GetMepSetting+0x29
win-mf.dll!PhysicalCamera::SaveSettingsToDefault+0x11c
win-mf.dll!PhysicalCamera::Stop+0x2d
win-mf.dll!PhysicalCamera::Uninitialize+0x2d
win-mf.dll!PhysicalCamera::~PhysicalCamera+0x2e
win-mf.dll!PhysicalCamera::Release+0x22
win-mf.dll!MF_Create+0x4f
win-mf.dll!DeviceEnumerator::EnumerateCameraCallback+0xc2
win-mf.dll!MF_EnumerateCameras+0x93
win-mf.dll!DeviceEnumerator::Enumerate+0x7c
win-mf.dll!GetMediaFoundationSourceProperties+0xb2
obs.dll!obs_source_properties+0x8d
obs64.exe!OBSPropertiesView::ReloadProperties+0x81

Full logs (session and crash):

2024-06-16 11-04-39.txt

Crash 2024-06-16 11-04-54.txt

thyintel · 2024-06-28T21:38:01Z

I launched this PR on a Windows 11 Insider build, and got a crash when adding the source.

Snippets:

11:04:53.494: Video Capture Device 2 - MF: DecodeDeviceId failed
11:04:53.494: Video Capture Device 2 - MF: Video configuration failed
11:04:53.501: User added source 'Video Capture Device 2 - MF' (MediaFoundationsource_input) to scene 'Scene'

win-mf.dll!PhysicalCamera::GetBlur+0x55
win-mf.dll!PhysicalCamera::GetMepSetting+0x29
win-mf.dll!PhysicalCamera::SaveSettingsToDefault+0x11c
win-mf.dll!PhysicalCamera::Stop+0x2d
win-mf.dll!PhysicalCamera::Uninitialize+0x2d
win-mf.dll!PhysicalCamera::~PhysicalCamera+0x2e
win-mf.dll!PhysicalCamera::Release+0x22
win-mf.dll!MF_Create+0x4f
win-mf.dll!DeviceEnumerator::EnumerateCameraCallback+0xc2
win-mf.dll!MF_EnumerateCameras+0x93
win-mf.dll!DeviceEnumerator::Enumerate+0x7c
win-mf.dll!GetMediaFoundationSourceProperties+0xb2
obs.dll!obs_source_properties+0x8d
obs64.exe!OBSPropertiesView::ReloadProperties+0x81

Full logs (session and crash):

2024-06-16 11-04-39.txt

Crash 2024-06-16 11-04-54.txt

It looks like the Crash logs are from the Windows 10 build, are there any from your attempt at adding the source on Windows 11?

WizardCM · 2024-06-29T00:53:04Z

@thyintel the crash log is definitely from Windows 11, per the build number 26236 - not sure why it says 10. As I mentioned here, the MediaFoundation source is entirely hidden/disabled on on Windows 10 due to using Windows 11-only APIs.

RytoEX · 2024-07-10T21:04:54Z

This builds and runs on Windows 11 23H2 with the Windows 11 SDK (10.0.22621.0). The "Video Capture Device 2" is available and correctly loads my webcam. However, in Debug configuration, it spams the log with the following:

log spam

source 'Video Capture Device 2' (MediaFoundationsource_input) created
Video Capture Device 2: DecodeDeviceId failed
Video Capture Device 2: Video configuration failed
User added source 'Video Capture Device 2' (MediaFoundationsource_input) to scene 'Scene'
C:\dev\obsproject\obs-studio\plugins\win-mf\libmfcapture\source\PhysicalCamera.cpp(1363)\win-mf.dll!00007FFA13A03EB7: (caller: 00007FFA13A04389) ReturnHr(3003) tid(4df8) 80070490 Element not found.
    [PhysicalCamera::GetMepSetting(GetBlur(blur, shallowfocus, mask))]
C:\dev\obsproject\obs-studio\plugins\win-mf\libmfcapture\source\PhysicalCamera.cpp(1401)\win-mf.dll!00007FFA13A043E9: (caller: 00007FFA13A06055) ReturnHr(3004) tid(4df8) 80070490 Element not found.
    [PhysicalCamera::SaveSettingsToDefault(GetMepSetting(setting))]
C:\dev\obsproject\obs-studio\plugins\win-mf\libmfcapture\source\PhysicalCamera.cpp(1363)\win-mf.dll!00007FFA13A03EB7: (caller: 00007FFA13A04389) ReturnHr(3005) tid(3978) 80070490 Element not found.
    [PhysicalCamera::GetMepSetting(GetBlur(blur, shallowfocus, mask))]
C:\dev\obsproject\obs-studio\plugins\win-mf\libmfcapture\source\PhysicalCamera.cpp(1401)\win-mf.dll!00007FFA13A043E9: (caller: 00007FFA13A06055) ReturnHr(3006) tid(3978) 80070490 Element not found.
    [PhysicalCamera::SaveSettingsToDefault(GetMepSetting(setting))]
C:\dev\obsproject\obs-studio\plugins\win-mf\libmfcapture\source\PhysicalCamera.cpp(393)\win-mf.dll!00007FFA13A04567: (caller: 00007FFA13A04CDB) ReturnHr(3007) tid(5490) C00D36E6 The requested attribute was not found.    [PhysicalCamera::FillSegMask(pSample->GetUnknown(MFSampleExtension_CaptureMetadata, IID_PPV_ARGS(&spMetadataAttri)))]
C:\dev\obsproject\obs-studio\plugins\win-mf\libmfcapture\source\PhysicalCamera.cpp(393)\win-mf.dll!00007FFA13A04567: (caller: 00007FFA13A04CDB) ReturnHr(3008) tid(3fcc) C00D36E6 The requested attribute was not found.    [PhysicalCamera::FillSegMask(pSample->GetUnknown(MFSampleExtension_CaptureMetadata, IID_PPV_ARGS(&spMetadataAttri)))]
C:\dev\obsproject\obs-studio\plugins\win-mf\libmfcapture\source\PhysicalCamera.cpp(397)\win-mf.dll!00007FFA13A0462E: (caller: 00007FFA13A04CDB) ReturnHr(3009) tid(5490) C00D36E6 The requested attribute was not found.    [PhysicalCamera::FillSegMask(spMetadataAttri->GetBlobSize( MF_CAPTURE_METADATA_FRAME_BACKGROUND_MASK, &cbBlobSize))]
C:\dev\obsproject\obs-studio\plugins\win-mf\libmfcapture\source\PhysicalCamera.cpp(397)\win-mf.dll!00007FFA13A0462E: (caller: 00007FFA13A04CDB) ReturnHr(3010) tid(3fcc) C00D36E6 The requested attribute was not found.    [PhysicalCamera::FillSegMask(spMetadataAttri->GetBlobSize( MF_CAPTURE_METADATA_FRAME_BACKGROUND_MASK, &cbBlobSize))]
C:\dev\obsproject\obs-studio\plugins\win-mf\libmfcapture\source\PhysicalCamera.cpp(397)\win-mf.dll!00007FFA13A0462E: (caller: 00007FFA13A04CDB) ReturnHr(3011) tid(5490) C00D36E6 The requested attribute was not found.    [PhysicalCamera::FillSegMask(spMetadataAttri->GetBlobSize( MF_CAPTURE_METADATA_FRAME_BACKGROUND_MASK, &cbBlobSize))]
C:\dev\obsproject\obs-studio\plugins\win-mf\libmfcapture\source\PhysicalCamera.cpp(397)\win-mf.dll!00007FFA13A0462E: (caller: 00007FFA13A04CDB) ReturnHr(3012) tid(5994) C00D36E6 The requested attribute was not found.    [PhysicalCamera::FillSegMask(spMetadataAttri->GetBlobSize( MF_CAPTURE_METADATA_FRAME_BACKGROUND_MASK, &cbBlobSize))]
C:\dev\obsproject\obs-studio\plugins\win-mf\libmfcapture\source\PhysicalCamera.cpp(397)\win-mf.dll!00007FFA13A0462E: (caller: 00007FFA13A04CDB) ReturnHr(3013) tid(5490) C00D36E6 The requested attribute was not found.    [PhysicalCamera::FillSegMask(spMetadataAttri->GetBlobSize( MF_CAPTURE_METADATA_FRAME_BACKGROUND_MASK, &cbBlobSize))]
C:\dev\obsproject\obs-studio\plugins\win-mf\libmfcapture\source\PhysicalCamera.cpp(397)\win-mf.dll!00007FFA13A0462E: (caller: 00007FFA13A04CDB) ReturnHr(3014) tid(5994) C00D36E6 The requested attribute was not found.    [PhysicalCamera::FillSegMask(spMetadataAttri->GetBlobSize( MF_CAPTURE_METADATA_FRAME_BACKGROUND_MASK, &cbBlobSize))]

Given the log spam, I wonder if something is not appropriately gated.

Appropriately, since the hardware I'm testing on at the moment does not have an NPU, I do not see the NPU features (background removal, eye gaze correction, etc.). I will re-check on capable hardware at a later time.

plugins/win-mf/mf-plugin.cpp

WizardCM · 2024-07-31T14:07:44Z

The current implementation of this PR will also need to bump the minimum Windows SDK version to 22621 due to the usage of IMFCameraControlNotify.

obs-studio/cmake/windows/compilerconfig.cmake

Lines 45 to 47 in 8b975c4

    
           if(CMAKE_VS_WINDOWS_TARGET_PLATFORM_VERSION VERSION_LESS 10.0.20348) 
        
             message(FATAL_ERROR "OBS requires Windows SDK version 10.0.20348.0 or more recent.\n" 
        
                                 "Please download and install the most recent Windows SDK.")

WizardCM · 2024-07-31T14:17:18Z

Ran the build on a debugger on Windows and confirmed the crash was not due to building on Windows:

RytoEX

It looks like this PR has some files generated using an older version of obs-plugintemplate. Those files should be replaced using a newer version of the obs-plugintemplate.

New code files should have appropriate license headers (GPLv2+).

cmake/Modules/FindWIL.cmake

plugins/win-mf/CMakeLists.txt

plugins/win-mf/cmake/legacy.cmake

plugins/win-mf/data/locale/en-US.ini

plugins/win-mf/plugin-macros.generated.h

plugins/win-mf/plugin-macros.h.in

plugins/win-mf/CMakeLists.txt

cmake/finders/FindWIL.cmake

plugins/win-mf/data/locale/en-US.ini

plugins/win-mf/libmfcapture/mfcapture.hpp

plugins/win-mf/libmfcapture/source/DeviceControlChangeListener.cpp

plugins/win-mf/libmfcapture/mfcapture.hpp

plugins/win-mf/libmfcapture/source/DeviceControlChangeListener.hpp

plugins/win-mf/libmfcapture/source/PhysicalCamera.hpp

RytoEX · 2025-03-04T21:46:02Z

plugins/CMakeLists.txt

@@ -87,4 +87,5 @@ add_obs_plugin(text-freetype2)
 add_obs_plugin(vlc-video WITH_MESSAGE)
 add_obs_plugin(win-capture PLATFORMS WINDOWS)
 add_obs_plugin(win-dshow PLATFORMS WINDOWS)
+add_obs_plugin(win-mf PLATFORMS WINDOWS)


Todo for OBS: are we satisfied using win-mf for the plugin name?

I'd prefer if the name were spelt-out - the abbreviation is ambiguous from the outside and doesn't provide any good hint at what's inside the can.

win-mediafoundation would be acceptable, personally I don't like the platform prefixes and rather let the technology speak for itself (i.e., a plugin called "obs-mediafoundation" contains support for "Media Foundation", which just happens to be only available on Windows).

Incidentally, we used to have a module named win-mf that provided Media Foundation encoders on Windows, so it might not be a good idea to use the same name for a capture plugin.

RytoEX · 2025-03-04T22:41:37Z

plugins/win-mf/libmfcapture/source/mfcapture.rc

+VS_VERSION_INFO VERSIONINFO
+ FILEVERSION 30,0,1,0
+BEGIN
+    BLOCK "StringFileInfo"
+    BEGIN
+	BLOCK "040904B0"
+	BEGIN
+	    VALUE "CompanyName", "Intel Corporation"
+	    VALUE "FileDescription", "OBS Video Capture module"
+	    VALUE "FileVersion", "30.0.1"
+	    VALUE "ProductName", "OBS Studio"
+	    VALUE "ProductVersion", "30.0.1"
+	    VALUE "LegalCopyright", "Copyright (C) 2023, Intel Corporation"
+	    VALUE "InternalName", "win-mf"
+	    VALUE "OriginalFilename", "win-mf"
+	END
+    END
+    BLOCK "VarFileInfo"
+    BEGIN
+	VALUE "Translation", 0x409,1200
+    END
+END


Rather than hard-coding this, we tend to use an .rc.in file and have CMake process that into an .rc file, with few exceptions. @PatTheMav ?

I'm not sure if the rest of the file contents here are used.

Correct, almost all values are defined by CMake project definition, so the file should be generated by CMake as well. Particularly version numbers will be fully dynamic.

RytoEX · 2025-03-04T22:44:15Z

plugins/win-mf/libmfcapture/source/resource.hpp

@@ -0,0 +1,23 @@
+// {{NO_DEPENDENCIES}}


Similar to the .rc file, I'm not sure what these are used for.

RytoEX · 2025-03-04T22:45:23Z

plugins/win-mf/mf-plugin.cpp

@@ -0,0 +1,20 @@
+/* mf-plugin.cpp */


Please add an appropriate license header with copyright info.

plugins/win-mf/libmfcapture/source/PhysicalCamera.cpp

RytoEX · 2025-03-04T22:56:02Z

plugins/win-mf/libmfcapture/source/PhysicalCamera.cpp

+class VideoBufferLock {
+
+public:
+	VideoBufferLock(IMFMediaBuffer *pBuffer)
+	{
+		m_spBuffer = pBuffer;
+		m_spBuffer->QueryInterface(IID_PPV_ARGS(&m_sp2DBuffer));
+	}
+
+	~VideoBufferLock()
+	{
+		UnlockBuffer();
+		m_spBuffer = nullptr;
+		m_sp2DBuffer = nullptr;
+	}
+
+	HRESULT LockBuffer(LONG lDefaultStride, DWORD dwHeightInPixels, BYTE **ppbScanLine0, LONG *plStride)
+	{
+		HRESULT hr = S_OK;
+		if (m_sp2DBuffer) {
+			hr = m_sp2DBuffer->Lock2D(ppbScanLine0, plStride);
+		} else {
+			BYTE *pData = NULL;
+			hr = m_spBuffer->Lock(&pData, NULL, NULL);
+			if (SUCCEEDED(hr)) {
+				*plStride = lDefaultStride;
+				if (lDefaultStride < 0) {
+					*ppbScanLine0 = pData + abs(lDefaultStride) * (dwHeightInPixels - 1);
+				} else {
+					*ppbScanLine0 = pData;
+				}
+			}
+		}
+
+		m_bLocked = (SUCCEEDED(hr));
+		return hr;
+	}
+
+	void UnlockBuffer()
+	{
+		if (m_bLocked) {
+			if (m_sp2DBuffer) {
+				m_sp2DBuffer->Unlock2D();
+			} else {
+				m_spBuffer->Unlock();
+			}
+			m_bLocked = FALSE;
+		}
+	}
+
+private:
+	wil::com_ptr_nothrow<IMFMediaBuffer> m_spBuffer;
+	wil::com_ptr_nothrow<IMF2DBuffer> m_sp2DBuffer;
+
+	BOOL m_bLocked = FALSE;
+};


Wondering if we should define this in a separate file. @PatTheMav ?

Yes, any class definition should get its own separate source file.

I have moved the code into a separate file, but should it also have a header file?

plugins/win-mf/libmfcapture/source/PhysicalCamera.hpp

RytoEX

For new files, use appropriate license headers (GPLv2+).

plugins/win-mf/libmfcapture/source/framework.hpp

plugins/win-mf/libmfcapture/source/PhysicalCamera.cpp

plugins/win-mf/win-mf.cpp

RytoEX

Newly added files should have appropriate and compatible license headers (GPLv2+).

RytoEX · 2025-04-23T19:10:47Z

plugins/win-mf/libmfcapture/source/CriticalSection.cpp

@@ -0,0 +1,21 @@
+class CriticalSection {


Please add appropriate license headers (GPLv2+).

RytoEX · 2025-04-23T19:11:42Z

plugins/win-mf/libmfcapture/source/VideoBufferLock.cpp

@@ -0,0 +1,58 @@
+#include <mfidl.h>


Please add appropriate license headers (GPLv2+).

RytoEX · 2025-04-29T17:56:10Z

plugins/win-mf/CMakeLists.txt

+    libmfcapture/source/DeviceControlChangeListener.cpp
+    libmfcapture/source/mfcapture.cpp
+    libmfcapture/source/PhysicalCamera.cpp
+    libmfcapture/source/VideoBufferLock.cpp
+    libmfcapture/source/CriticalSection.cpp


Alphabetize these.

RytoEX · 2025-04-29T18:19:25Z

plugins/win-mf/win-mf.cpp

+	bool _deactivateWhenNotShowing = false;
+	bool _flip = false;
+	bool _active = false;
+	bool _autorotation = true;
+	bool _firstframe = true;


Avoid prefixing variables with _. While technically permitted by the spec in these cases, it's better to avoid altogether.

RytoEX · 2025-04-29T18:23:05Z

plugins/win-mf/win-mf.cpp

+
+	void MediaFoundationSourceLoop();
+
+	void static __stdcall _OnVideoData(void *pData, int Size, long long llTimestamp, void *pUserData);


The C++ standard reserves identifiers that begin with an underscore and a capital letter.

RytoEX · 2025-04-29T18:24:44Z

plugins/win-mf/win-mf.cpp

+static DWORD CALLBACK MediaFoundationSourceThread(LPVOID ptr)
+{
+	MediaFoundationSourceInput *input = (MediaFoundationSourceInput *)ptr;
+	os_set_thread_name("win-MediaFoundation: MediaFoundationSourceThread");


Suggested change

os_set_thread_name("win-MediaFoundation: MediaFoundationSourceThread");

os_set_thread_name("win-mediafoundation: MediaFoundationSourceThread");

RytoEX · 2025-04-29T18:29:14Z

plugins/win-mf/win-mf.cpp

+		if (!properties.empty()) {
+		}


What's the intent of this block?

RytoEX · 2025-04-29T18:31:00Z

plugins/win-mf/win-mf.cpp

+
+inline bool MediaFoundationSourceInput::Activate(obs_data_t *settings)
+{
+


Remove unnecessary blank line.

RytoEX · 2025-04-29T18:47:48Z

plugins/win-mf/libmfcapture/source/VideoBufferLock.cpp

+		m_spBuffer = nullptr;
+		m_sp2DBuffer = nullptr;


Do these need to be manually set to nullptr in the destructor? I thought wil::com_ptr_nothrow and wil::com_ptr were smart pointers that should clean up after themselves.

RytoEX · 2025-04-30T18:40:54Z

plugins/win-mf/cmake/windows/obs-module.rc.in

+      VALUE "ProductName", "${OBS_PRODUCT_NAME}"
+      VALUE "ProductVersion", "${OBS_VERSION_CANONICAL}"
+      VALUE "Comments", "${OBS_COMMENTS}"
+      VALUE "LegalCopyright", "${OBS_LEGAL_COPYRIGHT}"


You may need to hardcode this line to use a specific copyright attribution.

thyintel marked this pull request as draft April 2, 2024 21:29

WizardCM added the New Feature New feature or plugin label Apr 2, 2024

RytoEX self-assigned this Apr 3, 2024

thyintel force-pushed the obs_intel_ai branch from 4b745e5 to 165b26a Compare April 5, 2024 18:56

thyintel mentioned this pull request Apr 5, 2024

deps.windows: Add WIL headers obsproject/obs-deps#242

Merged

thyintel force-pushed the obs_intel_ai branch 3 times, most recently from fc46b24 to 0584cda Compare April 5, 2024 20:49

RytoEX requested changes Apr 9, 2024

View reviewed changes

thyintel changed the title ~~win-mf: Add win-mf project~~ win-mf: Add Windows Media Foundation Capture Device and Intel NPU AI features Apr 15, 2024

thyintel force-pushed the obs_intel_ai branch 6 times, most recently from c8280fd to dcea1bb Compare April 23, 2024 03:06

thyintel force-pushed the obs_intel_ai branch from dcea1bb to d72b83c Compare May 7, 2024 22:23

RytoEX marked this pull request as ready for review May 16, 2024 17:55

thyintel force-pushed the obs_intel_ai branch from d72b83c to 4085cf5 Compare May 17, 2024 00:09

thyintel force-pushed the obs_intel_ai branch from 4085cf5 to 411f873 Compare May 28, 2024 22:02

tytan652 reviewed Jul 31, 2024

View reviewed changes

plugins/win-mf/mf-plugin.cpp Outdated Show resolved Hide resolved

thyintel force-pushed the obs_intel_ai branch from 677be88 to 2b117ff Compare September 13, 2024 18:59

RytoEX added the Seeking Testers Build artifacts on CI label Sep 13, 2024

RytoEX mentioned this pull request Sep 13, 2024

CI: Use Windows 11 SDK 10.0.22621.0 #11283

Merged

6 tasks

thyintel force-pushed the obs_intel_ai branch 2 times, most recently from 6598aae to eca2e43 Compare December 5, 2024 21:06

RytoEX requested changes Jan 8, 2025

View reviewed changes

thyintel force-pushed the obs_intel_ai branch 2 times, most recently from 2c6ef1a to bbe146a Compare February 4, 2025 20:39

RytoEX requested changes Mar 4, 2025

View reviewed changes

thyintel force-pushed the obs_intel_ai branch from bbe146a to b23625b Compare March 7, 2025 22:52

RytoEX requested changes Mar 8, 2025

View reviewed changes

derrod mentioned this pull request Mar 25, 2025

win-mf: Reintroduce win-mf plugin for Media Foundation-based encoding on WoA #11993

Open

6 tasks

thyintel force-pushed the obs_intel_ai branch 3 times, most recently from d1d4308 to c014990 Compare March 26, 2025 19:29

thyintel force-pushed the obs_intel_ai branch 5 times, most recently from 9ff3014 to d9c667d Compare April 2, 2025 21:10

thyintel force-pushed the obs_intel_ai branch 4 times, most recently from 3b22ef5 to e925aa4 Compare April 17, 2025 15:27

thyintel added 2 commits April 17, 2025 08:30

win-mf: Add Windows Media Foundation Capture Device

1233cdb

win-mf: Add Intel NPU AI Features

7513dec

thyintel force-pushed the obs_intel_ai branch from e925aa4 to 7513dec Compare April 17, 2025 15:30

RytoEX requested changes Apr 23, 2025

View reviewed changes

RytoEX requested changes Apr 30, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

win-mf: Add Windows Media Foundation Capture Device and Intel NPU AI features #10471

win-mf: Add Windows Media Foundation Capture Device and Intel NPU AI features #10471

thyintel commented Apr 2, 2024 •

edited

Loading

RytoEX left a comment

RytoEX commented Apr 24, 2024

RytoEX commented May 16, 2024 •

edited

Loading

WizardCM commented Jun 16, 2024

WizardCM commented Jun 16, 2024

thyintel commented Jun 28, 2024

WizardCM commented Jun 29, 2024

RytoEX commented Jul 10, 2024

WizardCM commented Jul 31, 2024

WizardCM commented Jul 31, 2024

RytoEX left a comment

RytoEX Mar 4, 2025

PatTheMav Mar 5, 2025 •

edited

Loading

RytoEX Mar 5, 2025 •

edited

Loading

RytoEX Mar 4, 2025

PatTheMav Mar 5, 2025

RytoEX Mar 4, 2025

RytoEX Mar 4, 2025

RytoEX Mar 4, 2025

PatTheMav Mar 5, 2025

thyintel Apr 17, 2025

RytoEX left a comment

RytoEX left a comment

RytoEX Apr 23, 2025

RytoEX Apr 23, 2025

RytoEX Apr 29, 2025

RytoEX Apr 29, 2025

RytoEX Apr 29, 2025

RytoEX Apr 29, 2025

RytoEX Apr 29, 2025

RytoEX Apr 29, 2025

RytoEX Apr 29, 2025

RytoEX Apr 30, 2025


		void MediaFoundationSourceLoop();

		void static __stdcall _OnVideoData(void pData, int Size, long long llTimestamp, void pUserData);

	os_set_thread_name("win-MediaFoundation: MediaFoundationSourceThread");
	os_set_thread_name("win-mediafoundation: MediaFoundationSourceThread");


		inline bool MediaFoundationSourceInput::Activate(obs_data_t *settings)
		{

win-mf: Add Windows Media Foundation Capture Device and Intel NPU AI features #10471

Are you sure you want to change the base?

win-mf: Add Windows Media Foundation Capture Device and Intel NPU AI features #10471

Conversation

thyintel commented Apr 2, 2024 • edited Loading

Description

Motivation and Context

How Has This Been Tested?

Types of changes

Checklist:

RytoEX left a comment

Choose a reason for hiding this comment

RytoEX commented Apr 24, 2024

RytoEX commented May 16, 2024 • edited Loading

WizardCM commented Jun 16, 2024

WizardCM commented Jun 16, 2024

thyintel commented Jun 28, 2024

WizardCM commented Jun 29, 2024

RytoEX commented Jul 10, 2024

WizardCM commented Jul 31, 2024

WizardCM commented Jul 31, 2024

RytoEX left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

PatTheMav Mar 5, 2025 • edited Loading

Choose a reason for hiding this comment

RytoEX Mar 5, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

RytoEX left a comment

Choose a reason for hiding this comment

RytoEX left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

thyintel commented Apr 2, 2024 •

edited

Loading

RytoEX commented May 16, 2024 •

edited

Loading

PatTheMav Mar 5, 2025 •

edited

Loading

RytoEX Mar 5, 2025 •

edited

Loading