Reason is simple:
-
AV_FRAME_DATA_SEI_UNREGISTEREDhas been added with FFmpeg 4.4: avutil: add AV_FRAME_DATA_SEI_UNREGISTERED side data type · FFmpeg/FFmpeg@bc8ab08 · GitHub - Debian Bullseye provides FFmpeg 4.3:
https://packages.debian.org/bullseye/ffmpeg - So either
ha-avmaking use ofAV_FRAME_DATA_SEI_UNREGISTEREDgets reverted, or it won’t be possible to compile it on any Debian version below Bookworm (and many other distros), unless FFmpeg (the development headers) is compiled as well.
If you are just installing it with pip, which is also what HA core does on first service start, then this is only relevant on 32-bit ARM and RISC-V (and other rare architectures), as PyPI provides pre-compiled wheels for x86 and aarch64: https://pypi.org/project/ha-av/#files
For 32-bit ARM Debian and Raspbian (and some Ubuntu versions where library versions match), piwheels is an alternative. But well, it provides Python 3.7 and 3.9 wheels only, until they decide to add support for Bookworm, and as it builds against respective Debian repo libraries, recent builds fail for exactly the same reason: https://piwheels.org/project/ha-av/
I do understand that going with recent dependencies/features is great, sometimes make certain things much easier, and users using distros which natively ship too old software is not an issue of upstream developers. But it would make the life of many 32-bit ARM users much easier if:
- There would be a way to revert or make the use of
AV_FRAME_DATA_SEI_UNREGISTEREDinha-avoptional - Or make the use of
ha-avitself optional for HA core: New modules PyTurboJPEG and ha-av installed on first HA core start
Sorry for the code-formatted links, as new users are restricted to 2 links per post.