[mythtv-users] UK-Mendip DVB-T multiplex, post 11 January 2011

Alex Butcher mythlist at assursys.co.uk
Mon Jan 24 00:37:33 UTC 2011


Hi -

I'm served by the Mendip transmitter. I rescanned on 18 January as there
were some changes on 11 January (the ArqivaB mplex moved from C59 to C67,
where it'll stay until September 2011, when the SDN mplex will move from C62
to C48, ArqivaA from C56 to C52 and ArqivaB from C67 to C56).

My dtv_multiplex table now looks like this:

mysql> select mplexid,transportid,networkid,frequency,modulation,bandwidth,lp_code_rate,transmission_mode,guard_interval,constellation,hp_code_rate from dtv_multiplex;
+---------+-------------+-----------+-----------+------------+-----------+--------------+-------------------+----------------+---------------+--------------+
| mplexid | transportid | networkid | frequency | modulation | bandwidth | lp_code_rate | transmission_mode | guard_interval | constellation | hp_code_rate |
+---------+-------------+-----------+-----------+------------+-----------+--------------+-------------------+----------------+---------------+--------------+
|      15 |        4161 |      9018 | 794000000 | auto       | a         | auto         | a                 | auto           | auto          | auto         |
|      16 |        8204 |      9018 | 738000000 | qam_64     | 8         | 1/2          | 8                 | 1/32           | qam_64        | 2/3          |
|      17 |       12290 |      9018 | 802166670 | qam_64     | 8         | 1/2          | 2                 | 1/32           | qam_64        | 2/3          |
|      18 |       20480 |      9018 | 754166670 | qam_16     | 8         | 3/4          | 2                 | 1/32           | qam_16        | 3/4          |
|      19 |       24640 |      9018 | 842000000 | auto       | a         | auto         | a                 | auto           | auto          | auto         |
+---------+-------------+-----------+-----------+------------+-----------+--------------+-------------------+----------------+---------------+--------------+
5 rows in set (0.00 sec)

I'm having weird tuning/failed recording problems with a Nova-T-500
card that used to work perfectly before a coincidental rebuild/system
upgrade from Fedora 8/MythTV 0.21-fixes to Fedora 14/MythTV 0.24-fixes.
I'm wondering if the proliferation of 'auto' in some of those columns
may be a factor.

A good recording goes like this in the mythbackend log:

