Package Details: ffmpeg-obs 6.1.1-10

Git Clone URL: https://aur.archlinux.org/ffmpeg-obs.git (read-only, click to copy)
Package Base: ffmpeg-obs
Description: Complete solution to record, convert and stream audio and video with fixes for OBS Studio. And various options in the PKGBUILD
Upstream URL: https://ffmpeg.org/
Keywords: audio codec convert encoder ffmpeg media obs vaapi video
Licenses: GPL-3.0-only
Conflicts: ffmpeg
Provides: ffmpeg, libavcodec.so, libavdevice.so, libavfilter.so, libavformat.so, libavutil.so, libpostproc.so, libswresample.so, libswscale.so
Submitter: tytan652
Maintainer: tytan652
Last Packager: tytan652
Votes: 17
Popularity: 0.37
First Submitted: 2021-12-16 11:56 (UTC)
Last Updated: 2024-04-07 06:53 (UTC)

Required by (1827)

Sources (3)

Pinned Comments

tytan652 commented on 2022-07-23 05:48 (UTC)

Please, this package follow Arch Linux ffmpeg package version. Don't put ffmpeg-obs out-of-date if both packages are on the same version.

tytan652 commented on 2021-12-17 15:32 (UTC)

OBS Project actually patch FFmpeg to fix some issues and also add RIST support starting from 27.2.

So I created this package, a ffmpeg package that ensure that you have those.

I really wanted to not do this but some fixes are needed, so I did my best to add those "feature-set options".

They allow you to build ffmpeg with feature-set based on other ffmpeg packages from AUR.

Read the PKGBUILD for more information about them.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »

zeroconf commented on 2022-09-04 19:20 (UTC)

Sounds like issue(s) fixed as later I tried, compiled fine. Now new issue (bizarre messages but still works) appeared with software update but it's not related with current package, more like packaging system itself (pacman, yay).

tytan652 commented on 2022-09-04 15:49 (UTC)

@zeroconf it compiles fine on an updated chroot, the issue is on your side.

zeroconf commented on 2022-09-04 15:12 (UTC)

Currently (September 4, 2022) impossible to compile, in the end of package installation:

during RTL pass: final
libavcodec/x86/vp9dsp_init_16bpp_template.c: In function ‘avg_8tap_smooth_64v_10_sse2’:
libavcodec/x86/vp9dsp_init_16bpp_template.c:57:1: internal compiler error: Segmentation fault
   57 | filters_8tap_1d_fn3(avg, BPC, sse2, sse2, 16bpp)
      | ^
0x1789784 internal_error(char const*, ...)
        ???:0
0x73bd76 lookup_decl_die(tree_node*)
        ???:0
Please submit a full bug report, with preprocessed source (by using -freport-bug).
Please include the complete backtrace with any bug report.
See <https://bugs.archlinux.org/> for instructions.
lto-wrapper: fatal error: gcc returned 1 exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
make: *** [ffbuild/library.mak:119: libavcodec/libavcodec.so.59] Error 1
==> ERROR: A failure occurred in build().
    Aborting...
error: target not found: libajantv2
 -> error making: ffmpeg-obs

Could not find a way to use that suggested -freport-bug parameter.

tytan652 commented on 2022-08-20 10:05 (UTC)

@Freso, I was the maintainer of ffmpeg-ndi and the patch that added NDI (4, 5 was not there when I began) back and I decided to stop maintaining it.

And since I stopped maintaining it, I removed the NDI option here because it is no longer maintained, if one day someone decided to maintain ffmpeg-ndi I would maybe try to re-add it.

Freso commented on 2022-08-20 09:52 (UTC)

I don’t see any explanation in the commit message, so: why was the NDI option dropped? Is NDI now always included or is it gone completely?

tytan652 commented on 2022-07-23 06:06 (UTC)

Yes, but it is not updated to 5.1. For now ffmpeg-obs is up do date because ffmpeg is still 5.0.1.

HurricanePootis commented on 2022-07-23 05:58 (UTC)

ffmpeg has been marked out of date as well https://archlinux.org/packages/extra/x86_64/ffmpeg/

tytan652 commented on 2022-07-23 05:48 (UTC)

Please, this package follow Arch Linux ffmpeg package version. Don't put ffmpeg-obs out-of-date if both packages are on the same version.

gardotd426 commented on 2022-07-12 12:56 (UTC) (edited on 2022-07-12 13:19 (UTC) by gardotd426)

I'll also add that something seems to be wrong with the PKGBUILD, in that it doesn't enable any of the LLVM Nvidia decoders when running the normal PKGBUILD without any envvars. You have to enable the proprietary stuff to get support for any of that.

Here's with FFMPEG_OBS_CUDA=ON


ffmpeg -decoders | grep nv

 V..... av1_cuvid            Nvidia CUVID AV1 decoder (codec av1)
 V....D dsicinvideo          Delphine Software International CIN video
 V..... h264_cuvid           Nvidia CUVID H264 decoder (codec h264)
 V..... hevc_cuvid           Nvidia CUVID HEVC decoder (codec hevc)
 V....D idcinvideo           id Quake II CIN video (codec idcin)
 V..... mjpeg_cuvid          Nvidia CUVID MJPEG decoder (codec mjpeg)
 V..... mpeg1_cuvid          Nvidia CUVID MPEG1VIDEO decoder (codec mpeg1video)
 V..... mpeg2_cuvid          Nvidia CUVID MPEG2VIDEO decoder (codec mpeg2video)
 V..... mpeg4_cuvid          Nvidia CUVID MPEG4 decoder (codec mpeg4)
 V..... vc1_cuvid            Nvidia CUVID VC1 decoder (codec vc1)
 V..... vp8_cuvid            Nvidia CUVID VP8 decoder (codec vp8)
 V..... vp9_cuvid            Nvidia CUVID VP9 decoder (codec vp9)
 V....D wnv1                 Winnov WNV1
 A....D twinvq               VQF TwinVQ

And here is just running the standard PKGBUILD with no changes:


ffmpeg -decoders | grep -i nv

 V....D dsicinvideo          Delphine Software International CIN video
 V....D idcinvideo           id Quake II CIN video (codec idcin)
 V....D wnv1                 Winnov WNV1
 A....D twinvq               VQF TwinVQ

I'll add that ffmpeg -hwaccels still shows cuda and vdpau on both packages.

But regardless of whether FFMPEG_OBS_CUDA=ON is enabled or not, I still don't get av1_vdpau as a possible decoder, which is what's supposed to be the new one.

gardotd426 commented on 2022-07-12 12:49 (UTC)

ffmpeg has added av1_vdpau decode support to allow Ampere GPUs to use VDPAU for AV1 hardware decoding in ffmpeg. This was done after libvdpau v1.5 added support for AV1 decoding.

The current tag used in the PKGBUILD for ffmpeg does indeed include the commits enabling AV1 VDPAU decode, but it is not listed in the available decoders when using ffmpeg-obs. I'm not sure if it's a configuration option or what, but something is definitely wrong.

I have an RTX 3090, with full AV1 decoding support, and the NV control panel reports that AV1 decode support is indeed recognized. I also have libvdpau 1.5 installed. It's not an issue on my end. I'd appreciate if you could maybe look into it.

Here's the commit @ ffmpeg: https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/a44fba0b5b3b4090f9238751736198ddd1f0f1d5

And here is someone demonstrating that support shows up for them when building ffmpeg directly from master: https://github.com/xuanruiqi/vdpau-va-driver-vp9/issues/3#issuecomment-1181426181

Finally, the article announcing this from Phoronix: https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-AV1-VDPAU-FFmpeg

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »