Mailing List Archive: atrpms: users

New MPlayer and FFmpeg Packages?

Index | Next | Previous | View Threaded

jrw3319 at gmail

Mar 10, 2009, 3:00 PM

Post #1 of 13 (2379 views)
Permalink

New MPlayer and FFmpeg Packages?

Not to sound pushy or anything, but any chance that there are new,
VDPAU capable packages forthcoming for MPlayer and FFmpeg? "Official"
support for VDPAU was announced over on the MPlayer site at the end of
February, and while there was some discussion around that time here on
the list about a new package being released in the ATrpms repo it
apparently never came about. As far as FFmpeg, I know there is a
fairly current version in the repos, and I honestly don't know whether
it supports VDPAU or not, but since there was a new version released
today (0.5) and it is closely tied to MPlayer I figured I would ask.

Thanks,
John

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

jrw3319 at gmail

Mar 17, 2009, 10:53 AM

Post #2 of 13 (2287 views)
Permalink

Re: New MPlayer and FFmpeg Packages? [In reply to]

On Tue, Mar 10, 2009 at 6:00 PM, John Welch <jrw3319 [at] gmail> wrote:
> Not to sound pushy or anything, but any chance that there are new,
> VDPAU capable packages forthcoming for MPlayer and FFmpeg? "Official"
> support for VDPAU was announced over on the MPlayer site at the end of
> February, and while there was some discussion around that time here on
> the list about a new package being released in the ATrpms repo it
> apparently never came about. As far as FFmpeg, I know there is a
> fairly current version in the repos, and I honestly don't know whether
> it supports VDPAU or not, but since there was a new version released
> today (0.5) and it is closely tied to MPlayer I figured I would ask.
>
> Thanks,
> John
>

Just wanted to say thanks for the new mplayer and ffmpeg packages.

John

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

atrpms at duncb

Mar 17, 2009, 3:02 PM

Post #3 of 13 (2289 views)
Permalink

Re: New MPlayer and FFmpeg Packages? [In reply to]

John Welch wrote:
> On Tue, Mar 10, 2009 at 6:00 PM, John Welch <jrw3319 [at] gmail> wrote:
>
>> Not to sound pushy or anything, but any chance that there are new,
>> VDPAU capable packages forthcoming for MPlayer and FFmpeg? "Official"
>> support for VDPAU was announced over on the MPlayer site at the end of
>> February, and while there was some discussion around that time here on
>> the list about a new package being released in the ATrpms repo it
>> apparently never came about. As far as FFmpeg, I know there is a
>> fairly current version in the repos, and I honestly don't know whether
>> it supports VDPAU or not, but since there was a new version released
>> today (0.5) and it is closely tied to MPlayer I figured I would ask.
>>
>> Thanks,
>> John
>>
>>
>
> Just wanted to say thanks for the new mplayer and ffmpeg packages.
>
> John
>
>
Hi John

Is vdpau working for you in these builds? I'm getting:

Error opening/initializing the selected video_out (-vo) device.

I cant see any specific VDPAU config options in the .spec, so maybe the
autodetection failed?

Do you have the build logs Axel?

Cheers

Dunc

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

atrpms at duncb

Mar 17, 2009, 4:05 PM

Post #4 of 13 (2285 views)
Permalink

Re: New MPlayer and FFmpeg Packages? [In reply to]

Dunc wrote:
> I cant see any specific VDPAU config options in the .spec, so maybe the
> autodetection failed?
>
>
>
Looks like this is the case:

> ldd /usr/bin/mplayer |grep vdpau
returns no results. It should be showing something like
> libvdpau.so.1 => /usr/lib64/nvidia-graphics-180.29/libvdpau.so.1
> (0x0000003454e00000)
In order for my compilation of mplayer to detect vdpau with the atrpms
nvidia packages, I had to include these config options:

