Actually it is not my patch (as should be obvious as From: is not me) and
*NO* changes in API/ABI of openjpeg are happening with upsream patch. As
for your ABI... There is only one correct way to manipulate openjpeg API,
if you did that wrong, it is your problem.
Standard thing: "unexpected that u
On Sun, Jun 06, 2021 at 05:42:54PM +0300, Valerii Zapodovnikov wrote:
> Did you even read the commit message? You need to apply a patch to openjpeg
> itself. Sigh.
yes i read your commit message.
you are changing the API/ABI of openjpeg and doing a matching change in
the interface in ffmpeg to ope
Did you even read the commit message? You need to apply a patch to openjpeg
itself. Sigh.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ.
On Sun, Jun 06, 2021 at 09:27:32AM +0300, Valerii Zapodovnikov wrote:
> From: Rémi Achard
>
> Patch should be applied to decode XYZ samples with not native
> decoder in ffmpeg (-c:v libopenjpeg, not -c:v jpeg2000). jpeg2000
> works already.
> Now, this is AFAIK a patch that should be applied afte
From: Rémi Achard
Patch should be applied to decode XYZ samples with not native
decoder in ffmpeg (-c:v libopenjpeg, not -c:v jpeg2000). jpeg2000
works already.
Now, this is AFAIK a patch that should be applied after upstream's
patch: https://github.com/uclouvain/openjpeg/pull/1200
Please note th
