Package Details: ffmpeg-obs 7.1-1

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: 18
Popularity: 0.90
First Submitted: 2021-12-16 11:56 (UTC)
Last Updated: 2024-11-11 17:07 (UTC)

Required by (1916)

Sources (3)

Pinned Comments

tytan652 commented on 2022-07-23 05:48 (UTC) (edited on 2024-06-21 13:15 (UTC) by tytan652)

Please, this package follow Arch Linux ffmpeg package version (not the staging or the testing one).

Don't put ffmpeg-obs out-of-date if both packages are on the same version. If you do, you might be ignored in the future.

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 .. 3 4 5 6 7 8 9 10 11 12 13 Next › Last »

applebloom commented on 2023-03-11 19:20 (UTC)

FFMpeg now fails to find pocketsphinx and it was temporarily disabled in ffmpeg-full.

tytan652 commented on 2023-03-10 06:45 (UTC)

FFmpeg 6 has been push to stable repos.

The simplest way to update without conflict is to install ffmpeg then reinstall this package afterward.

BrianAllred commented on 2023-03-10 02:00 (UTC) 

error: failed to prepare transaction (could not satisfy dependencies)
:: installing ffmpeg-obs (6-1) breaks dependency 'libavcodec.so=59-64' required by mpv
:: installing ffmpeg-obs (6-1) breaks dependency 'libavdevice.so=59-64' required by mpv
:: installing ffmpeg-obs (6-1) breaks dependency 'libavfilter.so=8-64' required by mpv
:: installing ffmpeg-obs (6-1) breaks dependency 'libavformat.so=59-64' required by mpv
:: installing ffmpeg-obs (6-1) breaks dependency 'libavutil.so=57-64' required by mpv
:: installing ffmpeg-obs (6-1) breaks dependency 'libswscale.so=6-64' required by mpv

tytan652 commented on 2023-03-09 16:34 (UTC)

@Typology, you are missing dependencies in your system. This is not an issue from the package.

Typology commented on 2023-03-09 16:19 (UTC) 

ERROR: nvdec requested, but not all dependencies are satisfied: ffnvcodec

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.
==> ERROR: A failure occurred in build().
    Aborting...

tytan652 commented on 2023-02-03 18:58 (UTC)

@ptr1337, none of the FFmpeg package that I know have !lto, so no. If it is enabled by default it means that you have an issue because I have no issue to build in my chroot.

And for debug, I know that it is enabled by default but there is no point updating all my PKGBUILD to remove this.

ptr1337 commented on 2023-02-03 18:29 (UTC)

@tytan652

Please add options=(!lto), the package is not compiling when LTO is enabled right now. LTO got enabled in a older version of devtools as default. Also you should remove the options=(debug) from all of your packages. debug is now as default enabled in devtools. Arch has also removed options=(debug) from all their packages, cause it got enabled as default now.

Gnatzelle commented on 2023-02-03 10:52 (UTC) (edited on 2023-02-03 17:30 (UTC) by Gnatzelle)

Hi tytan...

There is this nasty bug atm with building ffmpeg from source (fix is also there): https://bugs.archlinux.org/task/77324#comment214748 Had to Cherry-Pick the commit to build your package again after a reinstall.

Would be nice if you could update the PkgBuild :)

EDIT: Thank you for the quick fix :D

thlmenezes commented on 2023-01-24 15:19 (UTC) (edited on 2023-01-24 23:43 (UTC) by thlmenezes)

[SOLVED] ~read edit1 for solution + improvement idea

Hello,

been trying to install obs-studio-tytan652, but I receive a build error on this package (ffmpeg-obs) build as seem below

ERROR: gnutls not found using pkg-config

I had it installed on my Manjaro Gnome 5.10 kernel, but changed to a Manjaro XFCE 6.10 kernel; after the error I've already tested with the old kernel, so I believe its not related to that.

My system is freshly formatted, and obs was one of the first programs I attempted installing.

Help?

EDIT 1: the problem was with pkg-config install, just had to reinstall and it worked

another program i tried installing gave me an error, maybe could be added those validations here

# aur/obs-linuxbrowser
./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from...
configure.ac:43: the top level
checking for glib-gettext >= 2.2.0...
  testing glib-gettextize... found 2.74.4
checking for intltool >= 0.25...
  testing intltoolize... found 0.51.0
checking for pkg-config >= 0.14.0...
  testing pkg-config... not found.
***Error***: You must have pkg-config >= 0.14.0 installed
  to build GConf.  Download the appropriate package for
  from your distribution or get the source tarball at
    'http://www.freedesktop.org/software/pkgconfig/releases/pkgconfig-0.14.0.tar.gz

In general to install the obs-studio-tytan654, I've installed at least pkg-config and dh-autoreconf, also installed automake, but I'm not certain if that was needed for obs or another package

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).

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