What each box became

Every row is something a station used to buy, rack, power and replace. In Ramus Cloud each is a part you switch on, and all of them meet in one routing table.

The boxIn Ramus CloudWhat it doesStatus
STL codec1 rack unitstudioEDGEAudio travels as Opus from studioEDGE, through Ramus Cloud, to every site that subscribes: the transmitter, another market, or another room in the same building. Use it as the main link, or as the backup to the one you have.Shipping
Audio router2 rack unitsRouting tableSources down the side, destinations across the top. One source feeds as many destinations as you like.Shipping
Closure extender1 rack unitPoint-to-point closuresA contact closure at the studio drives a relay at the transmitter site.Shipping
Silence sensor1 rack unitAlerts and failoverSilence, low level and clipping raise alerts. A route with a backup switches by itself when its source is lost, and goes back when the source holds steady.Shipping
Backup audio player1 rack unitFailover audioA file from your library is the backup for any route.Shipping
FM processor3 rack unitsProcessorThe processor runs in Ramus Cloud and the finished composite reaches txEDGE over CMPX.Shipping
RDS encoder1 rack unitProcessor, built inPS and RadioText, fed by the same now-playing data as your stream.Shipping
Diversity delay1 rack unitProcessor, built inThe delay between the FM and DAB legs, up to 12 seconds either way, set in the console.Shipping
Streaming encoder1 rack unitEncoderPushes any signal you route to it to your streaming provider. Each target is its own process.Keeping your own processor? Take the unprocessed program as HLS instead.Shipping
Modulation monitor*2 rack unitsFM MPX Analyzer*txEDGE listens to the station off air, and the console shows the multiplex you are transmitting.Shipping
Phone hybrid1 rack unitPhone hybridCallers arrive as signals you can route, with mix-minus built in.Coming
Remote broadcast codec1 rack unitRemote broadcast appA phone app that sends a remote back to the studio as a signal you can route.Coming
Logger1 rack unitLogger and skimmerAir checks and a compliance log, recorded from any signal you already route.Coming
*

The FM MPX Analyzer is a monitoring aid. It is not a calibrated modulation monitor and must not be used as a compliance measurement.

Routing table

Routing is a crosspoint grid: sources down the side, destinations across the top, the way a hardware router panel reads. One source can feed as many destinations as you like, and each mark shows whether its route is carrying, on its backup, or switched off.

Routing table
Crosspoint gridPoint-to-point closures
Listen in the browser
A routing grid with one source feeding two destinations and one route on its backup.
SourceProcessorEncoderAux TX
Studio ACarryingCarrying
Studio BSwitched offOn its backup
Failover audio
CarryingOn its backupSwitched off

Alerts and failover

Give a route a backup, such as another source or a file from your library, and it fails over by itself when its source is lost, with an alert. When the source returns and holds steady, the route goes back and the alert clears.

Silence, low level and clipping raise alerts of their own. Contact closures route point to point, so a closure at the studio can drive a relay at the transmitter site. You can listen to any audio signal in the browser.

Alerts and failover
Automatic failover and returnSilence, low level and clipping alerts
A studio feed with three subscribers and a backupStudio on air. The studio publishes its program once. The transmitter, the aux site and the stream each subscribe to it.

Processor

The FM processor runs as its own service in Ramus Cloud, so the transmitter site receives finished audio. It has an RDS encoder for PS and RadioText, fed by the same now-playing data as your stream.

The processor has an FM leg and a DAB leg. Set the diversity delay between them in the console, up to 12 seconds either way. Every change to the delay is recorded with who made it.

txEDGE sits at the transmitter site. It receives the processed composite over CMPX and rebuilds the multiplex for the exciter, as analog composite or digital MPX.

Processor
RDS encoderDiversity delay, ±12 s
CMPX receiverAnalog composite output included
Digital MPX out via optional user-supplied hardware
The Ramus Cloud console's processor page: the meter bridge, the CMPX transport status, presets and the wideband AGC controls
The processor in the Ramus Cloud console.

CMPX sends the composite as its parts

CMPX, or component MPX, is how Ramus Cloud delivers a processed FM composite to the transmitter over the internet. Instead of shipping the 192 kHz multiplex whole and compressed, it sends the program audio and the carrier instructions for rebuilding the MPX baseband.

Program as components
The processed mid and side program travel as two Opus streams, 384 kbit/s combined by default.
Carriers rebuilt at the site
The txEDGE generates the 19 kHz pilot and the 38 kHz and 57 kHz carriers. Nothing is decoded out of compressed audio.
RDS kept as data
RDS groups arrive as data and are added to the composite at the site, never run through the limiter.
Same arithmetic everywhere
The same components produce the same composite, bit for bit, in the cloud and on the box.
Signed
The synthesis instructions are signed, and the txEDGE refuses any it can't verify.
The FM multiplex: what CMPX carries and what the txEDGE rebuilds
Carried as OpusRebuilt at the txEDGE
txEDGE: a grey enclosure with a smoked top printed with the txEDGE name, two BNC connectors on the front
txEDGE at the transmitter site. Illustrative.

Encoder

Ramus Cloud runs the encoder. It pushes any audio signal you route to it to your streaming provider over Icecast, and passes now-playing from your automation system along with it.

Each target runs as its own process, so a stuck connection to one provider doesn't interrupt the others.

Running your own processor at the transmitter site? The encoder can serve it the unprocessed program as a standard HLS stream instead, with now-playing in the playlist.

Encoder
Icecast pushNow-playing from your automation
One process per targetUnprocessed HLS for your own processor
One encoder pushing a program to three Icecast targets, one reconnecting, and serving it as HLS to a processor on siteProgramAutomationnow-playingEncoderMain streamstreamingApp streamstreamingPartner feedreconnectingOn-site processorHLS, unprocessed
Each target is its own connection. One reconnecting leaves the others streaming, and a processor on site pulls the unprocessed program as HLS.

FM MPX Analyzer*

txEDGE also listens to the station off air. The console's FM MPX Analyzer shows the off-air multiplex, so you can see what you are transmitting, not just what you sent.

FM MPX Analyzer
Off-air monitoringFM MPX Analyzer
The Ramus Cloud console's FM baseband spectrum from 0 to 60 kHz: the L+R audio, the 19 kHz pilot, the L minus R stereo subcarrier and the RDS subcarrier, with the processor composite and the off-air multiplex overlaid, plus a peak-hold trace
The FM MPX Analyzer in the Ramus Cloud console: the processor's composite and the off-air multiplex on one spectrum.

Coming next

  • Coming

    Phone hybrid

    Callers arrive as signals you can route, with mix-minus built in.

  • Coming

    Remote broadcast app

    A phone app that sends a remote back to the studio as a signal you can route.

  • Coming

    Logger and skimmer

    Air checks and a compliance log, recorded from any signal you already route.

  • Coming

    Transmitter control and monitoring

    Readings, alarms and control for the transmitter site, on a dashboard in the console.