qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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" <qemu-devel@nongnu.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH] ui/vnc: VA API based H.264 encoding for VNC framebuffer updates
Date: Thu, 10 Jan 2013 12:46:33 +0100	[thread overview]
Message-ID: <50EEAA19.8010800@redhat.com> (raw)
In-Reply-To: <0A61D11D-6E10-4866-9EAC-F35A10A93191@suse.de>

On 01/10/13 12:19, Alexander Graf wrote:
> 
> On 10.01.2013, at 12:10, Gerd Hoffmann wrote:
> 
>> On 01/10/13 11:37, Stefano Stabellini wrote:
>>> On Thu, 10 Jan 2013, Gerd Hoffmann wrote:
>>>> On 01/09/13 23:18, Alexander Graf wrote: Using libavcodec
>>>> directly is a non-starter as distros don't ship that due to the
>>>> multimedia codec patent mess.
>>> 
>>> libavcodec is certainly available on my ubuntu and debian
>>> installs.
>> 
>> Full version with H.264 support?  Or stripped down, with patented
>> codecs removed?
> 
> IIRC Ubuntu has full support. Also openSUSE has Packman where you
> could get full libavcodec builds.

Fedora has rpmfusion.  But packages in the distro core can't have direct
dependencies to 3rd party repo packages like
packman/rpmfusion/non-free/whatever-it-is-called-for-your-distro.

> But overall, gstreamer is probably the better interface to look at
> here, as it actually provides a plugin architecture that people can
> plug their almost-legal codecs into.

Exactly.  Taking the indirection via gstreamer plugins allows to build
qemu core distro package with H.264 support enabled.  Actually using
that requires the gstreamer plugins (for libavcodec and/or vaapi) being
installed of course.

cheers,
  Gerd

  reply	other threads:[~2013-01-10 11:46 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
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 [this message]
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=50EEAA19.8010800@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 \
    --cc=stefano.stabellini@eu.citrix.com \
    /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).