features:stream-monitor
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
features:stream-monitor [2017/05/19 06:37] – [Adding Streams] tw | features:stream-monitor [2020/07/14 16:20] (current) – [Audio Routing] tw | ||
---|---|---|---|
Line 34: | Line 34: | ||
In these action lists, you can do things like stopping/ | In these action lists, you can do things like stopping/ | ||
===== Audio Routing ===== | ===== Audio Routing ===== | ||
+ | |||
+ | The audio output for the Stream Monitor is set on the //Audio Devices// page in the config app or Control Panel. You can route the output to any soundcard or the [[features: | ||
+ | |||
+ | The Stream Monitor works best when running on an automated system where the automation is playing directly into the encoder, not any physical sound card. In that case, you can use the **Encoder High-Priority Input**. Set up your audio routing as follows: | ||
+ | |||
+ | * Player/ | ||
+ | * Stream Monitor output: " | ||
+ | |||
+ | The High Priority input will mute the regular encoder input as soon as any audio item is sending data to it. So your automated playlist will continue to play in the background, but it is automatically muted as long as the Stream Monitor is rebroadcasting any stream. When the stream ends, the encoder input will be unmuted again. [[features: | ||
+ | |||
+ | ===== Metadata ===== | ||
+ | |||
+ | Metadata (title updates) received from upstream are automatically forwarded to all outgoing stream connections if all of the following conditions are met: | ||
+ | |||
+ | * Stream Monitor plays directly into the encoder (output device is set to one of the " | ||
+ | * " | ||
+ | * " | ||
features/stream-monitor.txt · Last modified: 2020/07/14 16:20 by tw