![]() ![]() ![]() |
|
giggles: It appears from the logs provided that you also didn't run the two versions at the same time. 1.0.8 was run before 1.0.15 (see timestamps).
Again, half way through the second run (1.0.15) the version information changes (see '20:05:45:090 DII Message version change - removing modules') and the collector starts collecting the blocks again. If both versions had run simultaneously I would expect the same to occur in 1.0.8 (as Steve said - no collection code changed).
DSMCC / MHEG5 standards provide for the source transmission to issue updates and change the DSMCC version number accordingly. Thus we need to re-read the data blocks.
BTW - running this test at the top of the hour is a bad time anyway as this is when the change is MOST likely to occur. Eg. One program finishes, EPG updates with the next program on the end and removes to one that just finished. You will find most version changes occur half way through the hour or at the top of the hour.
Hope this makes sense ;-)
SJB: The references I have tracked for FlashForward are as follows
Wed April 4 series = crid://tvnz.co.nz/1008270 episode = crid://tvnz.co.nz/10163206
Sat April 7 series = crid://tvnz.co.nz/1008270 episode = crid://tvnz.co.nz/10163206
Wed April 11 series = crid://tvnz.co.nz/1008270 episode = crid://tvnz.co.nz/10163207
I'm thinking we can just use the number on the end and take a (small) risk that TV3 for example don't go and use a number used by TV1. They are probably assigned by the individual broadcasters.
From the data I've seen, they are only using CRIDs with scheme
authority (SA) and the event identifier (EID). I've not see any
instance identifiers in the data. As for how they are mapped, from
what I can tell, they are just unique ids created by the SA. Since
each channel has it's own SA, there is no correlation of encoding
schema. Thankfully, four channels share the same SA (tvnz.co.nz,
1,2,6, and 7). So as long as the same show stays on the same SA, you
shouldn't get duplicates. However, if the same show appeared on a
different SA, it would be issued another EID by that SA. And they are
completely different in their conventions too.
SJB: As we output an XMLTV file I think there may be another reason for only using the numbers on the end of references.
The XMLTV spec uses a 3 part number for the standard program reference in the format series ref . program ref . part ref
The parts are separated by a '.' so any conversion program that uses an XMLTV file would not work if the series, program or part ref also contained a '.' as the do for a full CRID.
The currently released version (1.0.15) has an option you can try to see if CRID's will work. Add Option:CRIDN to the ini file and it will output the reference numbers to the XMLTV file. It's worth a try to see if MP or MC for example can use them.
FUBARnz: Been using for a week now on terrestial tv, works perfactly, based in Napier. Only one problem is that tuners can't be used at same time as running programe but not major issue
|
![]() ![]() ![]() |