From: Nikolay Dimitrov <picmaster@mail.bg>
To: Ralph Imx <ralph_imx@gmx.co.uk>
Cc: meta-freescale@yoctoproject.org
Subject: Re: Slow frame rates when decoding H264 video
Date: Mon, 10 Nov 2014 18:59:00 +0200 [thread overview]
Message-ID: <5460EED4.8000508@mail.bg> (raw)
In-Reply-To: <trinity-45d9ae24-2616-4bbf-b0ec-1cf9443c1921-1415635422447@3capp-mailcom-bs01>
Hi Ralph,
On 11/10/2014 06:03 PM, Ralph Imx wrote:
> Hi,
> I'm struggling to get my Boundary Devices Nitrgoen6_lite board to decode
> H264 video at the framerate stated in the Freescale i.MX6Solo datasheet.
> It should be able to do 720p60 or 1080p30 video but all I've managed is
> 1080p at 23fps and 720p at 57fps using my own system. I *have* managed
> to reach 720p at 60fps and 1080p at 60fps by using an image using old
> VPU/IPU firmware but this is quite old and deprecated (see
> http://boundarydevices.com/ltib-on-i-mx6-without-x/). At least I know
> that my video clips are correctly encoded to allow decoding at full
> frame rate.
> Interestingly, if I try to decode a 1080p stream but use a 720p screen
> resolution with sync turned off, I can get the decoding going up to
> 43fps. The problem comes when I set the screen resolution to 1080p that
> the frame rate drops to 23fps.
> In addition to my own Linux system, I have created a Linux system
> (using bitbake fsl-image-multimedia-full) from the daisy, dizzy and
> master branches of Yocto but as I say, I can't get the required
> framerate here either. Does anyone know why I can't reach the stated
> specification for this chip of H264 decode using my own build? What
> could be the bottleneck - are there any issues with recent IPU/VPU firmware?
> Thanks.
How do you measure the playback framerate?
Regards,
Nikolay
prev parent reply other threads:[~2014-11-10 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 16:03 Slow frame rates when decoding H264 video Ralph Imx
2014-11-10 16:59 ` Nikolay Dimitrov [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=5460EED4.8000508@mail.bg \
--to=picmaster@mail.bg \
--cc=meta-freescale@yoctoproject.org \
--cc=ralph_imx@gmx.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 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.