qtav usage of libav

[Steven Robbins]

On Sunday, September 18, 2022 10:33:16 A.M. CDT Gilles Caulier wrote:
> Not really. But as ffmpeg API has changed between 4 and 5, and as QtAV
> API is mostly a wrapper around ffmpeg, this can be relevant.
> 
> Remember that AV* classes from QtAV are based historically on libav,
> and now, in fact ffmpeg, as libav is a dead project.

You mean libav as in https://libav.org/ ?  
I wasn't aware of that.

> When I reviewed QtAV code for digiKam integration I saw a lot of
> pre-compiler wrapping between libav and ffmpeg API, for regression
> compatibility. Typically code must continue to compile with all libav
> API, but in fact we don't care.

So are you saying that it is OK to remove libav compatibility code now?

To be clear: I'm NOT planning any such thing at present.  Right now I'm 
focused on writing tests that expose the bugs (with ffmpeg5), then fixing them.  
But, hypothetically, if I get through all that ... would it be of interest to 
remove unused code in qtav?

-Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20220918/3155f78b/attachment.sig>