Hi, I'm trying to use mplayer to watch TV and while it does work it has a few problems. 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 problem is. The other is that it hitches when playing TV - it doesn't do this when viewing movies. Has anyone else used mplayer for this? Do you see these problems? Anyone have any suggestions or solutions? The PC is running 5.4 and is an 900Mhz Athlon. The TV card is some generic bktr card with no EEPROM. I have the following in .mplayer/config if anyone is interested. tv=driver=bsdbt848:input=1:norm=PAL:chanlist=australia:channels=2-ABC,7-SAS7,9-NINE,10-TEN,28-SBS It would be nice to iron out this stuff because applying the mplayer post processing filters to TV makes it look much nicer :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20051113/a9507a16/attachment.bin
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 problem > 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 viewing > 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=driver=bsdbt848:input=1:norm=PAL:chanlist=australia:channels=2-ABC,7-SAS7,9-NINE,10-TEN,28-SBSI 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
On Sun, 13 Nov 2005 22:04:48 +1030 "Daniel O'Connor" <doconnor@gsoft.com.au> wrote:> 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 problem > is. > > The other is that it hitches when playing TV - it doesn't do this when viewing > movies.I had a quick look at what has happened to the capture code in mplayer since I last saw it (and felt a bit ill). It seems that it pretty much depends on the frame sync signals from the bktr device with a fallback one second alarm. I know that missing frame sync signals are not uncommon from instrumenting my capture code in ffmpeg which is kept sane by using a tightly timed usleep to capture a frame close ot the right time when the signal is missed. I'm guessing that enabling the audio capture is causing signals to be missed. -- C:>WIN | Directable Mirror Arrays The computer obeys and wins. | A better way to focus the sun You lose and Bill collects. | licences available see | http://www.sohara.org/