[mythtv-users] No EIT Data on Crystal Palace MUX 2

Dave Pearson lists at the-pearsons.co.uk
Wed Jul 28 21:16:47 UTC 2010

On 28/07/10 21:57, Nick Morrott wrote:
> On 28 July 2010 20:07, Dave Pearson<lists at the-pearsons.co.uk>  wrote:
>> I recently rescanned the DVB Channels in my MythTV system and have had a few
>> problems since:
>> Firstly, I couldn't get a lock on any of the Mux 2 Channels, even though the
>> scan detected them. I managed to resolve this by scanning each Transport
>> individually.
>> Unfortunately, I now have a problem getting the EIT Data for the Mux 2
>> channels (all of the other channels are receiving data correctly).
> Using the channel editor in mythtv-setup, check each of the mux #2
> channels and determine whether the "use on-air guide" flag is set for
> them - and enable it if it isn't. As I understand DVB-T, EIT listings
> for all channels are carried on each mux, so the mux 2 channel
> listings should be receivable from the other muxes. EIT is enabled on
> the source and non-mux #2 channels if you are seeing correct listings
> for the other DVB-T channels.
>> Is there any way I can re-initialize the EIT data or force a scan for this
>> MUX?
> I'd also check the 6 muxes in the channel scanner to ensure that each
> mux has a valid networkid and transportid, just to be thorough.
> Cheers,
> Nick
I've got "use on-air guide" set for all of the MUX2 channels, what am I 
looking for for valid networkid and transportid values?


More information about the mythtv-users mailing list