Terayon Communication Systems Inc. has added two new software features to its DM 6400 Network CherryPicker aimed at making digital advertising insertion more efficient.
The first allows operators to convert legacy dual tone multifrequency (DTMF) cue tones into the digital tones inside the CherryPicker.
The second enables MSOs to connect ad servers via Gigabit Ethernet, allowing for the efficient exchange of ads over longer distances.
Many of the existing cue tones deployed by cable networks use the DTMF frequency, said Terayon director of product marketing Mark Jeffrey. Typically, a network feed is sent to an encoder for video/audio encoding, while the DTMF cue tone is sent to the ad server for conversion to an SCTE-30 splice command.
By adding new software, the video/audio encoding and SCTE-30 splice command is handled by the CherryPicker, which also converts the SCTE-30 command to an SCTE-35 cue tone.
“The SCTE-35 cue tone is embedded and the program is primed,” Jeffery said. This method ensures picture quality by removing the traditional decode/re-encode procedure that increases cost, lowers picture quality and has more points of failure.
Jeffery contends that Gigabit Ethernet is an improvement over existing architectures. With traditional ASI distribution networks, ad servers and ad splicers have to be co-located at the master headend, he said, with the same set-up replicated at the hubs at the edge of operators’ networks for local ad insertion.
The Gigabit Ethernet model reduces overall network complexity by allowing for the centralization of ad content, he said, optimizing the number of ad servers required.
“You can manage them all from one place,” he said. “You can centralize ad servers, traffic and billing. This is proven in the enterprise space.”
Terayon is working with its cable customers, including Comcast, in trialing the new software, according to Jeffery.
Weekly digest of streaming and OTT industry news
Thank you for signing up to Multichannel News. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.