2007-07-27, 06:16 PM
I've just looked at MUX 2 again with TS Reader and it seems to be carrying almost all of the event information for Channel 4. MUX C, on the other hand, is now carrying significantly less information for Channel 4 than it was last night.
I've been reading the ETSI 'Specification for Service Information (SI) in DVB Systems'. It appears that it is only mandatory for a given TS to carry present/following event information for channels it carries. Carrying an EIT for the full schedule for the actual TS is optional as is carrying present/following and/or schedule event information for other transport streams.
sub - when you are harvesting the EPG, do you specifically only look for EIT data for known channels on each individual MUX or do you gather all EIT data on each MUX (ignoring present/following) and then 'clump' it all together?
Cheers,
Brian
I've been reading the ETSI 'Specification for Service Information (SI) in DVB Systems'. It appears that it is only mandatory for a given TS to carry present/following event information for channels it carries. Carrying an EIT for the full schedule for the actual TS is optional as is carrying present/following and/or schedule event information for other transport streams.
sub - when you are harvesting the EPG, do you specifically only look for EIT data for known channels on each individual MUX or do you gather all EIT data on each MUX (ignoring present/following) and then 'clump' it all together?
Cheers,
Brian