Troubleshooting Tips; Tag Time Not Advancing Properly; Background; Symptoms - Nielsen ID3 User Manual

Troubleshooting Tips

Validator is effective in pinpointing common problems faced by developers who use the
PCM-to-ID3 SDK. The remainder of this section lists some of the problems that Validator
can help to identify. In most cases, suggested remedies follow the problem description.

Tag Time Not Advancing Properly

Background

Each ID3 tag has a start time and an end time. Ideally, the difference between the start
and end times should be 10 seconds. If the tag fills with 10 or more EDUs, the tag-
duration is legitimately less than 10 seconds.
Sometimes, though, the tag duration is shorter than 10 seconds for no apparent reason.
In such cases, the tag time is not properly advancing.

Symptoms

If there is a real problem with tag times not advancing properly, the Summary Report
shows that the Tag Duration test failed as shown in the example below:

Possible Causes

When the application feeds data to the PCM-to-ID3 SDK, it calls this function:
The third argument to the function must be a value that increments by 1 second for every
second of delivered content. The PCM-to-ID3 SDK maintains its clock based on this
value. If it does not properly advance, the clock is wrong.
Another cause could be content that is bad or fed to the ID3-tag inserter at the wrong
rate.

Suggestions for Follow-up

•
Check the currentTime argument in your call to the PCM-to-ID3 SDK API
InputAudioData().
•
Send to Nielsen 10 minutes of transport-stream for further analysis.
Release 1.8 Revision F
ID3 Tag: Tag Duration Test:
void InputAudioData(uint8_t
currentTime);
Fail <35/0/2>
*inBuffer, uint32_t
56
ID3 Tag Validator Application User Manual
nSize, time_t
Nielsen Confidential