AVDemuxer mediastatus after unload call?

[Gilles Caulier]

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.

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.

Gilles

Le dim. 18 sept. 2022 à 15:21, Steven Robbins <steve at sumost.ca> a écrit :
>
> On Sunday, September 18, 2022 2:59:37 A.M. CDT Gilles Caulier wrote:
> > Hi Steven,
> >
> > Good question. I will also place another brick in the wall : this is
> > different between ffmpeg 4 and ffmpeg 5, as the API has changed a lot
> > ?
>
> Wait -- are you suggesting this has something to do with the base ffmpeg
> libraries from ffmpeg.org?    The media status code is all within AVDemuxer, so
> I would think the "media status" notion is defined by qtav/digikam -- no?
>
> As to ffmpeg 4 vs 5: I see no conditional code in the load() and unload()
> functions that suggest it has changed.
>
> -Steve