jp9000
/
obs-studio
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
obs-studio/plugins/win-dshow/CMakeLists.txt

151 lines
5.0 KiB
CMake
Raw Normal View History

win-dshow: Disable plugin and warn if submodule not found
2016-09-20 05:07:30 -07:00
if(NOT EXISTS "${CMAKE_CURRENT_SOURCE_DIR}/libdshowcapture/dshowcapture.hpp")
message(STATUS "libdshowcapture submodule not found! Please fetch submodules. win-dshow plugin disabled.")
return()
endif()
Add preliminary DirectShow capture plugin This covers the basics of devices. Mostly functional but not at 100% yet. Uses 'libdshowcapture' library to capture directshow video/audio. Both libdshowcapture and the plugin still need some work. Should at least capture basic webcams and capture cards for the time being.
2014-05-30 03:29:48 -07:00
project(win-dshow)
cmake: Rename FindFFMpeg to FindFFmpeg This was sort of driving me crazy: The 'm' in FFmpeg isn't supposed to be capitalized.
2015-07-18 16:15:01 -07:00
find_package(FFmpeg REQUIRED COMPONENTS avcodec avutil)
cmake: Replace FFMpeg modules with single module Now using components instead of one find_package call per module
2014-09-23 06:26:08 -07:00
include_directories(${FFMPEG_INCLUDE_DIRS})
win-dshow: Add FFmpeg decoding support
2014-09-12 19:51:45 -07:00
set(win-dshow_HEADERS
win-dshow: Put device id mangling in separate file This is going to be used for other code as well, so may as well put it in its own file.
2014-12-18 15:33:35 -08:00
encode-dstr.hpp
win-dshow: Add FFmpeg decoding support
2014-09-12 19:51:45 -07:00
ffmpeg-decode.h)
CMake: Build Windows modules with file descriptors
2019-06-16 04:42:58 -07:00
set(MODULE_DESCRIPTION "OBS DirectShow module")
win-dshow: Use cmake-based GUID for virtualcam
2020-09-06 17:04:06 -07:00
set(VIRTUALCAM_GUID "" CACHE STRING "VirtualCam GUID")
set(VIRTUALCAM_ENABLED FALSE)
if(VIRTUALCAM_GUID STREQUAL "")
message(STATUS "VirtualCam GUID not set! VirtualCam disabled.")
else()
set(INVALID_GUID TRUE)
string(REPLACE "-" ";" GUID_VALS ${VIRTUALCAM_GUID})
list(LENGTH GUID_VALS GUID_VAL_COUNT)
if(GUID_VAL_COUNT EQUAL 5)
string(REPLACE ";" "0" GUID_HEX ${GUID_VALS})
string(REGEX MATCH "[0-9a-fA-F]+" GUID_ACTUAL_HEX ${GUID_HEX})
if(GUID_ACTUAL_HEX STREQUAL GUID_HEX)
list(GET GUID_VALS 0 GUID_VALS_DATA1)
list(GET GUID_VALS 1 GUID_VALS_DATA2)
list(GET GUID_VALS 2 GUID_VALS_DATA3)
list(GET GUID_VALS 3 GUID_VALS_DATA4)
list(GET GUID_VALS 4 GUID_VALS_DATA5)
string(LENGTH ${GUID_VALS_DATA1} GUID_VALS_DATA1_LENGTH)
string(LENGTH ${GUID_VALS_DATA2} GUID_VALS_DATA2_LENGTH)
string(LENGTH ${GUID_VALS_DATA3} GUID_VALS_DATA3_LENGTH)
string(LENGTH ${GUID_VALS_DATA4} GUID_VALS_DATA4_LENGTH)
string(LENGTH ${GUID_VALS_DATA5} GUID_VALS_DATA5_LENGTH)
if(GUID_VALS_DATA1_LENGTH EQUAL 8 AND
GUID_VALS_DATA2_LENGTH EQUAL 4 AND
GUID_VALS_DATA3_LENGTH EQUAL 4 AND
GUID_VALS_DATA4_LENGTH EQUAL 4 AND
GUID_VALS_DATA5_LENGTH EQUAL 12)
set(GUID_VAL01 ${GUID_VALS_DATA1})
set(GUID_VAL02 ${GUID_VALS_DATA2})
set(GUID_VAL03 ${GUID_VALS_DATA3})
string(SUBSTRING ${GUID_VALS_DATA4} 0 2 GUID_VAL04)
string(SUBSTRING ${GUID_VALS_DATA4} 2 2 GUID_VAL05)
string(SUBSTRING ${GUID_VALS_DATA5} 0 2 GUID_VAL06)
string(SUBSTRING ${GUID_VALS_DATA5} 2 2 GUID_VAL07)
string(SUBSTRING ${GUID_VALS_DATA5} 4 2 GUID_VAL08)
string(SUBSTRING ${GUID_VALS_DATA5} 6 2 GUID_VAL09)
string(SUBSTRING ${GUID_VALS_DATA5} 8 2 GUID_VAL10)
string(SUBSTRING ${GUID_VALS_DATA5} 10 2 GUID_VAL11)
set(VIRTUALCAM_ENABLED TRUE)
set(INVALID_GUID FALSE)
endif()
endif()
endif()
endif()
if(INVALID_GUID)
message(WARNING "Invalid VirtualCam GUID! VirtualCam disabled.")
endif()
if(VIRTUALCAM_ENABLED)
add_definitions(-DVIRTUALCAM_ENABLED)
endif()
CMake: Build Windows modules with file descriptors
2019-06-16 04:42:58 -07:00
configure_file(${CMAKE_SOURCE_DIR}/cmake/winrc/obs-module.rc.in win-dshow.rc)
win-dshow: Use cmake-based GUID for virtualcam
2020-09-06 17:04:06 -07:00
configure_file(${CMAKE_CURRENT_SOURCE_DIR}/virtualcam-guid.h.in ${CMAKE_CURRENT_BINARY_DIR}/virtualcam-guid.h)
include_directories(${CMAKE_CURRENT_BINARY_DIR})
Add preliminary DirectShow capture plugin This covers the basics of devices. Mostly functional but not at 100% yet. Uses 'libdshowcapture' library to capture directshow video/audio. Both libdshowcapture and the plugin still need some work. Should at least capture basic webcams and capture cards for the time being.
2014-05-30 03:29:48 -07:00
set(win-dshow_SOURCES
win-dshow: Add FFmpeg decoding support
2014-09-12 19:51:45 -07:00
win-dshow.cpp
win-dshow: Add C985/C353 hardware h264 encoders This adds support for the AverMedia C985 encoder (which is available on C985 capture cards) as well as the C353 hardware encoder (which is currently available on the X99S Gaming 9 motherboards). These encoders have some limitations, such as limited resolutions (1280x720 and 1024x768), a max GOP size of 30, and the encoder format only supports YV12, which requires conversion if the current output format isn't the same. The C985 and C353 encoders seem to be pretty much identical, although it seems like the C353 has a bit more efficient encoding. I don't believe these are really suitable for streaming, as they do not really have the encoding efficiency needed to stream at lower bitrates, and seem to only support variable bitrate. However, for recording these encoders are quite nice to have available, and work quite well.
2014-12-19 12:31:23 -08:00
win-dshow-encoder.cpp
win-dshow: Move module loading to separate file The main module code was originally all packed in to the win-dshow.cpp file, which isn't exactly ideal or clean if one wants to add other things to the module as a whole.
2014-12-19 07:53:15 -08:00
dshow-plugin.cpp
CMake: Build Windows modules with file descriptors
2019-06-16 04:42:58 -07:00
ffmpeg-decode.c
win-dshow.rc)
Add preliminary DirectShow capture plugin This covers the basics of devices. Mostly functional but not at 100% yet. Uses 'libdshowcapture' library to capture directshow video/audio. Both libdshowcapture and the plugin still need some work. Should at least capture basic webcams and capture cards for the time being.
2014-05-30 03:29:48 -07:00
win-dshow: Use cmake-based GUID for virtualcam
2020-09-06 17:04:06 -07:00
if(VIRTUALCAM_ENABLED)
set(virtualcam-output_SOURCES
tiny-nv12-scale.c
shared-memory-queue.c
virtualcam.c)
set(virtualcam-output_HEADERS
tiny-nv12-scale.h
shared-memory-queue.h)
endif()
win-dshow: Add Virtual Camera (Windows) The virtual camera adds the ability to use the output of OBS itself as a camera that can be selected within other Windows applications. This is very loosely based upon the catxfish virtual camera plugin design. There is a shared memory queue, but instead of having 10-20 frames in the queue, there are now only 3 frames in the queue to minimize latency and reduce memory usage. The third frame is mostly to ensure that writing does not occur on the same frame being read; the delay is merely one frame at all times. The frames of the shared memory queue are NV12 instead of YUYV, which reduces the memory and data copied, as well as eliminate unnecessary conversion from NV12. Some programs (such as chrome, which uses webrtc to capture) do not support NV12 however, so an I420 conversion is provided, which is far less expensive than YUYV. The CPU cost of NV12 -> I420 is negligible in comparison. The virtual camera filter itself is based upon the output filter within the libdshowcapture library, which was originally implemented for other purposes. This is more ideal than the Microsoft example code because for one, it's far less convoluted, two, allows us to be able to customize the filter to our needs a bit more easily, and three, has much better RAII. The Microsoft CBaseFilter/etc code comprised of about 30 source files, where as the output filter comprises of two or three required source files which we already had, so it's a huge win to compile time. Scaling is avoided whenever possible to minimize CPU usage. When the virtual camera is activated in OBS, the width, height, and frame interval are saved, that way if the filter is activated, it will always remember the last OBS resolution/interval that the virtual camera was activated with, even if OBS is not active. If for some reason the filter activates before OBS starts up, and OBS starts up with a different resolution, it will use simple point scaling intermittently, and then will remember the new scaling in the future. The scaler could use some optimization. FFmpeg was not opted for because the FFmpeg DLLs would have to be provided for both architectures, which would be about 30 megabytes in total, and would make writing the plugin much more painful. Thus a simple point scaling algorithm is used, and scaling is avoided whenever possible. (If another willing participant wants to have a go at improving the scaling then go for it. But otherwise, it avoids scaling whenever possible anyway, so it's not a huge deal)
2020-06-20 06:44:19 -07:00
Add preliminary DirectShow capture plugin This covers the basics of devices. Mostly functional but not at 100% yet. Uses 'libdshowcapture' library to capture directshow video/audio. Both libdshowcapture and the plugin still need some work. Should at least capture basic webcams and capture cards for the time being.
2014-05-30 03:29:48 -07:00
set(libdshowcapture_SOURCES
libdshowcapture/source/capture-filter.cpp
win-dshow: Allow use of YV12 video format Previously, due to a bug in libdshowcapture, the NV12 format was actually being used for YV12 erroneously, and no actual support for YV12 existed. This fixes the bug with NV12 and adds support for YV12.
2014-12-19 07:45:10 -08:00
libdshowcapture/source/output-filter.cpp
Fix CMakeLists.txt yet again
2014-05-30 03:45:34 -07:00
libdshowcapture/source/dshowcapture.cpp
win-dshow: Allow use of YV12 video format Previously, due to a bug in libdshowcapture, the NV12 format was actually being used for YV12 erroneously, and no actual support for YV12 existed. This fixes the bug with NV12 and adds support for YV12.
2014-12-19 07:45:10 -08:00
libdshowcapture/source/dshowencode.cpp
Add preliminary DirectShow capture plugin This covers the basics of devices. Mostly functional but not at 100% yet. Uses 'libdshowcapture' library to capture directshow video/audio. Both libdshowcapture and the plugin still need some work. Should at least capture basic webcams and capture cards for the time being.
2014-05-30 03:29:48 -07:00
libdshowcapture/source/device.cpp
win-dshow: Allow use of YV12 video format Previously, due to a bug in libdshowcapture, the NV12 format was actually being used for YV12 erroneously, and no actual support for YV12 existed. This fixes the bug with NV12 and adds support for YV12.
2014-12-19 07:45:10 -08:00
libdshowcapture/source/encoder.cpp
Add preliminary DirectShow capture plugin This covers the basics of devices. Mostly functional but not at 100% yet. Uses 'libdshowcapture' library to capture directshow video/audio. Both libdshowcapture and the plugin still need some work. Should at least capture basic webcams and capture cards for the time being.
2014-05-30 03:29:48 -07:00
libdshowcapture/source/dshow-base.cpp
Update libdshowcapture to 0.2.0
2014-09-06 12:45:21 -07:00
libdshowcapture/source/dshow-demux.cpp
Add preliminary DirectShow capture plugin This covers the basics of devices. Mostly functional but not at 100% yet. Uses 'libdshowcapture' library to capture directshow video/audio. Both libdshowcapture and the plugin still need some work. Should at least capture basic webcams and capture cards for the time being.
2014-05-30 03:29:48 -07:00
libdshowcapture/source/dshow-enum.cpp
libdshowcapture/source/dshow-formats.cpp
libdshowcapture/source/dshow-media-type.cpp
win-dshow: Implement decoding of encoded devices
2014-09-12 19:53:59 -07:00
libdshowcapture/source/dshow-encoded-device.cpp
Add preliminary DirectShow capture plugin This covers the basics of devices. Mostly functional but not at 100% yet. Uses 'libdshowcapture' library to capture directshow video/audio. Both libdshowcapture and the plugin still need some work. Should at least capture basic webcams and capture cards for the time being.
2014-05-30 03:29:48 -07:00
libdshowcapture/source/log.cpp)
set(libdshowcapture_HEADERS
libdshowcapture/dshowcapture.hpp
clang-format: Apply formatting Code submissions have continually suffered from formatting inconsistencies that constantly have to be addressed. Using clang-format simplifies this by making code formatting more consistent, and allows automation of the code formatting so that maintainers can focus more on the code itself instead of code formatting.
2019-06-22 22:13:45 -07:00
libdshowcapture/source/external/IVideoCaptureFilter.h
Add preliminary DirectShow capture plugin This covers the basics of devices. Mostly functional but not at 100% yet. Uses 'libdshowcapture' library to capture directshow video/audio. Both libdshowcapture and the plugin still need some work. Should at least capture basic webcams and capture cards for the time being.
2014-05-30 03:29:48 -07:00
libdshowcapture/source/capture-filter.hpp
win-dshow: Allow use of YV12 video format Previously, due to a bug in libdshowcapture, the NV12 format was actually being used for YV12 erroneously, and no actual support for YV12 existed. This fixes the bug with NV12 and adds support for YV12.
2014-12-19 07:45:10 -08:00
libdshowcapture/source/output-filter.hpp
Add preliminary DirectShow capture plugin This covers the basics of devices. Mostly functional but not at 100% yet. Uses 'libdshowcapture' library to capture directshow video/audio. Both libdshowcapture and the plugin still need some work. Should at least capture basic webcams and capture cards for the time being.
2014-05-30 03:29:48 -07:00
libdshowcapture/source/device.hpp
win-dshow: Allow use of YV12 video format Previously, due to a bug in libdshowcapture, the NV12 format was actually being used for YV12 erroneously, and no actual support for YV12 existed. This fixes the bug with NV12 and adds support for YV12.
2014-12-19 07:45:10 -08:00
libdshowcapture/source/encoder.hpp
Add preliminary DirectShow capture plugin This covers the basics of devices. Mostly functional but not at 100% yet. Uses 'libdshowcapture' library to capture directshow video/audio. Both libdshowcapture and the plugin still need some work. Should at least capture basic webcams and capture cards for the time being.
2014-05-30 03:29:48 -07:00
libdshowcapture/source/dshow-base.hpp
Update libdshowcapture to 0.2.0
2014-09-06 12:45:21 -07:00
libdshowcapture/source/dshow-demux.hpp
libdshowcapture/source/dshow-device-defs.hpp
Add preliminary DirectShow capture plugin This covers the basics of devices. Mostly functional but not at 100% yet. Uses 'libdshowcapture' library to capture directshow video/audio. Both libdshowcapture and the plugin still need some work. Should at least capture basic webcams and capture cards for the time being.
2014-05-30 03:29:48 -07:00
libdshowcapture/source/dshow-enum.hpp
libdshowcapture/source/dshow-formats.hpp
libdshowcapture/source/dshow-media-type.hpp
libdshowcapture/source/log.hpp)
add_library(win-dshow MODULE
${win-dshow_SOURCES}
win-dshow: Add FFmpeg decoding support
2014-09-12 19:51:45 -07:00
${win-dshow_HEADERS}
win-dshow: Add Virtual Camera (Windows) The virtual camera adds the ability to use the output of OBS itself as a camera that can be selected within other Windows applications. This is very loosely based upon the catxfish virtual camera plugin design. There is a shared memory queue, but instead of having 10-20 frames in the queue, there are now only 3 frames in the queue to minimize latency and reduce memory usage. The third frame is mostly to ensure that writing does not occur on the same frame being read; the delay is merely one frame at all times. The frames of the shared memory queue are NV12 instead of YUYV, which reduces the memory and data copied, as well as eliminate unnecessary conversion from NV12. Some programs (such as chrome, which uses webrtc to capture) do not support NV12 however, so an I420 conversion is provided, which is far less expensive than YUYV. The CPU cost of NV12 -> I420 is negligible in comparison. The virtual camera filter itself is based upon the output filter within the libdshowcapture library, which was originally implemented for other purposes. This is more ideal than the Microsoft example code because for one, it's far less convoluted, two, allows us to be able to customize the filter to our needs a bit more easily, and three, has much better RAII. The Microsoft CBaseFilter/etc code comprised of about 30 source files, where as the output filter comprises of two or three required source files which we already had, so it's a huge win to compile time. Scaling is avoided whenever possible to minimize CPU usage. When the virtual camera is activated in OBS, the width, height, and frame interval are saved, that way if the filter is activated, it will always remember the last OBS resolution/interval that the virtual camera was activated with, even if OBS is not active. If for some reason the filter activates before OBS starts up, and OBS starts up with a different resolution, it will use simple point scaling intermittently, and then will remember the new scaling in the future. The scaler could use some optimization. FFmpeg was not opted for because the FFmpeg DLLs would have to be provided for both architectures, which would be about 30 megabytes in total, and would make writing the plugin much more painful. Thus a simple point scaling algorithm is used, and scaling is avoided whenever possible. (If another willing participant wants to have a go at improving the scaling then go for it. But otherwise, it avoids scaling whenever possible anyway, so it's not a huge deal)
2020-06-20 06:44:19 -07:00
${virtualcam-output_SOURCES}
${virtualcam-output_HEADERS}
Add preliminary DirectShow capture plugin This covers the basics of devices. Mostly functional but not at 100% yet. Uses 'libdshowcapture' library to capture directshow video/audio. Both libdshowcapture and the plugin still need some work. Should at least capture basic webcams and capture cards for the time being.
2014-05-30 03:29:48 -07:00
${libdshowcapture_SOURCES}
${libdshowcapture_HEADERS})
target_link_libraries(win-dshow
Fix win-dshow module CMakeLists.txt Didn't include the DirectShow library, and forgot to add one source file
2014-05-30 03:43:53 -07:00
libobs
dshow: link to correct uuid libs Remove the .lib postfix from strmiids ksuser provides KSCATEGORY_ENCODER and similar GUIDS used wmcodecdspuuid provides MEDIASUBTYPE_H264 MEDIASUBTYPE_RAW_AAC1 and MEDIASUBTYPE_I420 so no need to define them in dshow-formats. The submodule will have to be updated to support this change.
2015-02-04 07:43:02 -08:00
strmiids
ksuser
wmcodecdspuuid
win-dshow: Add Virtual Camera (Windows) The virtual camera adds the ability to use the output of OBS itself as a camera that can be selected within other Windows applications. This is very loosely based upon the catxfish virtual camera plugin design. There is a shared memory queue, but instead of having 10-20 frames in the queue, there are now only 3 frames in the queue to minimize latency and reduce memory usage. The third frame is mostly to ensure that writing does not occur on the same frame being read; the delay is merely one frame at all times. The frames of the shared memory queue are NV12 instead of YUYV, which reduces the memory and data copied, as well as eliminate unnecessary conversion from NV12. Some programs (such as chrome, which uses webrtc to capture) do not support NV12 however, so an I420 conversion is provided, which is far less expensive than YUYV. The CPU cost of NV12 -> I420 is negligible in comparison. The virtual camera filter itself is based upon the output filter within the libdshowcapture library, which was originally implemented for other purposes. This is more ideal than the Microsoft example code because for one, it's far less convoluted, two, allows us to be able to customize the filter to our needs a bit more easily, and three, has much better RAII. The Microsoft CBaseFilter/etc code comprised of about 30 source files, where as the output filter comprises of two or three required source files which we already had, so it's a huge win to compile time. Scaling is avoided whenever possible to minimize CPU usage. When the virtual camera is activated in OBS, the width, height, and frame interval are saved, that way if the filter is activated, it will always remember the last OBS resolution/interval that the virtual camera was activated with, even if OBS is not active. If for some reason the filter activates before OBS starts up, and OBS starts up with a different resolution, it will use simple point scaling intermittently, and then will remember the new scaling in the future. The scaler could use some optimization. FFmpeg was not opted for because the FFmpeg DLLs would have to be provided for both architectures, which would be about 30 megabytes in total, and would make writing the plugin much more painful. Thus a simple point scaling algorithm is used, and scaling is avoided whenever possible. (If another willing participant wants to have a go at improving the scaling then go for it. But otherwise, it avoids scaling whenever possible anyway, so it's not a huge deal)
2020-06-20 06:44:19 -07:00
w32-pthreads
cmake: Replace FFMpeg modules with single module Now using components instead of one find_package call per module
2014-09-23 06:26:08 -07:00
${FFMPEG_LIBRARIES})
win-dshow: Add Virtual Camera (Windows) The virtual camera adds the ability to use the output of OBS itself as a camera that can be selected within other Windows applications. This is very loosely based upon the catxfish virtual camera plugin design. There is a shared memory queue, but instead of having 10-20 frames in the queue, there are now only 3 frames in the queue to minimize latency and reduce memory usage. The third frame is mostly to ensure that writing does not occur on the same frame being read; the delay is merely one frame at all times. The frames of the shared memory queue are NV12 instead of YUYV, which reduces the memory and data copied, as well as eliminate unnecessary conversion from NV12. Some programs (such as chrome, which uses webrtc to capture) do not support NV12 however, so an I420 conversion is provided, which is far less expensive than YUYV. The CPU cost of NV12 -> I420 is negligible in comparison. The virtual camera filter itself is based upon the output filter within the libdshowcapture library, which was originally implemented for other purposes. This is more ideal than the Microsoft example code because for one, it's far less convoluted, two, allows us to be able to customize the filter to our needs a bit more easily, and three, has much better RAII. The Microsoft CBaseFilter/etc code comprised of about 30 source files, where as the output filter comprises of two or three required source files which we already had, so it's a huge win to compile time. Scaling is avoided whenever possible to minimize CPU usage. When the virtual camera is activated in OBS, the width, height, and frame interval are saved, that way if the filter is activated, it will always remember the last OBS resolution/interval that the virtual camera was activated with, even if OBS is not active. If for some reason the filter activates before OBS starts up, and OBS starts up with a different resolution, it will use simple point scaling intermittently, and then will remember the new scaling in the future. The scaler could use some optimization. FFmpeg was not opted for because the FFmpeg DLLs would have to be provided for both architectures, which would be about 30 megabytes in total, and would make writing the plugin much more painful. Thus a simple point scaling algorithm is used, and scaling is avoided whenever possible. (If another willing participant wants to have a go at improving the scaling then go for it. But otherwise, it avoids scaling whenever possible anyway, so it's not a huge deal)
2020-06-20 06:44:19 -07:00
set_target_properties(win-dshow PROPERTIES FOLDER "plugins/win-dshow")
source_group("libdshowcapture\\Source Files" FILES ${libdshowcapture_SOURCES})
source_group("libdshowcapture\\Header Files" FILES ${libdshowcapture_HEADERS})
Add preliminary DirectShow capture plugin This covers the basics of devices. Mostly functional but not at 100% yet. Uses 'libdshowcapture' library to capture directshow video/audio. Both libdshowcapture and the plugin still need some work. Should at least capture basic webcams and capture cards for the time being.
2014-05-30 03:29:48 -07:00
Fix double invocation of install_obs_plugin in every single plugin
2014-08-19 05:24:59 -07:00
install_obs_plugin_with_data(win-dshow data)
win-dshow: Add Virtual Camera (Windows) The virtual camera adds the ability to use the output of OBS itself as a camera that can be selected within other Windows applications. This is very loosely based upon the catxfish virtual camera plugin design. There is a shared memory queue, but instead of having 10-20 frames in the queue, there are now only 3 frames in the queue to minimize latency and reduce memory usage. The third frame is mostly to ensure that writing does not occur on the same frame being read; the delay is merely one frame at all times. The frames of the shared memory queue are NV12 instead of YUYV, which reduces the memory and data copied, as well as eliminate unnecessary conversion from NV12. Some programs (such as chrome, which uses webrtc to capture) do not support NV12 however, so an I420 conversion is provided, which is far less expensive than YUYV. The CPU cost of NV12 -> I420 is negligible in comparison. The virtual camera filter itself is based upon the output filter within the libdshowcapture library, which was originally implemented for other purposes. This is more ideal than the Microsoft example code because for one, it's far less convoluted, two, allows us to be able to customize the filter to our needs a bit more easily, and three, has much better RAII. The Microsoft CBaseFilter/etc code comprised of about 30 source files, where as the output filter comprises of two or three required source files which we already had, so it's a huge win to compile time. Scaling is avoided whenever possible to minimize CPU usage. When the virtual camera is activated in OBS, the width, height, and frame interval are saved, that way if the filter is activated, it will always remember the last OBS resolution/interval that the virtual camera was activated with, even if OBS is not active. If for some reason the filter activates before OBS starts up, and OBS starts up with a different resolution, it will use simple point scaling intermittently, and then will remember the new scaling in the future. The scaler could use some optimization. FFmpeg was not opted for because the FFmpeg DLLs would have to be provided for both architectures, which would be about 30 megabytes in total, and would make writing the plugin much more painful. Thus a simple point scaling algorithm is used, and scaling is avoided whenever possible. (If another willing participant wants to have a go at improving the scaling then go for it. But otherwise, it avoids scaling whenever possible anyway, so it's not a huge deal)
2020-06-20 06:44:19 -07:00
win-dshow: Use cmake-based GUID for virtualcam
2020-09-06 17:04:06 -07:00
if(VIRTUALCAM_ENABLED)
win-dshow: Add VirtualCam installer scripts This adds two batch scripts to install and uninstall the virtual cam devices for installations where the installer could not be used. Most commonly, this is for portable installations or those who prefer the .zip file.
2020-09-05 18:13:00 -07:00
configure_file(virtualcam-install.bat.in "${CMAKE_CURRENT_BINARY_DIR}/data/virtualcam-install.bat")
configure_file(virtualcam-uninstall.bat.in "${CMAKE_CURRENT_BINARY_DIR}/data/virtualcam-uninstall.bat")
install_obs_data_from_abs_path(win-dshow "${CMAKE_CURRENT_BINARY_DIR}/data" "obs-plugins/win-dshow")
win-dshow: Use cmake-based GUID for virtualcam
2020-09-06 17:04:06 -07:00
add_subdirectory(virtualcam-module)
endif()