Package Details: ffmpeg-mmal 2:5.0.1-3

Git Clone URL: https://aur.archlinux.org/ffmpeg-mmal.git (read-only, click to copy)
Package Base: ffmpeg-mmal
Description: ffmpeg built with MMAL hardware acceleration support for Raspberry Pi
Upstream URL: https://ffmpeg.org/
Licenses: GPL3
Conflicts: ffmpeg
Provides: ffmpeg, libavcodec.so, libavdevice.so, libavfilter.so, libavformat.so, libavutil.so, libpostproc.so, libswresample.so, libswscale.so
Submitter: fmang
Maintainer: fmang
Last Packager: fmang
Votes: 12
Popularity: 0.000102
First Submitted: 2016-09-14 09:46 (UTC)
Last Updated: 2022-06-20 20:32 (UTC)

Required by (1576)

Sources (3)

Latest Comments

1 2 3 4 5 6 .. 8 Next › Last »

DragonX256 commented on 2022-04-20 15:45 (UTC)

@strshr It's unsupported by upstream, because of moving to v4l2.

strshr commented on 2022-04-20 15:42 (UTC)

Is 64 bit still unsupported? Getting the mmal not found exception.

DragonX256 commented on 2021-10-28 00:59 (UTC) (edited on 2021-10-28 00:59 (UTC) by DragonX256)

@fmang Okay, did as you told me, and it worked! I suppose it's yay's AUR helper fault or something. Thanks!

fmang commented on 2021-10-27 21:08 (UTC)

@DragonX256 The PKGBUILD does not hardcode any dependency’s version number, only the built binary package requires concrete version numbers. libvpx and x264 got updated on October 22th, so the pkgrel bump should be enough to trigger the rebuild with the new versions.

Note however that if you built ffmpeg-mmal before your system upgrade, it would be hard-linked to the old dependencies. If that’s the case, your best option is to uninstall ffmpeg-mmal, upgrade your system, then rebuild ffmpeg-mmal. Also note that pacman -Syu, not being aware of AUR, won’t be smart enough to detect the new ffmpeg-mmal and rebuild it automatically.

DragonX256 commented on 2021-10-27 00:33 (UTC)

@fmang Well bumping pkgrel didn't do anything. PKGBUILD still have hard dependencies on versions of packages, which got updated recently. You should change theirs versions.

fmang commented on 2021-10-26 20:28 (UTC)

@DragonX256 I’ve updated the package right around the time you posted your comment. That issue should be solved now.

DragonX256 commented on 2021-10-26 16:02 (UTC)

Cannot build package because of hard dependencies:

:: installing libvpx (1.11.0-1) breaks dependency 'libvpx.so=6-32' required by ffmpeg-mmal
:: installing x264 (3:0.163.r3060.5db6aa6-1) breaks dependency 'libx264.so=161-32' required by ffmpeg-mmal

fmang commented on 2021-08-16 17:31 (UTC)

@cyph84 About AMF, I don’t see the point in keeping it enabled either. I updated the PKGBUILD.

fmang commented on 2021-08-16 17:24 (UTC)

@cyph84 If you’d like to share a working build of mpv for Raspberry Pi, you may create a new mpv-rpi package. The one I used to maintain was basically the upstream PKGBUILD with --enable-rpi added, and depending on ffmpeg-mmal instead of ffmpeg.

cyph84 commented on 2021-08-16 17:18 (UTC) (edited on 2021-08-16 17:20 (UTC) by cyph84)

Latest ffmpeg-mmal seems to be not building with amf-headers:

/usr/bin/ld: libavcodec/amfenc_h264.o: in function `GetDefaultChannelLayout':
amfenc_h264.c:(.text+0x0): multiple definition of `GetDefaultChannelLayout'; libavcodec/amfenc.o:amfenc.c:(.text+0x44): first defined here
/usr/bin/ld: libavcodec/amfenc_hevc.o: in function `GetDefaultChannelLayout':
amfenc_hevc.c:(.text+0x0): multiple definition of `GetDefaultChannelLayout'; libavcodec/amfenc.o:amfenc.c:(.text+0x44): first defined here
collect2: error: ld returned 1 exit status
make: *** [ffbuild/library.mak:103: libavcodec/libavcodec.so.58] Error 1

Don't see much harm in just disabling amf