From: Gerd Hoffmann <kraxel@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
David Verbeiren <david.verbeiren@intel.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ui/vnc: VA API based H.264 encoding for VNC framebuffer updates
Date: Thu, 10 Jan 2013 07:57:55 +0100 [thread overview]
Message-ID: <50EE6673.8030107@redhat.com> (raw)
In-Reply-To: <5650EBDE-4AAA-407A-829B-648E42B9DBB5@suse.de>
On 01/09/13 23:18, Alexander Graf wrote:
>
> On 09.01.2013, at 21:25, Anthony Liguori wrote:
>
>>
>> Since we really can't guarantee that libva will initialize okay, we
>> need to more gracefully handle falling back to another encoding
>> type.
>
> In fact, doesn't libavcodec / gstreamer support vaapi? If we could
> just send our updates to a library and have that determine whether
> vaapi is available or maybe fall back to software H.264 encoding,
> people without vaapi compatible hardware (or software) could exploit
> this feature too.
Using libavcodec directly is a non-starter as distros don't ship that
due to the multimedia codec patent mess.
gstreamer should be workable, and thanks to the plugin system you can
even use libavcodec indirectly if it happens to be installed (from 3rd
party repo).
cheers,
Gerd
next prev parent reply other threads:[~2013-01-10 6:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 17:27 [Qemu-devel] [PATCH] ui/vnc: VA API based H.264 encoding for VNC framebuffer updates David Verbeiren
2013-01-09 20:25 ` Anthony Liguori
2013-01-09 22:18 ` Alexander Graf
2013-01-10 6:57 ` Gerd Hoffmann [this message]
2013-01-10 10:37 ` Stefano Stabellini
2013-01-10 11:10 ` Gerd Hoffmann
2013-01-10 11:19 ` Alexander Graf
2013-01-10 11:46 ` Gerd Hoffmann
2013-01-10 13:43 ` Verbeiren, David
2013-01-10 15:14 ` Verbeiren, David
2013-01-10 20:15 ` Anthony Liguori
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=50EE6673.8030107@redhat.com \
--to=kraxel@redhat.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=david.verbeiren@intel.com \
--cc=qemu-devel@nongnu.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).