Robert Schlabbach wrote: > From: "Felix Domke" <tmbinc@xxxxxxxxxxxx> >>Original Network ID (=ONID), ServiceID (=SID) should uniquely identify a >>service. (In reality, it's not so easy, but let us assume it's true). >>every ONID:SID (i.e.: "service", or "service definition") has an >>associated TSID, i.e. the TSID where this service can be found. There >>are no two ONID:SID combinations with different TSIDs. > I think the above is wrong. From ETSI EN 300 468 V1.7.1: > | The combination of original_network_id and transport_stream_id allow > | each TS to be uniquely identified throughout the ETS application area. > | service_id: This is a 16-bit field which uniquely identifies a > | service within a TS. > So it is actually the triple ONID:TSID:SID which uniquely identifies a > service, not just the ONID:SID pair as you wrote. Hm, yes. Looks you're right. I think i've got confused by the fact that some tables only specify a service_id without a tsid, but in these cases, there's always a footnote that the service must be on the same TS. regards, Felix _______________________________________________ linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb