Z/IPStream R/2 Frequently Asked Questions
Updated
by
Bryan Jones
Introductory Questions
How do the licenses work on the R/2?
The license codes installed on your R/2 determine the number of audio programs you may ingest and process. For example, if you have three unique content audio programs, you will need an R/2 with licenses to unlock three audio program inputs. Once you ingest the audio program, you may process and encode each program more than once, in different formats, provided there are enough resources.
There are no front panel controls; how do I set up my new Z/IPStream R/2?
During the initial setup, you use a local keyboard and monitor to assign an IP address to the R/2 (please see the Quick Start Guide, or the manual, for more details). You complete the remainder of the configuration using a Web browser. To access the front panel menus, use the navigation cluster. The Quick Start Guide and manual is located here https://docs.telosalliance.com/z-ipstream-r2/quick-start-guide
Since I need to access the Web GUI, how do I get it on the network?
The LAN and WAN network connections default to statically set IP addresses as described in the Quick Start Guide (above). You can access the Web GUI by connecting a computer in the same subnet as one of the pre-programmed IP addresses or by changing the IP address as described in the QSG.
I need to have static IP. How do I configure this without a web interface?
If you can not access your R/2 from a Web Browser, the IP addresses can initially be changed by connecting a local keyboard and monitor as described in the QSG.
Can I change Network Interface Settings from the Web GUI?
Yes, you can edit your network interface settings in the Network menus after you log in the first time. If you change the IP address of your R/2, you will need to change that in your browser’s address bar so that the browser can connect to the R/2 on the new IP address.
Now how do I get audio in?
The Z/IPStream R/2 has two choices for audio input. AES/EBU or Livewire. To add an audio source, click on "Audio Sources" in the main menu. You will see a screen with a drop-down on the right labeled "Add Audio Source." After you open this, you can select AES/EBU or Livewire. Give the audio source you are adding a familiar name. The name you assign is the name you will see when you select the audio sources later on in configuration. Now, select the proper Livewire IP Driver input or AES/EBU input you are using/intend to use. If you have chosen the Livewire driver, you'll need to do one more step to get the audio flowing. At the top right of the menu is the "Livewire Driver" menu. Open this menu and then fill in the "DST (receive)" field with the proper Livewire channel corresponding to the audio source you just made. So if you selected Livewire input 1, fill in the first "DST (receive)" position.
What are the different streaming instance types?
We provide a variety of instance types to give users the ability to have maximum flexibility when it comes to implementation.
- Audio Processing Instance: This is used to process an audio program and send the processed audio out to the local outputs, either AES or Livewire. It is useful for program monitoring or additional processing.
- Standard AAC Encoder Instance: Used to process and encode an audio program to AAC. The R/2 can send the resulting stream to multiple media servers simultaneously.
- MP3 Encoder Instance: Same as the AAC Encoder instance, but the audio is encoded to MP3.
- Adaptive AAC Encoder Instance: An adaptive stream simultaneously encodes the same audio at multiple bitrates. Listeners can then select the appropriate bitrate depending on their available bandwidth. We support the Apple HLS and Microsoft SmoothStreaming formats.
- Processed or Watermarked Audio Source Instance: A Processed Audio Source allows you to reuse a processed audio program so that you don’t have to process the same audio multiple times. For example, if you need an Audio Processing Instance for local monitoring, a Standard AAC Encoder Instance for a high-quality stream, and an MP3 Encoder Instance for mobile platforms, you would want to set up a Processed Audio Source to feed all of them the same post-processed audio. You then would select ‘no processing’ on each of those instances because you are already processing the audio at the Processed Audio Source. This maximizes the number of streams you can generate while minimizing the CPU utilization.
- SHOUTcast or Icecast stream monitor Instance: Each license activates two monitoring instances. Monitoring instances can be used to monitor the stream from your server and send email notifications on stream silence or failure of the stream.
Any other tricks with program types?
You do not need two instances if you run redundant mount points. Instead, you just need to add each mount point. These mount points need identical codec settings and audio, but there can be different server types. This can help reduce on-screen clutter. In other words, a single SHOUTcast encoder instance can send to two (or more) SHOUTcast servers.
Do processing adjustments take effect universally immediately?
Yes, the processing adjustments take effect immediately. Make sure you save the processing adjustments; otherwise, they will disappear after a restart.
How can I locally monitor the R/2's audio without the headphone jack?
- You may use an Audio Processing instance or a Processed Audio Source instance to send the processed audio to an output device, AES or Livewire.
- If you purchased the R/2 with optional Omnia.9 Processing, then you can also monitor the audio via NfRemote. Once logged into NfRemote navigate to Client Audio Out, and then Patch Point. Under Patch Point, select an output on the PC you want to listen from and turn the output on by clicking the power button icon. If you get dropouts or stuttering audio, increase the audio buffer until they stop.
How many outbound streams can the R/2 support?
This depends on a variety of factors. The primary load on the R/2 is Omnia 9 processing instances. In most cases, you won't stress the R/2 but, as you add more instances or start seeing problems, check the Status page of the R/2 and see if the CPU or Memory are under full load. If you have not exceeded the resource limits but still have problems, you may need to check the bandwidth usage for all generated streams. Make sure that your Internet connection can handle all the streams and that no other computers or streams are using up your bandwidth. Consider creating the Omnia.9 as a Processed Audio Instance and using that new source for any sessions that use that audio.
What about MetaData?
Telos streaming products have always had full support for receiving Metadata, and the facilities for handling metadata are included. You shouldn't need any third-party software unless your automation system requires it. The Z/IP Stream can take metadata by TCP or UDP. We have a free "file watcher" utility if your automation can only create a text file.
What is Metadata2ui?
Metadat2ui (ui is short for user interface) is a Windows executable sometimes needed to configure the metadata being sent to some content distribution networks. It's used with more complex metadata requirements. For example, if you have more than one source of metadata and need to aggregate them, or you need to send metadata to a profanity delay first, so it's in sync with your audio.
Do I need this PC running Metadata2ui all the time?
No, you only need Metadata2ui open during configuration. We recommend you close it when not in use.
How do I get Metadata2ui?
You can get the latest version of Metadata2ui by contacting us. We'll make sure you get the correct version to go with your system. Use the contact form a the top of this page or email us at support@telosalliance.com.
What do I do with Metadata2ui?
We need to connect Metadata2ui to Z/IPStream R/2 using one of its IP Addresses. Click on the File button, followed by New Connection. Now you will have a screen where you can fill in the IP Address and Display Name for this R/2. Press OK, and now you will see the Z/IPStream listed as available. Find the connect button next to the R/2 you want to connect to and click it to connect.
I'm connected; now, how do I add metadata?
To get your Metadata flowing, we need some information about your setup to create a source.
- How does your playout system deliver its metadata? The Z/IPStream R/2 can accept metadata over incoming TCP or UDP. It can also make outbound connections to systems over TCP. Once you know your connection type, click "Source" and select it. Now configure your connection and move on to part two.
- We need to know your automation system's output and select the proper filter. You can now save your source to create it. Please contact Telos Support for assistance if your automation system is not listed.
My source is set up. How do I get my metadata out?
In most cases, you have to run your Metadata through a Translator. A Translator allows you to modify or clean up some metadata fields' content. To set up a Translator, open the Converter menu and select Translator.
What do I put in the translator?
What goes in the Translator depends on what fields we need to filter for the Content Distribution Network. For example, if the CDN needs a specific input value to trigger ad insertion or content coverage, we would use a "Change Field" to translate the metadata fields from what the automation system generates to what the CDN expects to see. Inside of the Change Field, you will have a Field Name, Match Value, and New Value. The Field Name is the general value of a specific portion of the metadata, and the Match Value will be the specific subvalue of this field. For example, if your automation system outputs "cue_type: COM" for commercials. You would use "cue_type" as the Field Name, and "COM" would be the Match Value for commercials. You then will need to get the value your CDN wants to see in place of COM and fill that in for the New Value.
My metadata is ingested and translated. What do I do with it now?
We're ready to send it out. Select Outputs on the menu bar and select "Send Over TCP." As the "source" for the output instance, select the Translator you just created. Select an output template that matches the format needed by your replicator, (for example, the template for Triton Digital it is often andoxml2). If sending the output to Triton Digital, set the "Destination address/port" to 127.0.0.1:31313 and click OK.
There is no filter or template for my Metadata. What do I do?
Contact us. We will write basic input filters or output templates for you for free. If we don't already have a filter, we'll ask you to provide us with sample output data, and we'll write one for you. This is software development, so we ask that you give us as much notice as you can. We may not be able to assist if you call us one hour before you need to go live with your metadata. Generally, we need 48 hours to write and test a new filter.
What about other metadata issues?
Metadata can be a very complex topic, and we're here to help. Please reach out to Telos support for assistance with this at 216-241-7225, or via email at support@telosalliance.com.
Triton Digital
Do I need to contact Triton Digital before I can use my R/2 with Triton Digital services?
Yes, you will need to contact Triton so they can provision your stations appropriately to work with the R/2.
Can I use the R/2 to stream to Triton and also to an internal server?
You can certainly use the R/2 to stream to Triton and another server. However, this portion only pertains to the Triton. Please reference the introductory section for standard configurations.
Since I am an existing Triton customer, will I still use Station Manager?
Technically yes, but no. The R/2 replaces the current PC that is running Station Manager. The R/2 has the Triton Station Manager built-in.
Where will I configure my connection to Triton Digital Services then?
You will need to navigate to Audio Sources, and then Triton Digital Services. You then will input your Station credentials from Triton, and click Save.
If Triton is not just another server instance type, how do I configure audio to reach Triton?
Triton operates out of a separate menu. To get your post-processed audio to this is a two-fold process. We will need to set up an Audio Processing Instance, which we point at a Livewire or AES output. Then you will need to take this output to another input to loop it back and select the second input as the Audio Device under Configure Station. This is useful in cases where (in the US) you might want to include Neilson PPM in your stream.
Configure Station? Where can I find that?
Under Triton Digital Services, after you have started the station you want to modify. Now click on the station we need to route audio to, and in the bottom right corner, you will see Configure Station. In this menu, you will now see Audio Device. Select the Post Processed Audio source here that you want to feed to Triton.
How does my metadata reach Triton?
Metadata is parsed within the R/2, but configured from an executable called Metadata2ui, as described in the previous section.
What is Metadata2ui?
Metadata2ui is an executable that needs to be installed on a local windows machine and is only needed to configure the metadata flow. More information on this can be found in the prior section, Metadata2ui.
My audio and metadata are out of sync. Why?
If you run your audio through a delay before the R/2, you will need to delay your Metadata the same amount. You accomplish this from the Configure Station menu. Once in the configuration find Cuepoint Delay Duration. Fill in the amount of time the audio is delayed in milliseconds and your metadata will be delayed the same amount as the audio.
Who do I call if I have a problem?
Both Telos and Triton Digital can field calls for the R/2. If it is a local problem with R/2 you likely want to call Telos first, and if it looks like an issue beyond your facility you may want to start with Triton Digital. If needed, Telos and Triton Digital will work together to resolve a situation.
