Date: Sun, 13 Nov 2005 15:30:24 +0100 From: Miguel Mendez <mmendez@gmail.com> To: Daniel O'Connor <doconnor@gsoft.com.au> Cc: freebsd-stable@freebsd.org Subject: Re: mplayer + bktr Message-ID: <c6c533210511130630n796e8020x30ddd494dfc7f0fb@mail.gmail.com> In-Reply-To: <200511132204.55664.doconnor@gsoft.com.au> References: <200511132204.55664.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi there,
> The first is that when you force it to capture audio (so mute and volume
> control work, or you can use mencoder) it does about 0.25 fps :( It doesn=
't
> appear to be using heaps of CPU or anything so I am not sure what the pro=
blem
> is.
I haven't tried this yet but can give it a go.
> The other is that it hitches when playing TV - it doesn't do this when vi=
ewing
> movies.
After trying to figure out why tv support wasn't there I've added the
" --enable-tv-bsdbt848" to the configure args and it's warking
flawlessly on my AMD64 box. This is 0.99.7_6. The output is crystal
clear here.
> Has anyone else used mplayer for this? Do you see these problems? Anyone
> have any suggestions or solutions?
Have you tried with xawtv and fxtv? Does the problem only show with
mplayer? What other build options did you enable when building the
software?
>tv=3Ddriver=3Dbsdbt848:input=3D1:norm=3DPAL:chanlist=3Daustralia:channels=
=3D2-ABC,7-SAS7,9-NINE,10-TEN,28-SBS
I have a similar config except set for Europe.
> It would be nice to iron out this stuff because applying the mplayer post
> processing filters to TV makes it look much nicer :)
Yes, it rocks. I've been using xawtv for a month and mplayer is so
much better. :)
Cheers,
--
Miguel Mendez <mmendez@gmail.com>
http://energyhq.blogspot.com
PGP Key: 0xDC8514F1
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c6c533210511130630n796e8020x30ddd494dfc7f0fb>