[mythtvnz] http://epg.org.nz/freeview.xml.gz

[David Moore]

On 25/03/13 03:08, Stephen Worthington wrote:
> ....
> And this is what happens when I use the AVerMedia tuner:
>
> root at mypvr:~/temp# mhegepgsnoop.py -zp -d /dev/dvb/adapter2/demux0 -v
> -t 3
> [snip]
> Getting tuning info for channel 3
> inversion: 0
> transmission_mode: 8
> guard_interval: 1/16
> hierarchy: n
> hp_code_rate: 3/4
> bandwidth: 8
> frequency: 562000000
> lp_code_rate: 3/4
> constellation: qam_64
>
> Tuning /dev/dvb/adapter2/frontend0 to channel 3
> Frontend name: DiBcom 7000MA/MB/PA/PB/MC
> Frontend type: FE_OFDM
>
> Parameters to be sent to /dev/dvb/adapter2/frontend0:
> Frequency = 562000000
> Inversion = 0 = INVERSION_OFF
> Bandwidth = 0 = BANDWIDTH_8_MHZ
> Transmission mode = 1 = TRANSMISSION_MODE_8K
> HP code rate = 3 = FEC_3_4
> LP code rate = 3 = FEC_3_4
> Constellation = 3 = QAM_64
> Guard interval = 1 = GUARD_INTERVAL_1_16
> Hierarchy = 0 = HIERARCHY_NONE
> Waiting for frontend to lock
> Frontend has lock
>
> Parameters read back from device. Might not be accurate?
> Frequency = 562000000
> Inversion = 2 = INVERSION_AUTO
> list index out of range
> Unable to tune /dev/dvb/adapter2/frontend0 . Exiting
>
> After adding a bit of debug code, I can see that the returned value
> for the Bandwidth parameter (feparams.u.ofdm.bandwidth) is actually
> 8000, so it is well out of range.  Probably a driver bug.
>
>
Looks like they return the bandwidth in kHz instead of a code for 
bandwidth. Not sure if this
is "legal" or not. If it is then I suppose I should update the tuning 
code if/when time permits.