<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.24.5">
</HEAD>
<BODY>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
</TD>
</TR>
</TABLE>
<BR>
On Thu, 2009-04-09 at 16:39 -0400, Paul Gallaway wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
> It just occurred to me what you are saying. mplayer is an external program
> tht mythtv calls and is independent to whether mythv has vdpau support or
> not. so as long as i have an mplayer that supports vdpau (which version
> would that be?), i should set the vdpau option for mplayer as long as i am
> running an nvidia driver that suports it?
>
> If so, what are the typical mplayer options that should boost 720p/1080p
> playback?
>
I haven't said anything about VDPAU. If you're using the deb's from
debian-multimedia.org (which I think you said in another post) you
don't have VDPAU support built in. As pointed out in the email from
Johnny you'd need to compile this into Myth using the source from
Jean-Yves which patches VDPAU it into 0.21-fixes. Otherwise you'll
need to install trunk.
Mplayer is an external program. And you are correct it does support
VDPAU but you would again need to build from source to get a version
supporting VDPAU in Lenny (or find another repository that has it).
What I /AM/ saying is that mplayer is an external program and that
mplayer is built using a more recent ffmpeg source with better h.264
support in comparison to the MythTV internal player. As a result I use
mplayer (or VLC) to playback files in mythvideo because I have poor
results with the internal player. Where the internal player fails
mplayer is able to succeed. Try it (did you even try to play the file
from the CLI as I suggested in my previous email?). If it fails then
maybe you need to look into VDPAU but I don't think I'd recommend you
go that route unless you install MythBuntu instead of Debian and use
Jean-Yves repository.
<A HREF="http://www.mythtv.org/wiki/MythVideo#External_Player_Configuration">http://www.mythtv.org/wiki/MythVideo#External_Player_Configuration</A>
Field reports to this list indicate that the Internal player in trunk
is much better as it has had a code refresh (or two) from ffmpeg so
this will be less of an issue in the future.
</PRE>
</BLOCKQUOTE>
<BR>
I think I didn't make myself clear. I was saying that I am thinking it doesn't matter whether the myth I am running is VDPAU or not (at this moment I am not using LiveTV on my myth install). And because I am not using LiveTV, it doesn't matter that mythtv doesn't support VDPAU (maybe unless using the Internal Player for video playback?) because if I use a version of mplayer with VDPAU support, it will be called as an external program and the fact that myth is not VDPAU "enabled" should not matter if I am running a version of mplayer that is.<BR>
<BR>
As I said in another reply I had run the videos in mplayer and they were more sluggish than the myth Internal Player. In fact mplayer was my initial player when I started this thread (which is also stated in the initial mail)<BR>
<BR>
I will be running this system as Debian Testing from tomorrow so hopefully the mplayer I pull from there will play ball as the current one fails with -vo vdpau.
</BODY>
</HTML>