Using an RTMP input

Glossa can receive an RTMP stream as its audio source. This is useful when your audio already lives in a streaming encoder or hardware that can send RTMP, and routing a local audio cable isn’t practical. Keep in mind that RTMP adds a little more delay than a direct line or a virtual cable, so use it only when those options don’t fit.

Step 1: Find your RTMP details in Glossa

Open your service and click Advanced Settings, just below the Start Streaming button. The RTMP section shows the server address and your stream key. Copy both.

Glossa starts transcribing by itself as soon as your encoder begins publishing, and stops when the encoder stops. Nobody has to open the browser or click Start Streaming, which makes RTMP a good fit for services that must start without an operator.

Because it starts automatically, remove Glossa as a destination in your encoder when you are not using it, or you may be charged for a stream you did not mean to run. Make sure the stream actually carries audio.

Step 2: Point your encoder at Glossa

In OBS, for example:

1. Go to Settings, then Stream.
2. Set Service to Custom.
3. Paste Glossa’s RTMP server URL into Server and your stream key into Stream Key.
4. Click OK, then Start Streaming.

Streaming to Glossa and your main platform at the same time

A single OBS stream output goes to one destination. If you also broadcast to YouTube or Facebook, you have a couple of options so both get the feed:

• Use a multi-output plugin or a restreaming service to send to both Glossa and your main platform at once.
• Or keep your main broadcast as is and feed Glossa with a virtual audio cable instead, which avoids RTMP’s extra delay. See Streaming with OBS and a virtual audio cable.

Glossa only needs the audio to translate, so you don’t have to send high-quality video. A lower video bitrate is fine and keeps things light.