| 1 |
On Fri, Mar 26, 2010 at 8:46 PM, 7v5w7go9ub0o <7v5w7go9ub0o@×××××.com> wrote: |
| 2 |
> On 03/26/10 17:08, Paul Hartman wrote: |
| 3 |
>> |
| 4 |
>> On Fri, Mar 26, 2010 at 10:18 AM, |
| 5 |
>> 7v5w7go9ub0o<7v5w7go9ub0o@×××××.com> wrote: |
| 6 |
>>> |
| 7 |
>>> I'd like to compile ffmpeg with vdpau - direct NVidia hardware |
| 8 |
>>> acceleration. This is a configuration flag for ffmpeg. |
| 9 |
>>> |
| 10 |
>>> Setting the "vdpau" use flag seems to set the configuration flag, |
| 11 |
>>> but also brings in the "x11-libs/libvdpau" libraries which I think |
| 12 |
>>> I do not want, as my NVidia proprietary driver provides these |
| 13 |
>>> libraries. |
| 14 |
>> |
| 15 |
>> AFAIK Nvidia split the vdpau off into libvdpau late last year |
| 16 |
>> sometime. On my system I use both nvidia-drivers and libvdpau without |
| 17 |
>> issue. libvdpau provides libvdpau.so while nvidia-drivers provides |
| 18 |
>> libvdpau_nvidia.so |
| 19 |
>> |
| 20 |
>> Here are my versions: |
| 21 |
>> |
| 22 |
>> x11-libs/libvdpau-0.3-r2 x11-drivers/nvidia-drivers-195.36.15 |
| 23 |
>> |
| 24 |
>> Are you using older versions? I use ~amd64 so maybe if you run stable |
| 25 |
>> it has the older versions. |
| 26 |
>> |
| 27 |
> |
| 28 |
> |
| 29 |
> AHA! THANKS! that explains a lot - including why they made libvdpau |
| 30 |
> ebuild a requirement for ffmpeg. |
| 31 |
> |
| 32 |
> I didn't know that libvdpau ebuild is simply an open-source version of |
| 33 |
> libvdpau.so. (The webpage describes a "wrapper" - duh, what's a wrapper? |
| 34 |
> But I suppose that if libvdpau.so is the first in line, and subsequently |
| 35 |
> loads other "driver" components, then it could be called a wrapper). |
| 36 |
> |
| 37 |
> Portage fell behind the NVidia driver releases a while back - probably |
| 38 |
> before the split you described - so I then started installing drivers |
| 39 |
> directly from NVidia.com, and not portage. |
| 40 |
> |
| 41 |
> (And NVidia continues to bundle libvdpau.so (proprietary?) along with the |
| 42 |
> other components.) |
| 43 |
> |
| 44 |
> So when ffmpeg wanted to add a "wrapper" to the mix, I decided no thanks |
| 45 |
> and started this thread - finally figuring out that I needed to remove |
| 46 |
> the requirement from the ebuild. Having libvdpau.so, everything worked fine. |
| 47 |
> |
| 48 |
> Now that I know what it is, I've installed the libvdpau package and |
| 49 |
> updated the portage NV drivers to current. If portage keeps current I'll |
| 50 |
> use it; if portage again falls behind I should be able to use NVidia.com and |
| 51 |
> ffmpeg will compile either way. |
| 52 |
> |
| 53 |
> Thanks again for your help. |
| 54 |
|
| 55 |
No problem. Also check out x11-misc/vdpauinfo it is a tool that shows |
| 56 |
the vdpau capabilities of your video card/drivers (which codecs & |
| 57 |
mixer features are supported). |
Archives