Table of Contents
Advertisement
Periodic Report
The example below indicates that 10 seconds have passed since the last INFO tag. The
test passed because 310 seconds had not transpired.
Possible Causes of Failure
Test 12 most often fails when the tag-inserter application incorrectly invokes a call to the
PCM-to-ID3 SDK function InputAudioData(). If you are the tag-inserter application
developer, check these two conditions:
•
If the PCM-to-ID3 SDK releases a DATA tag and an INFO tag immediately after your
application invokes a call to InputAudioData(), your application may be dropping
the INFO tag. Make certain to transmit all ID3 tags that are generated after
InputAudioData() returns.
•
The PCM-to-ID3 SDK requires that the calling application maintain a system clock by
correctly setting the currentTime argument to the InputAudioData() function.
The currentTime value must advance 1 second for each second of audio content
processed. If the value of currentTime is not correct, the timing of INFO and DATA
tags is incorrect. If your tag-inserter application is processing file input, make certain
that you base your currentTime value on the number of seconds of processed
data, not on a running system clock because the input file is processed faster than
real-time.
•
For fail-over protection, there may be two tag-inserter applications in a single
broadcast facility, both of which contribute ID3 tags to a single ID3 tag metadata
stream. If the switch between devices occurs precisely when an INFO tag is about to
be delivered, this configuration of tag-inserter devices may result in missed INFO
tags.
Test 13: INFO Tag Interval Test
Format
Format
Number of Errors
0
Maximum Tolerated
Release 1.8 Revision F
INFO Tag: Elapsed Time Report: Pass (10)
<number of INFO-tag interval errors / 0 /
maximum tolerated>
Number of errors detected
Not used
Maximum number of errors tolerated before failure is
declared
33
ID3 Tag Validator Application User Manual
Nielsen Confidential
Advertisement
Table of Contents