--with-extraincdir=/usr/include/nvidia-graphics-180.29/
--with-extralibdir=/usr/lib64/nvidia-graphics-180.29/

Although it would suggest this would tie it to a specific driver
version, it carried on working fine after I had moved up to 180.35

Dunc

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

promac at gmail

Mar 17, 2009, 6:24 PM

Post #5 of 13 (2275 views)
Permalink

Re: New MPlayer and FFmpeg Packages? [In reply to]

On Tue, Mar 17, 2009 at 8:05 PM, Dunc <atrpms [at] duncb> wrote:

> Dunc wrote:
> > I cant see any specific VDPAU config options in the .spec, so maybe the
> > autodetection failed?
> >
> >
> >
> Looks like this is the case:
>
> > ldd /usr/bin/mplayer |grep vdpau
> returns no results. It should be showing something like
> > libvdpau.so.1 => /usr/lib64/nvidia-graphics-180.29/libvdpau.so.1
> > (0x0000003454e00000)
> In order for my compilation of mplayer to detect vdpau with the atrpms
> nvidia packages, I had to include these config options:
>
> --with-extraincdir=/usr/include/nvidia-graphics-180.29/
> --with-extralibdir=/usr/lib64/nvidia-graphics-180.29/
>
> Although it would suggest this would tie it to a specific driver
> version, it carried on working fine after I had moved up to 180.35
>

Axel, there is a missing "%" in the line below:

--with-extraincdir=%{_includedir}/nvidia-graphics{?with_xvmcw::%{_includedir}/directfb}
\

This is the correct form:

--with-extraincdir=%{_includedir}/nvidia-graphics%{?with_xvmcw::%{_includedir}/directfb}
\

--
Paulo Roma Cavalcanti
LCG - UFRJ

promac at gmail

Mar 18, 2009, 5:46 AM

Post #6 of 13 (2261 views)
Permalink

Re: New MPlayer and FFmpeg Packages? [In reply to]

On Tue, Mar 17, 2009 at 10:24 PM, Paulo Cavalcanti <promac [at] gmail> wrote:

>
>
> On Tue, Mar 17, 2009 at 8:05 PM, Dunc <atrpms [at] duncb> wrote:
>
>> Dunc wrote:
>> > I cant see any specific VDPAU config options in the .spec, so maybe the
>> > autodetection failed?
>> >
>> >
>> >
>> Looks like this is the case:
>>
>> > ldd /usr/bin/mplayer |grep vdpau
>> returns no results. It should be showing something like
>> > libvdpau.so.1 => /usr/lib64/nvidia-graphics-180.29/libvdpau.so.1
>> > (0x0000003454e00000)
>> In order for my compilation of mplayer to detect vdpau with the atrpms
>> nvidia packages, I had to include these config options:
>>
>> --with-extraincdir=/usr/include/nvidia-graphics-180.29/
>> --with-extralibdir=/usr/lib64/nvidia-graphics-180.29/
>>
>> Although it would suggest this would tie it to a specific driver
>> version, it carried on working fine after I had moved up to 180.35
>>
>
> Axel, there is a missing "%" in the line below:
>
> --with-extraincdir=%{_includedir}/nvidia-graphics{?with_xvmcw::%{_includedir}/directfb}
> \
>
>
> This is the correct form:
>
> --with-extraincdir=%{_includedir}/nvidia-graphics%{?with_xvmcw::%{_includedir}/directfb}
> \
>
>
I rebuilt mplayer and it has vdpau support now. The problem is that
it does not work with xinerama. Since I do use my LCD plus
a TV, the xinerama module is loaded anyaway.

Then I rebuilt all the packages for F8 for running on a computer with
a single display, and it worked just fine.

Therefore, I think some work is still to be done on the nividia side,
because it is common for people using mythtv, to have two displays
in a twin view configuration.

If anyone has a solution for this problem, please, let me know.

--
Paulo Roma Cavalcanti
LCG - UFRJ

