You are not logged in.
Pages: 1
Rubberband is one of the most useful filters to change the pitch and tempo and with substantial quality. FFmpeg does not provide its own native or other means of pitch-shifting than to rely on other tools, such as sox or rubberband (cli tool, not library). If I recall correctly, rubberband support was included in previous versions of FFmpeg, then why remove it?
Offline
Checked a few revs of the ffmpeg package and it was never there from what I'm seeing. If you need it *now* rebuild with --enable-librubberband https://wiki.archlinux.org/title/Arch_Build_System or opt for ffmpeg-full from the AUR or so. If you want to see this mainlined make a low prio bug report feature request.
Offline
I originally brought this issue up, as other distributions such as Debian and Fedora provide librubberband. I tried to opt for ffmpeg-full but it is marked out of date, so I tried with ffmpeg-full-git but apparently due to patching failure, it failed at the prepare() stage.
patching file libavcodec/Makefile
Hunk #1 FAILED at 1096.
1 out of 1 hunk FAILED -- saving rejects to file libavcodec/Makefile.rej
patching file libavcodec/allcodecs.c
Hunk #1 succeeded at 799 (offset 20 lines).
patching file libavcodec/libsvt_vp9.c
==> ERROR: A failure occurred in prepare().
Aborting...
error: failed to build 'ffmpeg-full-git-5.2.r109920.gac6eec1fc2-1':
error: packages failed to build: ffmpeg-full-git-5.2.r109920.gac6eec1fc2-1
Offline
The flag [in ffmpeg-full] is perhaps erroneous as >=6.0 is in the testing repo.
Offline
You should not use -git of ffmpeg unless you absolutely know what you are doing, while ffmpeg-full is marked as "outdated" it is currently in line with the repository version but that is in the process of switching to ffmpeg 6 but that apparently has a few API regressions that need to get patched against beforehand anyway. So that ffmpeg-full is currently "outdated" is more correct with regards to the stable repository it should/would be compatible for.
Ah we coincided, yes that's what will be the case right now.
Last edited by V1del (2023-03-07 10:20:16)
Offline
Oh boy! ffmpeg-full can't find nvcc now.
ERROR: failed checking for nvcc.
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...
error: failed to build 'ffmpeg-full-5.1.2-4':
error: packages failed to build: ffmpeg-full-5.1.2-4
Offline
Pages: 1