From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: libvdpau (?)
Date: Sun, 28 Mar 2010 15:52:51 -0500 [thread overview]
Message-ID: <58965d8a1003281352n3c1580b8k118debf0922cc0b6@mail.gmail.com> (raw)
In-Reply-To: <4BAD6389.4070801@gmail.com>
On Fri, Mar 26, 2010 at 8:46 PM, 7v5w7go9ub0o <7v5w7go9ub0o@gmail.com> wrote:
> On 03/26/10 17:08, Paul Hartman wrote:
>>
>> On Fri, Mar 26, 2010 at 10:18 AM,
>> 7v5w7go9ub0o<7v5w7go9ub0o@gmail.com> wrote:
>>>
>>> I'd like to compile ffmpeg with vdpau - direct NVidia hardware
>>> acceleration. This is a configuration flag for ffmpeg.
>>>
>>> Setting the "vdpau" use flag seems to set the configuration flag,
>>> but also brings in the "x11-libs/libvdpau" libraries which I think
>>> I do not want, as my NVidia proprietary driver provides these
>>> libraries.
>>
>> AFAIK Nvidia split the vdpau off into libvdpau late last year
>> sometime. On my system I use both nvidia-drivers and libvdpau without
>> issue. libvdpau provides libvdpau.so while nvidia-drivers provides
>> libvdpau_nvidia.so
>>
>> Here are my versions:
>>
>> x11-libs/libvdpau-0.3-r2 x11-drivers/nvidia-drivers-195.36.15
>>
>> Are you using older versions? I use ~amd64 so maybe if you run stable
>> it has the older versions.
>>
>
>
> AHA! THANKS! that explains a lot - including why they made libvdpau
> ebuild a requirement for ffmpeg.
>
> I didn't know that libvdpau ebuild is simply an open-source version of
> libvdpau.so. (The webpage describes a "wrapper" - duh, what's a wrapper?
> But I suppose that if libvdpau.so is the first in line, and subsequently
> loads other "driver" components, then it could be called a wrapper).
>
> Portage fell behind the NVidia driver releases a while back - probably
> before the split you described - so I then started installing drivers
> directly from NVidia.com, and not portage.
>
> (And NVidia continues to bundle libvdpau.so (proprietary?) along with the
> other components.)
>
> So when ffmpeg wanted to add a "wrapper" to the mix, I decided no thanks
> and started this thread - finally figuring out that I needed to remove
> the requirement from the ebuild. Having libvdpau.so, everything worked fine.
>
> Now that I know what it is, I've installed the libvdpau package and
> updated the portage NV drivers to current. If portage keeps current I'll
> use it; if portage again falls behind I should be able to use NVidia.com and
> ffmpeg will compile either way.
>
> Thanks again for your help.
No problem. Also check out x11-misc/vdpauinfo it is a tool that shows
the vdpau capabilities of your video card/drivers (which codecs &
mixer features are supported).
prev parent reply other threads:[~2010-03-28 20:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 15:18 [gentoo-user] libvdpau (?) 7v5w7go9ub0o
2010-03-26 17:25 ` Kaddeh
2010-03-26 19:31 ` [gentoo-user] " 7v5w7go9ub0o
2010-03-26 18:29 ` [gentoo-user] " Alex Kuster
2010-03-26 19:36 ` [gentoo-user] " 7v5w7go9ub0o
2010-03-26 20:02 ` 7v5w7go9ub0o
2010-03-26 21:13 ` Neil Walker
2010-03-28 16:33 ` [gentoo-user] " Neil Bothwick
2010-03-26 21:08 ` Paul Hartman
2010-03-27 1:46 ` [gentoo-user] " 7v5w7go9ub0o
2010-03-27 10:46 ` Peter Humphrey
2010-03-28 20:52 ` Paul Hartman [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=58965d8a1003281352n3c1580b8k118debf0922cc0b6@mail.gmail.com \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.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