Axel.Thimm at ATrpms

Mar 21, 2009, 2:03 AM

Post #7 of 13 (2215 views)
Permalink

Re: New MPlayer and FFmpeg Packages? [In reply to]

Hi,

On Tue, Mar 17, 2009 at 10:24:37PM -0300, Paulo Cavalcanti wrote:
> On Tue, Mar 17, 2009 at 8:05 PM, Dunc <atrpms [at] duncb> wrote:
> > Dunc wrote:
> > > I cant see any specific VDPAU config options in the .spec, so maybe the
> > > autodetection failed?

You were probably looking at the specfile on www.atrpms.net which is
updated later than dl.atrpms.net.

> Axel, there is a missing "%" in the line below:
>
> --with-extraincdir=%{_includedir}/nvidia-graphics{?with_xvmcw::%{_includedir}/directfb}
> \
>
>
> This is the correct form:
>
> --with-extraincdir=%{_includedir}/nvidia-graphics%{?with_xvmcw::%{_includedir}/directfb}
> \

Thanks for the catch!
--
Axel.Thimm at ATrpms.net

promac at gmail

Mar 21, 2009, 5:15 AM

Post #8 of 13 (2209 views)
Permalink

Re: New MPlayer and FFmpeg Packages? [In reply to]

On Wed, Mar 18, 2009 at 9:46 AM, Paulo Cavalcanti <promac [at] gmail> wrote:

>
>
> On Tue, Mar 17, 2009 at 10:24 PM, Paulo Cavalcanti <promac [at] gmail>wrote:
>
>>
>>
>> On Tue, Mar 17, 2009 at 8:05 PM, Dunc <atrpms [at] duncb> wrote:
>>
>>> Dunc wrote:
>>> > I cant see any specific VDPAU config options in the .spec, so maybe the
>>> > autodetection failed?
>>> >
>>> >
>>> >
>>> Looks like this is the case:
>>>
>>> > ldd /usr/bin/mplayer |grep vdpau
>>> returns no results. It should be showing something like
>>> > libvdpau.so.1 => /usr/lib64/nvidia-graphics-180.29/libvdpau.so.1
>>> > (0x0000003454e00000)
>>> In order for my compilation of mplayer to detect vdpau with the atrpms
>>> nvidia packages, I had to include these config options:
>>>
>>> --with-extraincdir=/usr/include/nvidia-graphics-180.29/
>>> --with-extralibdir=/usr/lib64/nvidia-graphics-180.29/
>>>
>>> Although it would suggest this would tie it to a specific driver
>>> version, it carried on working fine after I had moved up to 180.35
>>>
>>
>> Axel, there is a missing "%" in the line below:
>>
>> --with-extraincdir=%{_includedir}/nvidia-graphics{?with_xvmcw::%{_includedir}/directfb}
>> \
>>
>>
>> This is the correct form:
>>
>> --with-extraincdir=%{_includedir}/nvidia-graphics%{?with_xvmcw::%{_includedir}/directfb}
>> \
>>
>>
> I rebuilt mplayer and it has vdpau support now. The problem is that
> it does not work with xinerama. Since I do use my LCD plus
> a TV, the xinerama module is loaded anyaway.
>
> Then I rebuilt all the packages for F8 for running on a computer with
> a single display, and it worked just fine.
>
> Therefore, I think some work is still to be done on the nividia side,
> because it is common for people using mythtv, to have two displays
> in a twin view configuration.
>
> If anyone has a solution for this problem, please, let me know.
>

In fact, I am not sure if this issue persists or not. It was true in the
past,
but maybe it has been already fixed.

The problem here is that the cards connected to my TVs are GeForce 7600 GT,
which does not support vdpau.

The ones which have worked in F8 are a Geforce 8500 GT and a 8400M GS.

--
Paulo Roma Cavalcanti
LCG - UFRJ

atrpms at duncb

Mar 22, 2009, 12:31 PM

