Upgrade to FFmpeg 6

[waddlesplash]

It has ABI differences with 4.2 and thus we must rebuild the media-addon against it immediately after upgrading.

[pulkomandy]

Should this really be a beta4 blocker? We're already going to have (once again) more than 1 year between releases, maybe it's time to stop adding new things to the beta4 milestone and have this in beta5 instead?

What's the reasoning for having it here?

[waddlesplash]

Note I recorded this as a "task"; I think the only thing required here is that we just rebuild the media-addon against the new FFmpeg. I don't think it will take any amount of time.

[waddlesplash]

We're still on a version of FFmpeg from 2019, is the main motivation for changing this.

[pulkomandy]

Ok, I guess I'm a bit worried about the regressions it could cause in media encoding/decoding if we need to adjust how we use the APIs. It would be annoying to further delay the release because of that. It really depends how much the API changed.

In general it's the kind of thing I'd rather do at the start and not at the end of a release cycle.

[jackburton]

Replying to pulkomandy:

Ok, I guess I'm a bit worried about the regressions it could cause in media encoding/decoding if we need to adjust how we use the APIs. It would be annoying to further delay the release because of that. It really depends how much the API changed.

In general it's the kind of thing I'd rather do at the start and not at the end of a release cycle.

I agree, especially since we already have various issues in media encoding/decoding. No need to introduce new, unknown ones.

[waddlesplash]

Based on reading the changelog, I think the changes are purely in terms of ABI? I agree if we have to make anything but trivial source changes then we should do this later.

[bruno]

If you do this later, will you move it to beta-5 or close the ticket for now?

[waddlesplash]

We now use a more current release of 4.2, I think this can be deferred at this point and we can jump straight to 5 when ready.

[pulkomandy]

I have made the necessary changes in the media add-on code.

The packages are available in haikuports (using the version suffix as usual to allow installing the packages side by side).

All that's needed now is updating the Haiku package repository to include the new version.

[waddlesplash]

Now done.