ID3 Tag Validator Application User Manual
Release 1.8 Revision F
28
Nielsen Confidential
The most likely cause of a CID timestamp error is that the PCM-to-ID3 SDK streaming
mode was set to 1 or 2 and neither is supported. Set the Streaming Mode to 0.
A timestamp error may also occur if PCM-to-ID3 SDK incorrectly assessed the daylight
saving time setting of the NAES watermark. In such cases, the CID timestamp may be
set to a value other than 3 a.m. Such cases are truly errors. If you encounter such errors,
work with your Nielsen support team to resolve them.
Test 8 Result: CID Timestamp (TS) Offset Test
Format
Format
<number of CID timestamp offset errors / 0
/ maximum tolerated>
Number of Errors
Number of errors detected
0
Not used
Maximum Tolerated
Maximum number of errors tolerated before failure is
declared
Test Result Meaning
Each tag includes an offset field that indicates the amount of time between one of the
tag’s EDUs and the CID timestamp. Valid EDUs within the tag should fall within 10
seconds before or after the sum of the CID timestamp plus the tag offset. For example, if
the CID timestamp is 3 a.m. and the CID timestamp offset is 3600, Validator should
report watermarks in the ID3 tag within 10 seconds of 4 a.m., which is 3 a.m. + 3600
seconds.
Example
The example below shows that all CID timestamp offsets were properly set. The test
passed because Validator allows up to 32 CID timestamp-offset errors.
ID3 Tag: CID TS Offset Test: Pass <1/0/32>
Possible Causes of Failure
These are the most common log messages when Validator finds a CID timestamp-offset
error:
-55: Non-zero tag offset when PC CID TS is 0, at Seqno xx, Tag
Time xx.
-55: Non-zero tag offset when FD CID TS is 0, at Seqno xx, Tag
Time xx.
-55: Non-zero tag offsets when PC and FD CID TS are 0, at Seqno
xx, Tag time xx.
Validator may find CID timestamp-offset errors for these reasons:
•
Although most locations in North America observe Daylight Saving Time (DST),
some locations do not. If the PCM-to-ID3 SDK was running in a time zone with a
