On Mon, Nov 25, 2013 at 12:20 PM, Pawel Veselov <
pawel....@gmail.com> wrote:
> On Mon, Nov 25, 2013 at 11:56 AM, Johann Koenig <
johann...@google.com>
> wrote:
>> On Sun, Nov 24, 2013 at 11:22 PM, Pawel Veselov <
pawel....@gmail.com>
>> wrote:
>> > This is as pertaining to libvpx-1.2.0
>> I presume you are using VP8
>
> Yes. And out of the box, libvpx-1.2.0 (published by WebM) doesn't have any
> other codecs, right?
That is correct.
>> > bps is ignored, since the only acceptable formats are planar, and not
>> > packed, isn't it?
>> Yes, VP8 supports only planar
>
> So, 'bps' field is ignored then, right?
It is always set to 12 because libvpx only supports I420.
>> > What are X and Y sub-sampling order values?
>
> Could you please clarify those? So far my guess is that it has something to
> do with how chroma information is applied to, or was taken from, the 8
> pixels from the corresponding sampling region.
I'm not sure.
>> > What's the difference between I420/YV12 and VPXI420/VPXYV12?
>> There should be no difference between I420 and VPXI420
>> The difference between I420 and YV12 that I420 has Y, U, V and YV12 has Y,
>> V, U
>
> So, I420 is same as VPXI420, and YV12 is same as VPXYV12. I guess
> application should only use I420 and YV12 format types, as "VPX*" is
> internal to libvpx?
The part of the application which calls libvpx functions must use
vpx_img_fmt_t so that the enum values match.