![]() This is the latest feature to bridge the gap between Zetta and NexGen. Once set up, it uses the NexGen-like matching processes which looks at the surrounding elements to place the voice track. Zetta’s station # is found in Station Config. Once you get NexGen’s Wancast receiver (STSR) installed on the Zetta site, it’s simply a matter of creating the mappings in NexGen and pointing to the correct location and station number. You indicate what folder you wish to have Zetta look for voice tracks in NexGen from this screen. ![]() In version 3.0.1 of Zetta, we introduced a “Content Ingest” tab, which at the moment only houses NexGen Voice Track Ingest. ![]() You still want to be able to leverage our industry leading interconnectivity between sites, so we invented a way for your to not lose that capability going forward with Zetta. ![]() In this article, I wanted to highlight one of the many compatibility bridges we have employed in Zetta to help the radio group that is very familiar with NexGen and starting to employ some Zetta. While they typically produce similar results, there are some different ways of getting there. In previous RCS Connect articles, I have been charting a path from a NexGen function to the same feature in the new Zetta universe. In every way, Zetta was created as the Next Generation of NexGen.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |