ID3 Tag Validator Application User Manual
Release 1.8 Revision F
9
Nielsen Confidential
Pre-Validation Checklist
A common source of tag-generator errors is the misinterpretation or omission of one or
more of the processes listed in Table 1. To avoid these mistakes and save yourself some
time, review these steps.
Table 1 – Pre-Validation Checklist
Step
Process
Requirements
Note
1
Your application receives a source
MPEG-2 transport stream that
contains Nielsen watermarks
Ensure the source content is
watermarked.
2
Your application extracts the audio
stream from the source transport
stream and converts the audio to
PCM format.
If the source program
contains more than one
audio elementary stream,
your application selects the
first stream in the Program
Map Table (PMT).
3
Your application delivers buffers of
PCM audio data to the PCM-to-
ID3 SDK and stamps each buffer
with the “current time.”
Ensure the “current time:”
advances by 1 second for every
second of audio processed.
Potential and most
frequent error:
The
application feeds system
clock time to the ID3 SDK
when it processes the
incoming audio content
faster than the rate at which
the audio is normally
delivered during live
streaming.
4
The PCM-to-ID3 SDK decodes the
Nielsen watermarks in the
incoming audio stream, generates
ID3 tags, and delivers ID3 tags
and log messages to your
application
Ensure your application stores the
log messages in a retrievable log
file.
5
ID3 Tags in HLS Steams Only
Your application inserts each
Nielsen ID3 tag into two transport
packets in a single metadata
Packetized Elementary Stream
(PES) packet.
Ensure the PMT elementary loop
defining the metadata PES
includes the required ID3 tag
descriptors, as defined in “Timed
Metadata in HTTP Live
Streaming.”
Within the metadata PES, the two
transport packets carrying the ID3
tag must be contiguous.
See “Related Documents”
on page 7.