2011-01-22 20:55:01.402 TVRec(1): StartRecording("Journey to the Edge
of the Universe")
2011-01-22 20:55:01.410 TVRec(1): Checking input group recorders -
begin
2011-01-22 20:55:01.419 TVRec(1): Checking input group recorders - done
2011-01-22 20:55:01.458 TVRec(1): StartedRecording(0x7fcfa40c2080)
fn(/srv/myth/video-R1e/recordings/1014_20110122205500.mpg)
2011-01-22 20:55:01.499 TVRec(1): ClearFlags(CancelNextRecording,) ->
RunMainLoop,SignalMonitorRunning,EITScannerRunning,
2011-01-22 20:55:01.531 TVRec(1): ClearFlags(EITScannerRunning,) ->
RunMainLoop,SignalMonitorRunning,
2011-01-22 20:55:01.540 TVRec(1): Changing from None to RecordingOnly
2011-01-22 20:55:01.554 TVRec(1):
ClearFlags(FrontendReady,CancelNextRecording,) ->
RunMainLoop,SignalMonitorRunning,
2011-01-22 20:55:01.563 TVRec(1): HandleTuning Request: Program(yes)
channel() input() flags(Recording,)
2011-01-22 20:55:01.575 TVRec(1): HW Tuner: 1->1
2011-01-22 20:55:01.607 TVRec(1): TeardownSignalMonitor() -- begin
2011-01-22 20:55:01.616 DVBSH(/dev/dvb/adapter1/frontend0):
RemoveListener(0x7fcf6c14a368) -- begin
2011-01-22 20:55:01.624 DVBSH(/dev/dvb/adapter1/frontend0):
RemoveListener(0x7fcf6c14a368) -- locked
2011-01-22 20:55:01.667 DVBSH(/dev/dvb/adapter1/frontend0): RunTS():
shutdown
2011-01-22 20:55:01.674 PIDInfo(/dev/dvb/adapter1/frontend0): Closing
filter for pid 0x0
2011-01-22 20:55:01.689 PIDInfo(/dev/dvb/adapter1/frontend0): Closing
filter for pid 0x10
2011-01-22 20:55:01.697 PIDInfo(/dev/dvb/adapter1/frontend0): Closing
filter for pid 0x11
2011-01-22 20:55:01.706 PIDInfo(/dev/dvb/adapter1/frontend0): Closing
filter for pid 0x12
2011-01-22 20:55:01.716 PIDInfo(/dev/dvb/adapter1/frontend0): Closing
filter for pid 0x14
2011-01-22 20:55:01.724 PIDInfo(/dev/dvb/adapter1/frontend0): Closing
filter for pid 0x12d
2011-01-22 20:55:01.739 PIDInfo(/dev/dvb/adapter1/frontend0): Closing
filter for pid 0x12e
2011-01-22 20:55:01.746 PIDInfo(/dev/dvb/adapter1/frontend0): Closing
filter for pid 0x12f
2011-01-22 20:55:01.754 PIDInfo(/dev/dvb/adapter1/frontend0): Closing
filter for pid 0x130
2011-01-22 20:55:01.766 PIDInfo(/dev/dvb/adapter1/frontend0): Closing
filter for pid 0x3eb
2011-01-22 20:55:01.774 PIDInfo(/dev/dvb/adapter1/frontend0): Closing
filter for pid 0xf02
2011-01-22 20:55:01.784 DVBSH(/dev/dvb/adapter1/frontend0): RunTS():
end
2011-01-22 20:55:01.796 DVBSH(/dev/dvb/adapter1/frontend0):
RemoveListener(0x7fcf6c14a368) -- end
2011-01-22 20:55:01.804 TVRec(1): TeardownSignalMonitor() -- end
2011-01-22 20:55:01.816 TVRec(1): ClearFlags(SignalMonitorRunning,) ->
RunMainLoop,
2011-01-22 20:55:01.824 TVRec(1): ClearFlags(PENDINGACTIONS,) ->
RunMainLoop,
2011-01-22 20:55:01.833 TVRec(1): No recorder yet, calling
TuningFrequency
2011-01-22 20:55:01.847 TVRec(1): Starting Signal Monitor
2011-01-22 20:55:01.855 TVRec(1): SetupSignalMonitor(1, 0)
2011-01-22 20:55:02.218 TVRec(1): Signal monitor successfully created
2011-01-22 20:55:02.242 TVRec(1): Setting up table monitoring.
2011-01-22 20:55:02.242 TVRec(1): SetFlags(SignalMonitorRunning,) ->
RunMainLoop,SignalMonitorRunning,
2011-01-22 20:55:02.256 Using profile 'Live TV' to record
2011-01-22 20:55:02.263 TVRec(1): ClearFlags(WaitingForSignal,) ->
RunMainLoop,SignalMonitorRunning,
2011-01-22 20:55:02.271 TVRec(1): DVB service_id 8442 on net_id 9018
tsid 8204
2011-01-22 20:55:02.284 TVRec(1): SetFlags(WaitingForSignal,) ->
RunMainLoop,WaitingForSignal,SignalMonitorRunning,
2011-01-22 20:55:02.291 TVRec(1): Successfully set up DVB table
monitoring.
2011-01-22 20:55:02.299 TVRec(1): ClearFlags(NeedToStartRecorder,) ->
RunMainLoop,WaitingForSignal,SignalMonitorRunning,
2011-01-22 20:55:02.315 DVBSH(/dev/dvb/adapter1/frontend0):
AddListener(0x7fcf7019f288) -- begin
2011-01-22 20:55:02.318 TVRec(1): SetFlags(NeedToStartRecorder,) ->
RunMainLoop,WaitingForSignal,NeedToStartRecorder,SignalMonitorRunning,
2011-01-22 20:55:02.329 DVBSH(/dev/dvb/adapter1/frontend0):
AddListener(0x7fcf7019f288) -- locked
2011-01-22 20:55:02.363 AutoExpire: CalcParams(): Max required Free
Space: 3.0 GB w/freq: 14 min
2011-01-22 20:55:02.365 DVBSH(/dev/dvb/adapter1/frontend0):
AddListener(0x7fcf7019f288) -- end
2011-01-22 20:55:02.366 DVBSH(/dev/dvb/adapter1/frontend0): RunTS():
begin
2011-01-22 20:55:02.415 PIDInfo(/dev/dvb/adapter1/frontend0): Opening
filter for pid 0x0
2011-01-22 20:55:02.424 PIDInfo(/dev/dvb/adapter1/frontend0): Opening
filter for pid 0x10
2011-01-22 20:55:02.431 PIDInfo(/dev/dvb/adapter1/frontend0): Opening
filter for pid 0x11
2011-01-22 20:55:02.439 PIDInfo(/dev/dvb/adapter1/frontend0): Opening
filter for pid 0x14
2011-01-22 20:55:02.448 CreatePATSingleProgram()
2011-01-22 20:55:02.459 PAT in input stream
2011-01-22 20:55:02.466 Program Association Table
  PSIP tableID(0x0) length(53) extension(0x200c)
       version(2) current(1) section(0) last_section(0)
          tsid: 8204
[...]

A failed recording (with mythfrontend's 'upcoming recordings' showing
it stuck in the 'tuning' state) goes like this:

2011-01-22 21:55:01.219 TVRec(3): StartRecording("Van Wilder")
2011-01-22 21:55:01.228 TVRec(3): Checking input group recorders -
begin
2011-01-22 21:55:01.235 TVRec(3): Checking input group recorders - done
2011-01-22 21:55:01.257 TVRec(3): StartedRecording(0x7fcfa40db440)
fn(/srv/myth/video-R1c/recordings/1024_20110122215500.mpg)
2011-01-22 21:55:01.279 TVRec(3): ClearFlags(CancelNextRecording,) ->
RunMainLoop,
2011-01-22 21:55:01.286 TVRec(3): Changing from None to RecordingOnly
2011-01-22 21:55:01.295 TVRec(3):
ClearFlags(FrontendReady,CancelNextRecording,) -> RunMainLoop,
2011-01-22 21:55:01.304 TVRec(3): HandleTuning Request: Program(yes)
channel() input() flags(Recording,)
2011-01-22 21:55:01.314 TVRec(3): HW Tuner: 3->3
2011-01-22 21:55:01.361 TVRec(3): ClearFlags(PENDINGACTIONS,) ->
RunMainLoop,
2011-01-22 21:55:01.369 TVRec(3): No recorder yet, calling
TuningFrequency
2011-01-22 21:55:01.385 TVRec(3): Starting Signal Monitor
2011-01-22 21:55:01.393 TVRec(3): SetupSignalMonitor(1, 0)
2011-01-22 21:55:01.796 TVRec(3): Signal monitor successfully created
2011-01-22 21:55:01.840 TVRec(3): Setting up table monitoring.
2011-01-22 21:55:01.840 TVRec(3): SetFlags(SignalMonitorRunning,) ->
RunMainLoop,SignalMonitorRunning,
2011-01-22 21:55:01.850 Using profile 'Live TV' to record
2011-01-22 21:55:01.856 TVRec(3): ClearFlags(WaitingForSignal,) ->
RunMainLoop,SignalMonitorRunning,
2011-01-22 21:55:01.876 TVRec(3): SetFlags(WaitingForSignal,) ->
RunMainLoop,WaitingForSignal,SignalMonitorRunning,
2011-01-22 21:55:01.887 TVRec(3): ClearFlags(NeedToStartRecorder,) ->
RunMainLoop,WaitingForSignal,SignalMonitorRunning,
2011-01-22 21:55:01.896 TVRec(3): SetFlags(NeedToStartRecorder,) ->
RunMainLoop,WaitingForSignal,NeedToStartRecorder,SignalMonitorRunning,
2011-01-22 21:55:01.865 TVRec(3): DVB service_id 28032 on net_id 9018
tsid 24640
2011-01-22 21:55:01.917 TVRec(3): Successfully set up DVB table
monitoring.

Note the lack of mention of SignalMonitorRunning in the latter, but the
mention of PENDINGACTIONS. I've also experienced failed recordings on
transportid 4161 (BBCA mplex) too.

I can see from <http://www.ukfree.tv/txdetail.php?a=ST564488> what the
modulation and constellation for transportids 4161 and 24640 should be
(qam_64) and the hp_code_rate (2/3), but what about the bandwidth,
transmission mode (8, for 8k, presumably), guard interval (1/32,
presumably)?

Best Regards,
Alex


More information about the mythtv-users mailing list