Skip Menu |

This queue is for tickets about the Linux-DVB-DVBT CPAN distribution.

Report information
The Basics
Id: 50952
Status: resolved
Priority: 0/
Queue: Linux-DVB-DVBT

People
Owner: Nobody in particular
Requestors: cpan [...] mollingtonconsultants.com
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 1.05
Fixed in: (no value)



Subject: dvbt-scan cannot scan using provided format
When I run the provided sample script device_list.pl as:- [root@legolas dvbt]# perl device_list.pl uk-WinterHill I receive the following output:- Conexant CX22702 DVB-T : adaptor number: 0, frontend number: 0 Error: Sorry, I can't set the DVB-T tuner to 754167000 MHz (error code -16) at device_list.pl line 16 When I run the program dvbt_scan with the same filename, I receive the following error:- [root@legolas dvbt]# dvbt-scan uk-WinterHill Setting frequency: 754166670 MHz Error: Sorry, I can't set the DVB-T tuner to 754166670 MHz (error code -16) at /usr/local/bin/dvbt-scan line 43 In both cases, the file I have passed is as follows:- # Winter Hill, North-West England # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 754166670 8MHz 3/4 NONE QAM16 2k 1/32 NONE The correct WinterHill file is actually currently like this:- # UK, Winter Hill # Auto-generated from http://www.dtg.org.uk/retailer/dtt_channels.html # and http://www.ofcom.org.uk/static/reception_advice/index.asp.html # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 754167000 8MHz 3/4 NONE QAM16 2k 1/32 NONE T 834167000 8MHz 2/3 NONE QAM64 2k 1/32 NONE T 850167000 8MHz 2/3 NONE QAM64 2k 1/32 NONE T 842167000 8MHz 3/4 NONE QAM16 2k 1/32 NONE T 786167000 8MHz 3/4 NONE QAM16 2k 1/32 NONE T 810167000 8MHz 3/4 NONE QAM16 2k 1/32 NONE # UK, Winter Hill B T 650000000 8MHz 3/4 NONE QAM16 2k 1/32 NONE T 626000000 8MHz 3/4 NONE QAM16 2k 1/32 NONE ... and I get the same errors reported. I think that there is probably something coded incorrectly in dvb_scan, but my knowledge of C is not up to much, I am afraid.
This is now fixed in 1.06, and I now actually use the value!