Tests 14 And 15: Info Tag Cid And Offset Tests - Nielsen ID3 User Manual

Meaning
The INFO Tag Interval test reports the number of times an INFO tag appeared too soon
or too late, in comparison to the previous INFO tag. Validator may report a tag as missing
at 310 seconds and may report the next tag as arriving too soon. As a result, Validator
reports two errors instead of just one. Take into account such double reporting when
evaluating Test 4 failures. See "Test 4 Result: Time Gap Test" on page 24.
Example
The example below shows Validator found no INFO-tag-interval errors. The test passed
because Validator allows up to one error.
Possible Causes of Failure
If INFO tags arrive too soon or too late, your application logs the following error message:
See "Possible Causes of Failure" for Test 12 on page 33.

Tests 14 and 15: INFO TAG CID and Offset Tests

Format
Format
Number of Errors
0
Maximum Tolerated
Meaning
For INFO tags, the PC and FD CIDs should both be set to the null CID, which is
X100zdCIGeIlgZnkYj6UvQ==. If either of the CIDs is set to a value other than the null
CID, Validator declares an INFO tag CID error.
Likewise, the tag offsets (PC and FD) for all INFO tags should be set to 0. If any INFO-
tag offsets are not set to 0, Validator declares an error.
Example
The example below shows Validator found no INFO-tag CID errors. The test passed
because Validator allows one such error. INFO-tag offset errors are reported in the same
way.
Release 1.8 Revision F
ID3 Tag: INFO Tag Interval Test:
-53: INFO tag is missing or late: sequence number xx
<number of INFO Tag CID errors / 0 / maximum
tolerated>
Number of errors detected
Not used
Maximum number of errors tolerated before failure is declared
INFO Tag: INFO Tag CID Test:
Pass <0/0/1>
Pass <0/0/1>
34
ID3 Tag Validator Application User Manual
Nielsen Confidential