<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-text-flowed" style="font-family: -moz-fixed;
font-size: 14px;" lang="x-western">Hi,
<br>
<br>
Alex - thanks again for your reply. I've solved this issue.
<br>
<br>
On 06/07/2011 21:23, Alex Butcher wrote:
<br>
<blockquote type="cite" style="color: #000000;">On Wed, 6 Jul
2011, Nigel Jewell wrote:
<br>
<br>
<blockquote type="cite" style="color: #000000;">Up until about 2
months ago I was able to receive all Freeview channels
<br>
on my MythTV box without any issues using a Hauppage Nova-T
DVB card
<br>
from the Mendip transmitter, however at the end of May I
noticed that
<br>
all channels on a single multiplex were failing to tune.
<br>
</blockquote>
ISTR that coincided with a change in the broadcasting parameters
and/or
<br>
frequencies. A quick Google can't confirm that, however.
<br>
</blockquote>
<br>
I have a script that I run a few times a day that uses dvbscan to
spot new channels and multiplexes (the tuning within MythTV has
never worked for me as it seems to lock onto lower power
transmitters from elsewhere). It compares with what it finds with
the channel and dtv_multiplex tables and emails me any
differences. That way I spot channel changes and multiplex
changes quickly without having to go through the pain of scanning
from within MythTV. It has worked fine for years - you can guess
where this is going <span class="moz-smiley-s1" title=":)"></span>
<br>
<br>
<blockquote type="cite" style="color: #000000;">
<blockquote type="cite" style="color: #000000;">If I plug the
aerial directly into my TV (which also has a Freeview
<br>
tuner) I receive all channels with good quality, so I can
safely assume
<br>
that I should be able to pick it up.
<br>
<br>
Using dvbscan as:
<br>
<br>
/usr/bin/scandvb -u -vvv uk-Mendip
<br>
</blockquote>
The tuning files aren't being kept up-to-date, in my experience.
<br>
</blockquote>
<br>
Agreed. Based upon dvbscan and dvbsnoop I am using the
following. Neither tool reported QAM16 or a 2k mode - and so
whilst they may be listed on ukfree.tv, it isn't what the tools
see.
<br>
<br>
# C54
<br>
T 738000000 8MHz 2/3 1/2 QAM64 8k 1/32 NONE
<br>
# C56+
<br>
T 754167000 8MHz 2/3 1/2 QAM64 8k 1/32 NONE
<br>
# C58
<br>
# .........................................
<br>
# C61
<br>
T 794000000 8MHz 2/3 1/2 QAM64 8k 1/32 NONE
<br>
# C62+
<br>
T 802167000 8MHz 2/3 1/2 QAM64 8k 1/32 NONE
<br>
# C67
<br>
T 842000000 8MHz 2/3 1/2 QAM64 8k 1/32 NONE
<br>
<br>
<blockquote type="cite" style="color: #000000;">
<blockquote type="cite" style="color: #000000;">Any ideas? I'm
not sure where to begin with this as it could be a fault
<br>
of the signal, of the kernel drivers, or of MythTV ... or
maybe my
<br>
channel configuration data ...
<br>
</blockquote>
You will need to adjust the contents of your dtv_multiplex
table.
<br>
</blockquote>
<br>
You're right, and it was the differences you had that pointed me
in the right direction. I had incorrect settings and transport id
for C67. I believe it was the transport id that was causing
tuning to fail.
<br>
<br>
It wasn't picked up by my script because it appears that the DVB
descriptor for that multiplex isn't broadcast with all of the
setup information.
<br>
<br>
I now have the following multiplex entries:
<br>
<br>
mysql> select frequency, bandwidth, hp_code_rate, lp_code_rate,
modulation, transmission_mode, guard_interval, hierarchy,
transportid from dtv_multiplex order by frequency\G
<br>
*************************** 1. row ***************************
<br>
frequency: 738000000
<br>
bandwidth: 8
<br>
hp_code_rate: 2/3
<br>
lp_code_rate: 1/2
<br>
modulation: qam_64
<br>
transmission_mode: 8
<br>
guard_interval: 1/32
<br>
hierarchy: n
<br>
transportid: 8204
<br>
*************************** 2. row ***************************
<br>
frequency: 754167000
<br>
bandwidth: 8
<br>
hp_code_rate: 2/3
<br>
lp_code_rate: 1/2
<br>
modulation: qam_64
<br>
transmission_mode: 8
<br>
guard_interval: 1/32
<br>
hierarchy: n
<br>
transportid: 20544
<br>
*************************** 3. row ***************************
<br>
frequency: 794000000
<br>
bandwidth: 8
<br>
hp_code_rate: 2/3
<br>
lp_code_rate: 1/2
<br>
modulation: qam_64
<br>
transmission_mode: 8
<br>
guard_interval: 1/32
<br>
hierarchy: n
<br>
transportid: 4161
<br>
*************************** 4. row ***************************
<br>
frequency: 802167000
<br>
bandwidth: 8
<br>
hp_code_rate: 2/3
<br>
lp_code_rate: 1/2
<br>
modulation: qam_64
<br>
transmission_mode: 8
<br>
guard_interval: 1/32
<br>
hierarchy: n
<br>
transportid: 12294
<br>
*************************** 5. row ***************************
<br>
frequency: 842000000
<br>
bandwidth: 8
<br>
hp_code_rate: 2/3
<br>
lp_code_rate: 1/2
<br>
modulation: qam_64
<br>
transmission_mode: 8
<br>
guard_interval: 1/32
<br>
hierarchy: n
<br>
transportid: 16514
<br>
5 rows in set (0.00 sec)
<br>
<br>
Thanks again for your reply - your comments were very helpful.
<br>
<br>
Regards,
<br>
Nige.
<br>
</div>
</body>
</html>