Test 24 Result: Pes Packet Header Check - Nielsen ID3 User Manual

Possible Causes of Failure
If Validator determines that the PTS is out-of-sync with the tag time, it delivers this
message to the log file:
The most likely cause of a tag-time error is poor multiplexing. For proper multiplexing to
occur, the PTS of each ID3 DATA Tag PES header must be set to the PTS of the
corresponding audio PES header. If the PTS values are properly set, the transport-
stream multiplexer should properly place the tags.

Test 24 Result: PES Packet Header Check

Format
Format
Number of Errors
0
Maximum Tolerated
Test Result Meaning
Validator counts the number of PES-packet headers that are associated with the Nielsen
ID3 tag metadata stream. There should be at least one of these PES packet headers
every 10 seconds.
If non-Nielsen ID3 tags are in the metadata PES, the PES packet-header count may be
much higher than expected. In that case, the assessment of "Pass" may not be
meaningful because it would indicate only that there are some metadata packets in the
stream. "Pass" would not indicate that the number of Nielsen PES packets is adequate.
This field is an "event" count, not an error count. Validator does not issue log messages
when it finds a Nielsen ID3 tag PES header.
Example
The example below shows that Validator found 319 Nielsen PES headers in the stream. The
test passed because Validator requires at least 237 instances.
Possible Causes of Failure
If the PES headers are missing, even though the PMT lists the stream in its elementary
loop, the PES stream itself may have been omitted from the transport stream during the
multiplexing process.
Release 1.8 Revision F
-64: Warning, Sequence Number xx: Tag time out-of-sync with PTS.
Delta = xx.
<count of PES packet headers / 0 / minimum
required>
Count of PES packet headers found in the stream
Minimum count required for test to pass
Not used
MPEG-2: PES Packet Header Test: Pass <319/237/0>
38
ID3 Tag Validator Application User Manual
Nielsen Confidential