Comment 7 for bug 1982775

Revision history for this message
In , Caulier-gilles-9 (caulier-gilles-9) wrote :

Hi Erich,

>In our packaging we simply had forced it with "DENABLE_MEDIAPLAYER=ON" in our debian/rules file, and removing that enabled it to build in my >PPA. I'm working with one of our more senior Ubuntu developers to see if we should proceed with that route, or if he wants to do a manual patch >to port it over to ffmpeg5 as he has more experience with that than I do.

Thanks to your proposal for porting help to ffmpeg5.

In all cases, ffmpeg 5 must be done in 8.x. See below the reasons why:

1/ 7.x use a maintenance branch named qt5-maintenance where no new main features will be add.
2/ 7.x Media Player feature depend of QtAv external dependency. QtAv use ffmpeg API.
3/ QtAv is not maintained since February 2022.
4/ In 8.x we include QtAv in digiKam core and we apply a lots of patch to port Qt6, ffmpeg5, and fix plenty of bugs.
5/ ffmpeg 5 port must be done in QtAV code includes in 8.x, as 85% of the job is already done.

The QtAV code in located here in digiKam 8.x (master branch) :

https://invent.kde.org/graphics/digikam/-/tree/master/core/libs/video/qtav

Look well the TODO list from the REDAME file.

There is an entry in bugzilla where we list the QtAV integration progress and the identified problem with the ffmpeg 5 API :

https://bugs.kde.org/show_bug.cgi?id=448681

Look the comment #33. The main problems are AVCodecParameters and AVCodecContext in QtAV code which are not properly ported to ffmpeg 5. The side effect is a quickly freeze of media player when a video is read.

We will really appreciate all contributions to finalize the ffmpeg 5 port. Please use the Gitlab Merge Request workflow to contribute to digiKam source code.

https://invent.kde.org/graphics/digikam/-/merge_requests

Thanks in advance

Gilles Caulier