Decoder SDK Monitor: Difference between revisions
From Engineering Client Portal
No edit summary |
|||
| Line 13: | Line 13: | ||
== Downloads == | == Downloads == | ||
{{TVDownloadRequestLink|name=Decoder SDK Monitor (Windows | {{TVDownloadRequestLink|name=Decoder SDK Monitor (Windows vs2017) v1.4|dlid=b3ae411765cfa2b878c3f50c0824e61d81a58fbb}} | ||
{{TVDownloadRequestLink|name=Decoder SDK Monitor (Windows vs2015) v1. | {{TVDownloadRequestLink|name=Decoder SDK Monitor (Windows vs2015) v1.4|dlid=68d1fd697862e663a7aa2efc46377f053c983a5a}} | ||
{{TVDownloadRequestLink|name=Decoder SDK Monitor (CentOS) v1. | {{TVDownloadRequestLink|name=Decoder SDK Monitor (CentOS) v1.4|dlid=c978921ba90736bf7f2c82287a0a97af89109bec}} | ||
Revision as of 21:23, 4 November 2019
Decoder Monitor SDK is offered to Nielsen OEMs who are creating a system to monitor Nielsen audio codes (both NAES and CBET). Instead of delivering a detailed report of each detected audio code, the Monitor SDK issues, at one-minute intervals, a list of audio codes detected since the last report.
Each audio code is identified only by its type (CBET + layer number; NAES 2/6 + PC/FD/CC/HF identifier) and its station ID (SID/CSID). The SDK does not report the timestamp, stacked/unstacked designator, or any other audio-code details that are typically reported by traditional Nielsen decoders.
At one-minute intervals, the SDK also delivers any alarms that apply. It logs status and error messages as they arise.
- Output is a simplified reporting using a JSON string format
- Output is on a timed interval of 60 seconds