Using an RTMP input

Send a stream straight to Glossa from OBS or a hardware encoder when a direct line isn't practical.

glossa

Last Update 1 个月前

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 look in its settings for the RTMP server URL and stream key.


Confirm in dashboard: the exact location and labels for the RTMP server URL and stream key inside your service settings (likely under Advanced Settings). Add a screenshot here before publishing.

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.

 

Was this article helpful?

0 out of 0 liked this article