Skip to main content

Is CDL inband source ID locator method currently supported in 1.1.4-RelB?

3 replies [Last post]
mattsiw
Offline
Joined: 2010-08-03
Points: 0

I am trying to get the frequency, program_number, and modulation from the sourceID passed in the CVT, so I can set up the tune for the download.

I sent the SI table file (Moto_Cert_chmap_4272010) from the Extended channel resource 'flow feed' on the HPNxPro. The SI manager is not parsing all of the tables included in the table file in one shot. The first time I sent the SI table, the SI manager successfully acquired the NIT, the second time, the SVCT, the third time, the NTT.

Do I need an updated SI table file?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
cpratt
Offline
Joined: 2008-12-18
Points: 0

The RI can perform SourceID-based OcapLocator resolution after acquiring the NIT and SVCT tables. This can occur in one pass if the NIT is included ahead of the SVCT. If the SVCT is signaled ahead of the NIT, it will take 2 passes to populate the database. The NTT is only necessary for service_name-based resolution.

I can't speak to how the HPNx PRO signals its tables, but if you can order or loop the tables you might be able to reduce the processing time.

Note that you can tune directly by SourceID and have the RI perform the (f,p,m) resolution - in which case it will hold off your tune until the NIT/SVCT have been acquired.

mattsiw
Offline
Joined: 2010-08-03
Points: 0

>> Note that you can tune directly by SourceID and have the RI perform the (f,p,m) resolution -
>> in which case it will hold off your tune until the NIT/SVCT have been acquired.

What api do I use to tune directly with the sourceID? I do not see anything in mpe_media.h.

cpratt
Offline
Joined: 2008-12-18
Points: 0

All tunes at the native level (MPE/MPEOS) are (frequency, modulation) tunes (with program_number thrown in for some platforms that refuse to tune without it).

The resolving of SourceIDs to (f,m) is done within the stack's Java code prior to initiation of the native tune.