Post #9 of 13 (2192 views)
Permalink

Re: New MPlayer and FFmpeg Packages? [In reply to]

Axel Thimm wrote:
> Hi,
>
> On Tue, Mar 17, 2009 at 10:24:37PM -0300, Paulo Cavalcanti wrote:
>
>> On Tue, Mar 17, 2009 at 8:05 PM, Dunc <atrpms [at] duncb> wrote:
>>
>>> Dunc wrote:
>>>
>>>> I cant see any specific VDPAU config options in the .spec, so maybe the
>>>> autodetection failed?
>>>>
>
> You were probably looking at the specfile on www.atrpms.net which is
> updated later than dl.atrpms.net.
>
>
>> Axel, there is a missing "%" in the line below:
>>
>> --with-extraincdir=%{_includedir}/nvidia-graphics{?with_xvmcw::%{_includedir}/directfb}
>> \
>>
>>
>> This is the correct form:
>>
>> --with-extraincdir=%{_includedir}/nvidia-graphics%{?with_xvmcw::%{_includedir}/directfb}
>> \
>>
>
> Thanks for the catch!
Upgraded this morning and all looks good, everything works as expected,
and linked properly.

One thing I was wondering though, when I tried to --rebuild myself, it
failed to find the vdpau stuff. In the spec it uses

--with-extralibdir=%{_libdir}/nvidia-graphics

Yet on my system every lib directory is in the form nvidia-graphics-180.x

Also it has the requirement nvidia-graphics-devel, but again I only have
nvidia-graphics-devel-180.x

Are you using macros to get around this or am I missing something?

Although I've been bulding packages myself for a few years now, its very
trial and error, and I never really seem to know what I'm doing! So this
is more learning curiosity than anything else

Many thanks for all the great work

Dunc

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

promac at gmail

Mar 22, 2009, 1:43 PM

Post #10 of 13 (2188 views)
Permalink

Re: New MPlayer and FFmpeg Packages? [In reply to]

On Sun, Mar 22, 2009 at 4:31 PM, Dunc <atrpms [at] duncb> wrote:

> Axel Thimm wrote:
> > Hi,
> >
> > On Tue, Mar 17, 2009 at 10:24:37PM -0300, Paulo Cavalcanti wrote:
> >
> >> On Tue, Mar 17, 2009 at 8:05 PM, Dunc <atrpms [at] duncb> wrote:
> >>
> >>> Dunc wrote:
> >>>
> >>>> I cant see any specific VDPAU config options in the .spec, so maybe
> the
> >>>> autodetection failed?
> >>>>
> >
> > You were probably looking at the specfile on www.atrpms.net which is
> > updated later than dl.atrpms.net.
> >
> >
> >> Axel, there is a missing "%" in the line below:
> >>
> >>
> --with-extraincdir=%{_includedir}/nvidia-graphics{?with_xvmcw::%{_includedir}/directfb}
> >> \
> >>
> >>
> >> This is the correct form:
> >>
> >>
> --with-extraincdir=%{_includedir}/nvidia-graphics%{?with_xvmcw::%{_includedir}/directfb}
> >> \
> >>
> >
> > Thanks for the catch!
> Upgraded this morning and all looks good, everything works as expected,
> and linked properly.
>
> One thing I was wondering though, when I tried to --rebuild myself, it
> failed to find the vdpau stuff. In the spec it uses
>
> --with-extralibdir=%{_libdir}/nvidia-graphics
>
> Yet on my system every lib directory is in the form nvidia-graphics-180.x
>
> Also it has the requirement nvidia-graphics-devel, but again I only have
> nvidia-graphics-devel-180.x
>
> Are you using macros to get around this or am I missing something?
>
> Although I've been bulding packages myself for a few years now, its very
> trial and error, and I never really seem to know what I'm doing! So this
> is more learning curiosity than anything else
>
> Many thanks for all the great work
>

You need

nvidia-graphics-devel-180.29-36.x86_64.rpm

This package creates the needed symbolic links:

/usr/lib64/nvidia-graphics -> nvidia-graphics-180.29

/usr/include/nvidia-graphics -> nvidia-graphics-180.29

--
Paulo Roma Cavalcanti
LCG - UFRJ

atrpms at duncb

Mar 22, 2009, 2:18 PM

Post #11 of 13 (2185 views)
Permalink

Re: New MPlayer and FFmpeg Packages? [In reply to]

Paulo Cavalcanti wrote:
>
> You need
>
> nvidia-graphics-devel-180.29-36.x86_64.rpm
>
> This package creates the needed symbolic links:
>
> /usr/lib64/nvidia-graphics -> nvidia-graphics-180.29
>
> /usr/include/nvidia-graphics -> nvidia-graphics-180.29
>
> --
> Paulo Roma Cavalcanti
> LCG - UFRJ

Ah I see, didnt realise there was 2 devel packages..

What's the reasoning behind having 2 packages, as I now have

nvidia-graphics180.29-devel-180.29-107.fc10.x86_64 and
nvidia-graphics-devel-180.29-36.x86_64 installed

The symlinks are there now of course and at least the spec makes sense ;)

Dunc

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

Axel.Thimm at ATrpms

Mar 24, 2009, 9:56 AM

Post #12 of 13 (2135 views)
Permalink

Re: New MPlayer and FFmpeg Packages? [In reply to]

Hi,

On Sun, Mar 22, 2009 at 09:18:48PM +0000, Dunc wrote:
> Paulo Cavalcanti wrote:
> >
> > You need
> >
> > nvidia-graphics-devel-180.29-36.x86_64.rpm
> >
> > This package creates the needed symbolic links:
> >
> > /usr/lib64/nvidia-graphics -> nvidia-graphics-180.29
> >
> > /usr/include/nvidia-graphics -> nvidia-graphics-180.29
> >
>
> Ah I see, didnt realise there was 2 devel packages..
>
> What's the reasoning behind having 2 packages, as I now have

The one is a fake package selecting the proper one. The nvidia
packages are multi-install capable and the recent developments show
why - some drivers work better for 3D games, others for PVR etc. So
everyone can pick their own best driver and driver development.

nvidia-graphics-devel justs sets the default one for "stable" and
there is also another nvidia-graphics-devel in "bleeding" activating
the latest and not-yet-stable-tagged nvidia driver development libs.

For example if you need vdpau development libs you will need the
"bleeding" version.

> nvidia-graphics180.29-devel-180.29-107.fc10.x86_64 and
> nvidia-graphics-devel-180.29-36.x86_64 installed
>
> The symlinks are there now of course and at least the spec makes sense ;)

--
Axel.Thimm at ATrpms.net

atrpms at duncb

Mar 24, 2009, 2:20 PM

Post #13 of 13 (2129 views)
Permalink

Re: New MPlayer and FFmpeg Packages? [In reply to]

Axel Thimm wrote:
>> Ah I see, didnt realise there was 2 devel packages..
>>
>> What's the reasoning behind having 2 packages, as I now have
>>
>
> The one is a fake package selecting the proper one. The nvidia
> packages are multi-install capable and the recent developments show
> why - some drivers work better for 3D games, others for PVR etc. So
> everyone can pick their own best driver and driver development.
>
> nvidia-graphics-devel justs sets the default one for "stable" and
> there is also another nvidia-graphics-devel in "bleeding" activating
> the latest and not-yet-stable-tagged nvidia driver development libs.
>
> For example if you need vdpau development libs you will need the
> "bleeding" version.
>
>
I understand,

thanks for the explanation!

Dunc

_______________________________________________
atrpms-users mailing list
atrpms-users [at] atrpms
http://lists.atrpms.net/mailman/listinfo/atrpms-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads