/g/ - Has anyone been able to successfully patch FFmpeg - Technology

Anonymous

06/19/26(Fri)10:26:38 No.109091050

File: MV5BYjhlMTVhMDQtOWUxZi00N(...).jpg (19 KB, 350x219)

Anonymous 06/19/26(Fri)10:26:38 No.109091050 Archived

Has anyone been able to successfully patch FFmpeg with FCVVDP? The patch was released in March 2026 and so was ffmpeg 8.0 so it should work. What the FUCK am I doing wrong mannnnn...

user01@DESKTOP-10GG5AB:/mnt/c/FCVVDP$ git clone --branch n8.0 --depth 1 https://git.ffmpeg.org/ffmpeg.git ffmpeg
Cloning into 'ffmpeg'...

user01@DESKTOP-10GG5AB:/mnt/c/FCVVDP$ cd ffmpeg
user01@DESKTOP-10GG5AB:/mnt/c/FCVVDP/ffmpeg$ cat RELEASE_NOTES
   The FFmpeg Project proudly presents FFmpeg 8.0 "Huffman", about 11
   months after the release of FFmpeg 7.1.

user01@DESKTOP-10GG5AB:/mnt/c/FCVVDP/ffmpeg$ git checkout n8.0
HEAD is now at 140fd65 Changelog: Remove "version <next>"
user01@DESKTOP-10GG5AB:/mnt/c/FCVVDP/ffmpeg$ git apply /mnt/c/FCVVDP/fcvvdp/patches/0001-feat-fcvvdp-support.patch
user01@DESKTOP-10GG5AB:/mnt/c/FCVVDP/ffmpeg$ ./configure --enable-fcvvdp
ERROR: fcvvdp not found

If you think configure made a mistake, make sure you are using the latest
version from Git.  If the latest version fails, report the problem to the
ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.libera.chat.
Include the log file "ffbuild/config.log" produced by configure as this will help
solve the problem.

More info on the project: https://github.com/halidecx/fcvvdp/blob/main/doc/cvvdp.md

Anonymous
06/19/26(Fri)15:59:15 No.109093261

Anonymous 06/19/26(Fri)15:59:15 No.109093261

>>109091050

bumpo for later. i may look into it.

meanwhile, state your system info and build environment as a starting point.

Anonymous
06/19/26(Fri)16:11:52 No.109093343

Anonymous 06/19/26(Fri)16:11:52 No.109093343

>>109091050
>>109093261 (Me)
didn't try anything yet, but just gave the build code a look.
did you actually install the library/header system-wide, or made their locations available to ffmpeg's configure (with `-I<include_path>`/`-L<lib_path>` flags)?

Anonymous
06/19/26(Fri)16:33:44 No.109093478

Anonymous 06/19/26(Fri)16:33:44 No.109093478

>>109093261
Not but I tried this on WSL on 2019 LTSC and it doesn't work either. Hardware is i5-6500 8GB RAM PC.

Do you really have to install a full version of loonix to het this shit working? I might be able to do it but I kinda don't want to waste my time off work configuring xorg and shit.

Anonymous
06/19/26(Fri)16:34:44 No.109093483

Anonymous 06/19/26(Fri)16:34:44 No.109093483

>>109093478
Not OP*

Anonymous
06/19/26(Fri)17:57:24 No.109093965

Anonymous 06/19/26(Fri)17:57:24 No.109093965

>>109093478
>Do you really have to install a full version of loonix
if FCVVDP supports windows, then no. and from a cursory look, i don't immediately see anything that would prevent it from building on windows.
but the problem with the average windows user (and new linux users, who are windows users from yesterday) is that they don't know how to build anything. so, i wouldn't be surprised at all if op didn't even build the library beforehand.

Anonymous
06/19/26(Fri)18:04:09 No.109094001

Anonymous 06/19/26(Fri)18:04:09 No.109094001

>>109093965 (Me)
i mean. just yesterday, a namefag larping wintard was talking about how clang is portable and rust is not. and some anons struggled to know what the hell he was talking about.
luckily, i have the ability to put myself in the brain of the clueless retarded, and think like them. so i knew he thought "portable" in the context of languages or language implementations, is the same "portable" in windows programs self contained in a folder lol.
the funniest part, is that he was wrong even with his "definition", because.. of course he would be.
i watched all that from a distance, because it's much funnier that way lmao.

Anonymous
06/19/26(Fri)19:27:28 No.109094376

Anonymous 06/19/26(Fri)19:27:28 No.109094376

>>109091050
Get a better CPU. Software efficiency is a thing of the past grandpa!