linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Figa <tfiga@chromium.org>
To: Ezequiel Garcia <ezequiel@collabora.com>
Cc: Nicolas Dufresne <nicolas@ndufresne.ca>,
	Alexandre Courbot <acourbot@chromium.org>,
	Pawel Osciak <posciak@chromium.org>,
	DVB_Linux_Media <linux-media@vger.kernel.org>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	kernel@collabora.com
Subject: Re: [RFC] media: uapi: Add VP8 low-level decoder API compound controls.
Date: Mon, 25 Feb 2019 14:34:45 +0900	[thread overview]
Message-ID: <CAAFQd5CQDy4+eWEDpMhdO=ySPN6y__WmTm3PAsVFukO7Sm-dXg@mail.gmail.com> (raw)
In-Reply-To: <4812f69e53d1313678d0c54577793362e6d7ad2e.camel@collabora.com>

On Fri, Feb 15, 2019 at 9:06 AM Ezequiel Garcia <ezequiel@collabora.com> wrote:
>
> On Wed, 2019-02-13 at 21:35 -0500, Nicolas Dufresne wrote:
> > Le mer. 13 févr. 2019 à 16:23, Ezequiel Garcia
> > <ezequiel@collabora.com> a écrit :
> > > Hi,
> > >
> > > On Wed, 2019-02-13 at 18:15 -0300, Ezequiel Garcia wrote:
[snip]
> > > > +     __u8 version;
> > > > +
> > > > +     /* Populated also if not a key frame */
> > > > +     __u16 width;
> > > > +     __u16 height;
> > > > +     __u8 horizontal_scale;
> > > > +     __u8 vertical_scale;
> > > > +
> > > > +     struct v4l2_vp8_segment_header segment_header;
> > > > +     struct v4l2_vp8_loopfilter_header lf_header;
> > > > +     struct v4l2_vp8_quantization_header quant_header;
> > > > +     struct v4l2_vp8_entropy_header entropy_header;
> > > > +
> > > > +     __u8 sign_bias_golden;
> > > > +     __u8 sign_bias_alternate;
> > > > +
> > > > +     __u8 prob_skip_false;
> > > > +     __u8 prob_intra;
> > > > +     __u8 prob_last;
> > > > +     __u8 prob_gf;
> > > > +
> > > > +     __u32 first_part_size;
> > > > +     __u32 first_part_offset; // this needed? it's always 3 + 7 * s->keyframe;
> > >
> > > As the comment says, it seems the first partition offset is always
> > > 3 + 7 * s->keyframe. Or am I wrong?
> >
> > I can't find it in VA API or GStreamer parsers. Ideally we need to
> > look in the spec, if it's calculated it does not belong here.
> >
>
> Looking into the spec, I don't think it's part of it.
>
> > https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/blob/master/gst-libs/gst/codecparsers/gstvp8parser.h#L255
> > https://github.com/intel/libva/blob/master/va/va_dec_vp8.h#L72
> >
> > Notice that VA splits this in two, the some part in the picture
> > parameter, and some parts as SliceParameters. I believe it's to avoid
> > having conditional field base on if key_frame == 0.
> >
>
> That might make sense. Something to look into.

Yeah, sounds reasonable, although VAAPI naming is a bit off, since VP8
doesn't have a notion of slices...

Best regards,
Tomasz

  reply	other threads:[~2019-02-25  5:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13 21:15 [RFC] media: uapi: Add VP8 low-level decoder API compound controls Ezequiel Garcia
2019-02-13 21:22 ` Ezequiel Garcia
2019-02-14  2:35   ` Nicolas Dufresne
2019-02-15  0:06     ` Ezequiel Garcia
2019-02-25  5:34       ` Tomasz Figa [this message]
2019-05-16 17:51         ` Nicolas Dufresne
2019-05-16 18:11 ` Nicolas Dufresne
2019-06-27  9:33 ` Paul Kocialkowski
2019-06-27 18:57   ` Ezequiel Garcia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAAFQd5CQDy4+eWEDpMhdO=ySPN6y__WmTm3PAsVFukO7Sm-dXg@mail.gmail.com' \
    --to=tfiga@chromium.org \
    --cc=acourbot@chromium.org \
    --cc=ezequiel@collabora.com \
    --cc=hans.verkuil@cisco.com \
    --cc=kernel@collabora.com \
    --cc=linux-media@vger.kernel.org \
    --cc=nicolas@ndufresne.ca \
    --cc=posciak@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).