On 14-07-2020 01:29 pm, Gyan Doshi wrote:
Plan to push in 24h.
Pushed as 1ec2b3de5a074ccce555e33d7f2826d963d7
Gyan
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit lin
On 14-07-2020 05:14 pm, Andreas Rheinhardt wrote:
Gyan Doshi:
Some legacy applications such as AVI2MVE expect raw RGB bitmaps
to be stored bottom-up, whereas our RIFF BITMAPINFOHEADER assumes
they are always stored top-down and thus write a negative value
for height. This can prevent reading o
Gyan Doshi:
> Some legacy applications such as AVI2MVE expect raw RGB bitmaps
> to be stored bottom-up, whereas our RIFF BITMAPINFOHEADER assumes
> they are always stored top-down and thus write a negative value
> for height. This can prevent reading of these files.
>
> Option flipped_raw_rgb adde
On 14-07-2020 01:54 pm, Paul B Mahol wrote:
Why is option called rgb?
It have nothing to do with rgb.
Flipped can be any encoded file.
No, coded or uncoded streams with a codec tag or raw YUV bitmaps are
always indicated as positive height. Only raw RGB bitmaps can be
signaled as flipped.
Why is option called rgb?
It have nothing to do with rgb.
Flipped can be any encoded file.
On 7/14/20, Gyan Doshi wrote:
> Plan to push in 24h.
>
> On 08-07-2020 06:21 pm, Gyan Doshi wrote:
>> Some legacy applications such as AVI2MVE expect raw RGB bitmaps
>> to be stored bottom-up, whereas our
Plan to push in 24h.
On 08-07-2020 06:21 pm, Gyan Doshi wrote:
Some legacy applications such as AVI2MVE expect raw RGB bitmaps
to be stored bottom-up, whereas our RIFF BITMAPINFOHEADER assumes
they are always stored top-down and thus write a negative value
for height. This can prevent reading of
Some legacy applications such as AVI2MVE expect raw RGB bitmaps
to be stored bottom-up, whereas our RIFF BITMAPINFOHEADER assumes
they are always stored top-down and thus write a negative value
for height. This can prevent reading of these files.
Option flipped_raw_rgb added to AVI and Matroska mu
