From: 'Sakari Ailus' <sakari.ailus@iki.fi>
To: Kamil Debski <k.debski@samsung.com>
Cc: "'Mauro Carvalho Chehab'" <mchehab@redhat.com>,
linux-media@vger.kernel.org,
"'Laurent Pinchart'" <laurent.pinchart@ideasonboard.com>,
"'Sebastian Dröge'" <sebastian.droege@collabora.co.uk>,
"Sylwester Nawrocki" <s.nawrocki@samsung.com>,
"Marek Szyprowski" <m.szyprowski@samsung.com>
Subject: Re: [RFC] Resolution change support in video codecs in v4l2
Date: Fri, 9 Dec 2011 21:58:01 +0200 [thread overview]
Message-ID: <20111209195801.GC1967@valkosipuli.localdomain> (raw)
In-Reply-To: <00f401ccb4d1$12dcda50$38968ef0$%debski@samsung.com>
On Wed, Dec 07, 2011 at 12:12:08PM +0100, Kamil Debski wrote:
>
> > From: Sakari Ailus [mailto:sakari.ailus@iki.fi]
> > Sent: 06 December 2011 23:42
> >
>
> [...]
>
> >
> > > >>>That's a good point. It's more related to changes in stream properties
> > ---
> > > >>>the frame rate of the stream could change, too. That might be when you
> > could
> > > >>>like to have more buffers in the queue. I don't think this is critical
> > > >>>either.
> > > >>>
> > > >>>This could also depend on the properties of the codec. Again, I'd wish
> > a
> > > >>>comment from someone who knows codecs well. Some codecs need to be able
> > to
> > > >>>access buffers which have already been decoded to decode more buffers.
> > Key
> > > >>>frames, simply.
> > > >>
> > > >>Ok, but let's not add unneeded things at the API if you're not sure. If
> > we have
> > > >>such need for a given hardware, then add it. Otherwise, keep it simple.
> > > >
> > > >This is not so much dependent on hardware but on the standards which the
> > > >cdoecs implement.
> > >
> > > Could you please elaborate it? On what scenario this is needed?
> >
> > This is a property of the stream, not a property of the decoder. To
> > reconstruct each frame, a part of the stream is required and already decoded
> > frames may be used to accelerate the decoding. What those parts are. depends
> > on the codec, not a particular implementation.
>
> They are not used to accelerate decoding. They are used to predict what
> should be displayed. If that frame is missing or modified it will cause
> corruption in consecutive frames.
>
> I want to make it clear - they are necessary, not optional to accelerate
> decoding speed.
I think we're talking about the same thing. They are being used to
accelerate it --- instead of reconstructing the previous frame from the
compressed stream, the codecjust reuses it. In practice this is always done
and the implementations probably require it.
--
Sakari Ailus
e-mail: sakari.ailus@iki.fi jabber/XMPP/Gmail: sailus@retiisi.org.uk
prev parent reply other threads:[~2011-12-09 19:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 10:31 [RFC] Resolution change support in video codecs in v4l2 Kamil Debski
2011-12-02 12:35 ` Mauro Carvalho Chehab
2011-12-02 13:57 ` Sakari Ailus
2011-12-02 15:41 ` Kamil Debski
2011-12-02 17:07 ` Mauro Carvalho Chehab
2011-12-02 17:32 ` Kamil Debski
2011-12-02 18:09 ` Mauro Carvalho Chehab
2011-12-06 12:00 ` Laurent Pinchart
2011-12-06 14:28 ` 'Sakari Ailus'
2011-12-06 14:41 ` Mauro Carvalho Chehab
2011-12-06 15:19 ` Kamil Debski
2011-12-06 15:40 ` Mauro Carvalho Chehab
2011-12-06 16:11 ` Kamil Debski
2011-12-06 16:39 ` Mauro Carvalho Chehab
2011-12-07 11:49 ` Kamil Debski
2011-12-10 9:17 ` 'Sakari Ailus'
2011-12-12 11:11 ` Laurent Pinchart
2011-12-03 0:08 ` 'Sakari Ailus'
2011-12-05 13:01 ` Mauro Carvalho Chehab
2011-12-02 16:50 ` Mauro Carvalho Chehab
2011-12-06 14:35 ` Sakari Ailus
2011-12-06 15:03 ` Kamil Debski
2011-12-09 19:54 ` 'Sakari Ailus'
2011-12-12 10:17 ` Kamil Debski
2012-01-01 22:29 ` 'Sakari Ailus'
2012-01-04 10:19 ` Kamil Debski
2012-01-11 22:30 ` 'Sakari Ailus'
2011-12-12 10:59 ` Laurent Pinchart
2011-12-12 11:09 ` Kamil Debski
2011-12-06 16:20 ` Mauro Carvalho Chehab
2011-12-06 22:41 ` Sakari Ailus
2011-12-07 11:12 ` Kamil Debski
2011-12-09 19:58 ` 'Sakari Ailus' [this message]
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=20111209195801.GC1967@valkosipuli.localdomain \
--to=sakari.ailus@iki.fi \
--cc=k.debski@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@redhat.com \
--cc=s.nawrocki@samsung.com \
--cc=sebastian.droege@collabora.co.uk \
/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