From: Maarten Lankhorst <maarten.lankhorst-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
Cc: "nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: Errors during vdpau mpeg2 decoding
Date: Thu, 04 Sep 2014 07:04:22 +0200 [thread overview]
Message-ID: <5407F2D6.9060509@canonical.com> (raw)
In-Reply-To: <CAKb7UvjMYmt1y+m_uek6vVjA3cHuPTRKKAEicvK3UgghCLOT0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hey,
On 04-09-14 05:53, Ilia Mirkin wrote:
> Hi Maarten,
>
> I'm seeing these prints, which feel like they're accompanied by bad frames:
>
> 0x7f7fcb29ab70 is not a real ref: -0.011 72712/72709 0% 35% 1.0% 0 0
>
> This comes from
>
> if (dec->refs[idx].vidbuf != refs[i]) {
> debug_printf("%p is not a real ref\n", refs[i]);
> // FIXME: Maybe do m2mf copy here if a application really
> depends on it?
> continue;
> }
>
> Can you explain what this means, and what the fixme is referring to?
I keep internal track of the reference frames that were decoded last. If vidbuf in the internal state is not equal to the ref here it means something else got decoded in that slot and we no longer have the intermediary frame used for decoding.
~Maarten
prev parent reply other threads:[~2014-09-04 5:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 3:53 Errors during vdpau mpeg2 decoding Ilia Mirkin
[not found] ` <CAKb7UvjMYmt1y+m_uek6vVjA3cHuPTRKKAEicvK3UgghCLOT0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-04 5:04 ` Maarten Lankhorst [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=5407F2D6.9060509@canonical.com \
--to=maarten.lankhorst-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
--cc=imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.