FFmpeg 7.1 transition part 2#22551
Conversation
|
About |
Thank you for pointing that out, after you said that I noticed that Audacity has already been supporting FFmpeg 7 since Audacity version 3.6. In order to test that I reverted most of 04dd0b7 locally and inserted Should I remove That seems like possibly a good thing to wait a little while and put in a "part 3" PR, since this PR is already pretty large, and the changes to |
|
I do not think you should touch audacity-ffmpeg. It exists for some reason. |
|
The issue linked to by the comment has been closed for a long time, |
|
Are we ready to merge this batch in the meantime? |
|
Probably it will be better to replace vlc-qt's patch symlink with the following code in |
The symlinks work fine, why would a |
|
To avoid messing with patches after each VLC update. |
I'm not sure I follow. I personally think the explicitness of the symlinks outweighs the benefit of automatically pulling in new patches. |
|
We should get this merged before even more of them get yoinked for acute issues. |
Patch cherry-picked from DeaDBeeF-Player/deadbeef@d4cca560
Replace the use of `frame->channels` with the hardcoded `channels` global variable the app has, and replace the use of `swr_alloc_set_opts()` with calls to `av_channel_layout_default()` and `swr_alloc_set_opts2()`
These link to the identical patches in the main/vlc package, similar to how there are symbolic links for patches in the x11/vim-gtk package, to the main/vim package.
46d9cbb to
47dc6c9
Compare
yes sorry i didn't know whether it needs my approval or not, if it looks ready to you then it's ready, and afterward I will make another PR with the revision bumps for |
Well it's your PR, so I didn't wanna go over your head on this, but since sylirre and Grimler had started bumping some of the packages in this PR I felt it was best to get it merged now so we can have the related issues closed.
Thank you. |

Progress on #22502
Bumped packages
Packages that require bumping to be compatible with FFmpeg 7.
handbrake: 1.9.0ffplay: 7.1 to matchffmpegPatched packages
Packages that require patching to successfully build against FFmpeg 7.
vlc+vlc-qt: patches copied from Debian Testingdeadbeef: patch cherry-pickedoshu: I wrote and tested the patch for this package by myself. It works for me, but hopefully it is good enough to work for everyone.Recompiled packages
Packages that are revision-bumped to recompile against FFmpeg 7 with no other changes.
audacious-pluginskf6-kfilemetadatakid3mgbamltspekSkipped packages
Packages that I suspect do not technically need to be revision-bumped (recompiled), because I suspect that they continue to fully work after updating the
ffmpegpackage to FFmpeg 7, without being recompiled.A primary reason for me to suspect that is that the command
pkg install -y $pkgname && for f in $(dpkg -L $pkgname); do ldd $f 2>/dev/null | grep libav; doneprints nothing, for all of them. This strongly suggests, but does not absolutely guarantee, that they all use some methods of connecting to FFmpeg that do not require recompilation after major FFmpeg version updates.If extra caution is wanted to make sure no revision bumps are missed and there is no possibility of a mistake, then maybe these should all be marked with revision bumps as well, just to be on the safe side.
firefoxthunderbirdkdenliveshotcutDifficult packages
These packages are supposed to be compiled against FFmpeg, but currently are not because it is very difficult for me to compile them against FFmpeg 7.
I have not yet found any existing operating system that shows an example of compiling
python-torchaudioagainst FFmpeg 7,but maybe there will be one soon, or if that doesn't happen then I could attempt to make patches for them by myself but it might take a long time.
python-torchaudiopython-torchvisionConfusing package
waypipeWhen I check, it appears that
waypipeis not currently capable of calling FFmpeg API on Termux (regardless of whether the FFmpeg version is 6 or 7). This suggests that FFmpeg is not a true build or runtime dependency ofwaypipeon Termux yet. More details are explained in a comment inbuild.sh.I am not great at Wayland or very experienced with it, I hope that someone who is familiar with Wayland or a contributor to Waypipe upstream could explain what is going on and if there is any workaround.