Index | Thread | Search

From:
Brad Smith <brad@comstyle.com>
Subject:
Re: UPDATE: FFmpeg 6.1.1
To:
Rafael Sadowski <rafael@sizeofvoid.org>
Cc:
Theo Buehler <tb@theobuehler.org>, ports@openbsd.org
Date:
Wed, 25 Sep 2024 03:20:34 -0400

Download raw body.

Thread
On 2024-09-25 2:16 a.m., Rafael Sadowski wrote:
> On Wed Sep 25, 2024 at 01:31:12AM GMT, Brad Smith wrote:
>> On 2024-09-24 6:28 a.m., Theo Buehler wrote:
>>> On Sun, Sep 22, 2024 at 07:55:38AM +0200, Rafael Sadowski wrote:
>>>> Could some throw this into a bulk build please?
>>>>
>>>> The entire Qt5/Qt6 ecosystem depends on FFmpeg API >= 5.
>>> This doesn't look too bad. The qtwebengines depend on an extra symbol
>>> that would need to be patched into system ffmpeg since the chromium
>>> devs didn't want to listen to the ffmpeg devs:
>>>
>>> https://ffmpeg.org/pipermail/ffmpeg-devel/2021-September/285401.html
>>>
>>> That's a bit annoying. Link to the patch below.
>>>
>>> vlc has some vaapi issues. I haven't looked further. A few of the other
>>> fallout has patches floating around the net, others don't seem to be
>>> ready for new ffmpeg and others are probably ready for removal.
>>>
>>> Here's the short list. Not sure how badly the bulk was cut short, seems
>>> to have affected mostly the Qt ecosystem.
>>>
>>> audio/chromaprint
>>> audio/moc
>> I was looking at trying to update this to a fork that is maintained that
>> also has update
>> to date FFmpeg patches merged.
> Thanks
>
>>> audio/potamus
>> I want to drop potamus.
> Yes please let's start a poll  on ports@.
>
>>> emulators/ppsspp
>>> games/alephone/alephone
>>> graphics/openscenegraph
>> Diff already posted.
> Does your patches work with current and 6 or only 6? That information
> would be helpful for the upgrade/commit process.

Anything I have sent out so far is intended to work with current and 
with newer FFmpeg.