ironon · June 18, 2025 19:18
diff --git a/how to get VideoProcessingFramework to run in 2025 b/how to get VideoProcessingFramework to run in 2025
 how to get VideoProcessingFramework (PyNvCodec) to run in 2025

 (by no means a comprehensive guide this took me many hours of random debugging and random jankness)

 0. download the visual studio installer if you dont have it already, and install the MSVC v144 compiler, which unless you look really closely will be labeled as the v143 compiler for some reason, its only like 40 words into the official title that it tells you its actually v144 but whatever i didn't care or anything
 1. download FFMPEG 6 (an old version) as this will not work with the latest FFMPEG versions (https://web.archive.org/web/20230301132406if_/https://www.gyan.dev/ffmpeg/builds/packages/ffmpeg-6.0-full_build-shared.7z)
 2. set an environment variable in your system: SKBUILD_CONFIGURE_OPTIONS to '-DTC_FFMPEG_ROOT=<FFMPEG LOCATION>'  (in my case, it was C:\Users\macphersond\Downloads\ffmpeg-6.0-full_build-shared\ffmpeg-6.0-full_build-shared)
 (<FFMPEG_LOCATION> should have a bunch of folders in it, lib and bin folders and stuff)
 3. run `pip install . --config-settings=cmake.args="-DCMAKE_CXX_FLAGS=-D__SSE4A__"`
 4. when you get a cmake error for having too low of a cmake version, open in vs-code or any editor "C:\VideoProcessingFramework\_skbuild\win-amd64-3.10\cmake-build\_deps\pybind11-src\CMakeLists.txt" and find where it says "cmake_minimum_required(VERSION 3.4)"
 5. run the same pip command as step 3, except while its running, go into the CMakeLists.txt file and change the "3.4" to "3.6", while spamming Ctrl+S. You may have to modify the file inbetween saves to ensure VSCode actually saves it. This is because the build process will overwrite any change you make, and put it back to 3.4, which is why we are overwriting it constantly so we overwrite it's overwriting.
	how to get VideoProcessingFramework (PyNvCodec) to run in 2025

	(by no means a comprehensive guide this took me many hours of random debugging and random jankness)

	0. download the visual studio installer if you dont have it already, and install the MSVC v144 compiler, which unless you look really closely will be labeled as the v143 compiler for some reason, its only like 40 words into the official title that it tells you its actually v144 but whatever i didn't care or anything
	1. download FFMPEG 6 (an old version) as this will not work with the latest FFMPEG versions (https://web.archive.org/web/20230301132406if_/https://www.gyan.dev/ffmpeg/builds/packages/ffmpeg-6.0-full_build-shared.7z)
	2. set an environment variable in your system: SKBUILD_CONFIGURE_OPTIONS to '-DTC_FFMPEG_ROOT=<FFMPEG LOCATION>' (in my case, it was C:\Users\macphersond\Downloads\ffmpeg-6.0-full_build-shared\ffmpeg-6.0-full_build-shared)
	(<FFMPEG_LOCATION> should have a bunch of folders in it, lib and bin folders and stuff)
	3. run `pip install . --config-settings=cmake.args="-DCMAKE_CXX_FLAGS=-D__SSE4A__"`
	4. when you get a cmake error for having too low of a cmake version, open in vs-code or any editor "C:\VideoProcessingFramework\_skbuild\win-amd64-3.10\cmake-build\_deps\pybind11-src\CMakeLists.txt" and find where it says "cmake_minimum_required(VERSION 3.4)"
	5. run the same pip command as step 3, except while its running, go into the CMakeLists.txt file and change the "3.4" to "3.6", while spamming Ctrl+S. You may have to modify the file inbetween saves to ensure VSCode actually saves it. This is because the build process will overwrite any change you make, and put it back to 3.4, which is why we are overwriting it constantly so we overwrite it's overwriting.