Search Criteria
Package Details: ffmpeg-normalize 1.31.1-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/ffmpeg-normalize.git (read-only, click to copy) |
---|---|
Package Base: | ffmpeg-normalize |
Description: | Normalize loudness of audio and video files using FFmpeg |
Upstream URL: | https://github.com/slhck/ffmpeg-normalize |
Keywords: | audio ffmpeg normalization |
Licenses: | MIT |
Submitter: | nicoulaj |
Maintainer: | willemw |
Last Packager: | willemw |
Votes: | 6 |
Popularity: | 0.000006 |
First Submitted: | 2019-04-13 20:49 (UTC) |
Last Updated: | 2025-02-20 06:41 (UTC) |
Dependencies (9)
- ffmpeg (ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-cudaAUR, ffmpeg-decklinkAUR, ffmpeg-amd-fullAUR, ffmpeg-ffplayoutAUR, ffmpeg-gitAUR, ffmpeg-amd-full-gitAUR, ffmpeg-fullAUR, ffmpeg-full-gitAUR, ffmpeg-libfdk_aacAUR, ffmpeg-headlessAUR, ffmpeg-obsAUR)
- python-colorlog
- python-ffmpeg-progress-yieldAUR
- python-tqdm
- python-build (make)
- python-installer (make)
- python-setuptools (make)
- python-wheel (make)
- python-pytest (check)
Latest Comments
1 2 Next › Last »
chungy commented on 2025-02-07 08:46 (UTC)
Thanks, I needed to rebuild python-ffmpeg-progress-yield.
willemw commented on 2025-02-07 08:20 (UTC)
@chungy:
checkrebuild
is in packagerebuild-detector
. It will also automatically warn you during a system upgrade. Very useful.Or try this:
pacman -Ql python-ffmpeg-progress-yield
should list files in/usr/lib/python3.13
, not in/usr/lib/python3.12
in which case that package needs to be rebuilt.chungy commented on 2025-02-07 06:18 (UTC)
@williemw I don't have that command.
willemw commented on 2025-02-05 07:37 (UTC)
@chungy: check, by running
checkrebuild
, to see if there are any "out-of-date" packages that need to be rebuilt.chungy commented on 2025-02-05 07:26 (UTC)
This package both fails to run and fails to build, likely after the Python 3.13 update.
willemw commented on 2024-07-15 17:25 (UTC)
@periode:
Try building with the official ffmpeg package (temporarily) installed.
Running
ffmpeg -encoders 2>&1 | grep libx265
should print 2 lines. Maybe those encoders were not built into the custom ffmpeg.See https://github.com/slhck/ffmpeg-normalize: it shows you how to have a static ffmpeg version on your system which you can use just for ffmpeg-normalize, in case you don't want to uninstall your custom ffmpeg permanently.
periode commented on 2024-07-15 12:32 (UTC)
@willemw
I just did, and here's the error:
I have a custom build of ffmpeg on my machine, so looks like this is the issue?
willemw commented on 2024-07-04 12:02 (UTC) (edited on 2024-07-04 12:07 (UTC) by willemw)
@periode: Strange. Cannot reproduce (in a clean chroot build environment).
Maybe build and install with the tests disabled. Then run for example
ffmpeg-normalize test/test.mp4 -c:v libx265
from thesrc/ffmpeg-normalize-1.28.2
build directory.periode commented on 2024-07-03 14:08 (UTC)
The ffmpeg tests fail for me:
I can't paste whole output, so here's the summary:
1 2 Next › Last »