[MPlayer-dvb] DVB streaming read failed after running tzap

[Nico Sabbi]

Bruce Ying ha scritto:
> I'm new to this mailing list, so excuse me if I'm posting to the wrong place.
> I'm using a DiBcom USB module on an Ubuntu 11.04 host. The v4l-dvb
> drivers were downloaded via git and built on June 13, 2012.
> Basically, I can watch DVB-T by running mplayer (version
> SVN-r35003-4.5.2); however, if I launched mplayer after running tzap,
> I would get a series of "dvb_streaming_read, attempt N. n failed with
> errno 0 when reading 2048 bytes" failure messages. I must unplug the
> DiBcom USB tuner and plug it in again so that I could relaunch mplayer
> to tune to a DVB-T channel.
>
> The console output of running mplayer as well as tzap is as attached below.
>
> Has anyone experienced the same problem?
>
>
> hying<at>  hying-VT3410-8595CMB:~$ tzap -r -c .tzap/channels.conf CTS
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> reading channels from file '.tzap/channels.conf'
> tuning to 593000000 Hz
> video pid 0x1393, audio pid 0x1394
> status 0f | signal 6322 | snr 008a | ber 001fffff | unc 00000000 |
> status 1f | signal 614f | snr 0098 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 5f5d | snr 0099 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 5fbf | snr 00a1 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 5f9e | snr 009d | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 6027 | snr 009e | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 608d | snr 00a1 | ber 00000000 | unc 00000000 | FE_HAS_LOCK

> status 1f | signal 625e | snr 00a1 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 6127 | snr 009f | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 60ad | snr 00a2 | ber 00000030 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 614f | snr 009e | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 6323 | snr 00a3 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 604d | snr 00a4 | ber 00000030 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 6294 | snr 009f | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1f | signal 60a9 | snr 009d | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> ^C
> hying<at>  hying-VT3410-8595CMB:~$ gmplayer dvb://CTS
> MPlayer SVN-r35003-4.5.2 (C) 2000-2012 MPlayer Team
>
> Playing dvb://CTS.
> dvb_tune Freq: 593000000
> dvb_streaming_read, attempt N. 6 failed with errno 0 when reading 2048 bytes
> dvb_streaming_read, attempt N. 5 failed with errno 0 when reading 2048 bytes
> dvb_streaming_read, attempt N. 4 failed with errno 0 when reading 2048 bytes
> dvb_streaming_read, attempt N. 3 failed with errno 0 when reading 2048 bytes
> dvb_streaming_read, attempt N. 2 failed with errno 0 when reading 2048 bytes
> dvb_streaming_read, attempt N. 1 failed with errno 0 when reading 2048 bytes
> dvb_streaming_read, return 0 bytes
> _______________________________________________
> MPlayer-dvb mailing list
> MPlayer-dvb at mplayerhq.hu
> https://lists.mplayerhq.hu/mailman/listinfo/mplayer-dvb
>

why on earth are you running mplayer dvb://  alongside tzap? there's no 
reason.
tzap is needed to tune the channel and stream its content to the 
appropriare dvr0 device,
mplayer when run with the dvb:// syntax does the same thing so
1) either run only mplayer dvb://
2) or run

tzap -r -c .tzap/channels.conf CTS

and on a different terminal run mplayer<  /dev/dvb/adapter0/dvr0