On 2005-04-28 at 16:37BST "Simon Baxter" wrote: > > Was mplayer built with dvb support? > No, I just Yummed it (lazy!!) Fine. As an aside: the present way packages are distributed with bits missing is rather tedious ;-) > >> It looks ok : > >> [root@media ~]# /root/bin/tzap -c /root/.tzap/channels.conf -r 'five' > >> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > >> tuning to 561833330 Hz > >> video pid 0x0000, audio pid 0x0caa > >> status 01 | signal 3838 | snr f763 | ber 0000089c | unc 00000000 | > >> status 01 | signal 3939 | snr f763 | ber 0000089c | unc 00000000 | > >> status 1f | signal 3a3a | snr ffd6 | ber 00000029 | unc 00000000 | > >> FE_HAS_LOCK > >> status 1f | signal 3939 | snr ffff | ber 00000000 | unc 0000000b | > >> FE_HAS_LOCK > >> status 1f | signal 3939 | snr ffff | ber 00000000 | unc 00000000 | > >> FE_HAS_LOCK > > > > What happens if you start tzap like that and then > > > > cat /dev/dvb/adapter0/dvr0 > five.ts > > > > ... kill it after a while and then ls -l five.ts to see if > > you got anything? If you did, you can use mencoder to > > convert it to something else (or view the ts with mplayer). > > tzap tune works fine - but I get nothing on a 'cat' either. But presumably if you use the above recipe with one of you "OK" channels, you do get a transport stream in the file? If so, then you can rule out mplayer as a source of the problem altogether. > > no output at all! Anything in /var/log/messages? -- J?n Fairbairn Jon.Fairbairn at cl.cam.ac.uk
