On 10/01/12 13:54, Steven Toth wrote:
The Nanostick works fine for between 5 and 25 minutes and then without any
error messages cuts out. The TS drops to a tiny stream of non-TS data. It
seems to contain a lot of 0x00s and 0xffs.
What does femon show for demodulator statistics?
Well... I downloaded the latest dvb-apps via mecurial from linuxtv.org
and the following happened at the start while it was working:
status SCVYL | signal ffff | snr 00ef | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status SCVYL | signal ffff | snr 00f1 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status SCVYL | signal ffff | snr 00ee | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status SCVYL | signal ffff | snr 00f0 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status SCVYL | signal ffff | snr 00f2 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status SCVYL | signal ffff | snr 00ee | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status SCVYL | signal ffff | snr 00f0 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
and when it stopped working, this time an hour later, nothing had
changed. In fact, it looks like the driver keeps lock even when it's not
recording at all.
Any ideas anyone? Looks like the tuner is OK....
The thing that's really confusing me is the totally random amounts of
time it takes before it fails. This time it was over an hour. For
reference though this was the first time I'd tried it with standard
definition transmissions. Not only lower data rate but also DVB-T rather
than DVB-T2.
Many thanks,
Jim.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
