- How do I get and use the Omnia.9 Remote Control application?
If not already done, connect the Omnia.9 to your network and assign it an IP address per the manual. Connect to the unit using any standard web browser as follows: http://:7380 (for example: http://192.168.0.183:7380) You will see a simple screen titled: Welcome to Omnia.9 HTTP server - version... Under Downloadables: click on the link after: Download Remote Interface (Windows Application): and choose "Save File" to download the remote control app to a folder on your computer. Once downloaded, navigate to the folder where it was downloaded and right-click on "NfRemote.exe" and select Send To...Desktop (Create Shortcut). From your Windows Desktop, right-click on the NfRemote.exe shortcut and select "Properties". Add the following to the end of the "Target" field, immediately after the " mark at the end: host=password=1234 The finished "Target" field should look like this: "C:\Downloads\NfRemote.exe" host=192.168.0.183 password=1234 This assumes that the unit's IP address has been assigned to 192.168.0.183 and the password has not been changed from the default of 1234. Then click the "Apply" button. Now you should be able to double-click the desktop shortcut and open the remote
- How do I get the automation metadata for RDS into the Omnia.9?
All kinds of automated data entry into the Omnia.9 are done through the HTTP automation interface. The procedure is the same for *all* controls in the Omnia.9, it is not specific to RDS. One easy way to do it with an automation system that only spits out a text file is to have a batch file running as a background process, calling "wget" (an open source HTTP utility) every few seconds to set the RDS PS and/or RT parameters. The HTTP server is accessible at http://omnia9-ip-address:7380 -- you will need to add the computer (or IP range) that needs access to the HTTP Access menu in System Configuration. This is the same procedure as used to download the remote application from the Omnia.9. The Internal and External RDS generators are mutually exclusive -- if you use an external one, the one in the Omnia.9 must be disabled.
- How is Omnia.9 different from the Omnia.11 and Omnia.7?
We like to think of the Omnia.9 as the “swiss army knife” of processors due to its great flexibility and because of all it can do in a single box. The Omnia.7 is a little brother to the 9 that has the same analysis tools available but with less available processing bands and only a single stereo input (versus 4 for the 9). The Omnia.11 is more like a Ferrari to the 9’s SUV (and the 7’s Honda Civic), concentrating on and maximizing the audio processing of a single stereo input with great intelligence, outputting audio and composite MPX (only) that is ready for FM or HD1 / Streaming use.
- How do the physical rear panel inputs relate to the various processing cores?
A fully-optioned Omnia.9 can take in three independent audio sources via its physical rear panel inputs. Each physical input is then assigned to an internal signal path within Omnia.9 in the System > I/O Options > Input 1/2/3 menus.
Keep in mind that individual processing cores must be enabled, disabled, and configured in the System > System Configuration > Processing Paths menu, and only options that have been purchased and installed in your particular Omnia.9 will be available.
Though the rear panel digital inputs are labeled “Main In,” “AES Reference,” and “Aux In” in an effort to represent a typical installation scenario, they are in fact all identical and interchangeable.
One important thing to understand is how each audio source is “shared” within the unit. Again, using a fully-optioned unit for illustration, audio destined for the FM processor is also shared by the HD-1, Streaming 1, and Studio cores. Audio destined for HD-2 is shared by the Streaming 2 core, while audio for the HD-3 feed is shared by the Streaming 3 core.
- Which rear panel output should I use?
The choice of which rear panel outputs to use will depend upon the configuration of your particular plant.
In an all-digital plant where Omnia.9 is located at the studio and feeding AES audio to an STL with AES inputs, output audio should come from the Main FM Out 1, Main FM Out 2, and Aux Out outputs. The source of the processed audio for each of these outputs is determined in the System > I/O Options > Main Outputs menu.
For example, the Main FM Out 1 might be set to “FM Pre-emph L/R” in order to output pre-emphasized audio for the main FM channel which will be de-emphasized later in the chain. Main FM Out 2 might be set to “HD-1” to route audio destined for the HD-1 path. Aux Out may be set to “HD-2” for audio being sent to the HD-2 path.
If Omnia.9 is located at the transmitter, one of the two rear panel composite outputs can be used to feed the main FM audio directly to the exciter. This is also true if Omnia.9 is located at the studio feeding a composite STL. In these cases, adjustments to the output are made in the System > I/O Options > FM Options menu.
- How do I set input levels?
Input levels are set in the System > I/O Options > Source Adjustment menu.
- How do I set output levels?
If you are using Omnia.9’s digital outputs, levels are set in in the System > I/O Options > Main Outputs menu.
If you are using the composite outputs, levels are set in the System > I/O Options > FM Options menu.
- Where is the diversity delay?
Omnia.9 provides a “diversity delay” so that FM audio can be delayed and time-aligned to corresponding HD-1 audio, ensuring listeners with HD radios will experience a smooth transition when their receivers switch back and forth between the analog and digital signals.
This control has been relocated in this version of the software and is now found in the System > I/O Options > Diversity Delay menu. Double-clicking on the slider will bring up three independent sliders for Coarse, Medium and Fine adjustment.
- I’m having difficulty getting my Omnia.9 on my local network. I can’t “ping” it either.
As a security measure, Omnia.9 is not “ping-able” on the network so the inability to get traditional ping response is not necessarily a sign of a problem.
There are two basic conditions that must be met before a remote connection to Omnia.9 is possible:
- Omnia.9 must have a password set up via the front panel.
- Omnia.9 must be connected to your local network and have a working IP address initially assigned to it via DHCP (a static address can be established later).
Note: It is not necessary to “white list” a computer in order to access Omnia.9 remotely. Any computer running the NfRemote software can access Omnia.9 providing the user knows the unit’s password. White listing IS required to access the built-in HTTP server, however.
To set up a password, navigate to the System > System Config > Password menu from the front panel. Enter your password in the “Enter Password” and “Repeat Password” fields and click on the “Set Password” button.
To set up an IP address, navigate to the System > System Configuration > IP Configuration menu from the front panel. Click on “Use DHCP” to enable Omnia.9 to receive an IP address from your DHCP server. If, after a period of 30-60 seconds, the internal loopback address is still displayed, Omnia.9 is not communicating with the DHCP servers and there are network issues outside of the unit to explore.
While it is beyond the scope of this manual to provide specific IP troubleshooting advise, we can suggest the following basic steps:
- Try using a different Ethernet cable to rule out that a bad cable is at fault.
- Plug Omnia.9 into a different port on your router or switch to rule out a bad port.
- Plug Omnia.9 into a different router or switch altogether to eliminate a bad piece of hardware.
- Plug another device (such as a laptop computer) into the same port and see if it will communicate with the DHCP server.
- Using a computer that is already known to work on the network, use an Ethernet cable to connect Omnia.9 directly to that computer. In most cases, the computer will act as an ad-hoc DHCP server and attempt to assign Omnia.9 an IP address.
- Where do I get a copy of the remote software?
The remote software client (NfRemote) is always available from within Omnia.9 itself and can be retrieved using the built-in HTTP server. Any time you update your Omnia.9 software it is a good idea to update your NfRemote software as well to ensure compatibility.
The computer used to access the HTTP server must be on Omnia.9’s “white list” and Omnia.9 must be set up properly on your local network. To place a computer on the white list, navigate to System > System Configuration > HTTP Access and enter the IP address and subnet mask in the format shown below.
Using a web browser of your choice (and the actual IP address of your Omnia.9 to replace the sample address here), enter “http://192.168.1.1:7380”. This will bring up the HTTP server home page which contains a link to the NfRemote software. Download, locate and install the software. Once installed, assign
a “friendly” name of your choice in the “Comment” field, enter the IP address and password, and click “Connect”.
- What is the "MKII Platform Upgrade"?
Factory new Omnia 9 units have some software and hardware differences with their predecessors. We've titled these platform differences "MKII". While our software supports both new and legacy systems, certain feature sets require the MKII platform to operate, this includes Livewire +AES67 AoIP functionality and Kantar watermarking (used in France).
- How do I know if I need the MKII upgrade?
If you are planning to update your plant to Livewire / AoIP, or are a user in France where Kantar watermarking is being rolled out, you will need this upgrade.
- How do I get the MKII platform upgrade?
MKII upgrades require factory service from Telos or an authorized Telos repair center.
- Is there a cost associated with the MKII Platform Update?
Yes, Please check with your local dealer for pricing.
- I’ve had my Omnia.9 for several years, can I upgrade it to have Livewire?
Yes. You’ll need to send it to us (or a qualified Telos service center) to have the MKII platform upgrade installed.
- Why isn’t Livewire or AoIP just a software change?
Livewire+ AES67 uses more resources and computing power than available on the legacy Omnia.9. In order to support Livewire and facilitate future updates, we needed to expand our platform.
- Why does the MKII platform update require factory service?
Delicate Hardware modifications, warranty provisions, and third party software license agreements require this to be a factory update.