Fallback and push

[durandguru]

Hi,

I have setup an stream to go to mistserver. I have configured an fallback stream on that stream. Everything works for that. I also push that stream to another destination, but when pushing and the source goes offline, the fallback is not sent. Is that by design?

[Rokamun]

Hey,

Yes that's actually by design. The fallback is meant for viewers only as pushing has more control from the server side.

A very quick method to do this would be to leverage the custom variables and a simple bash script.

#!/bin/bash

#use local API to bypass authentication, url-encode active_streams call to keep readability
DATA=$(curl -G "http://localhost:4242/api2" \
    --data-urlencode "command={\"active_streams\":{\"streams\":\"$1\"}}")



#Check Data for debugging
#echo $DATA


#Check if the word "Online" is there for the exact stream name match. If present stream is online, otherwise stream is offline
if [[ $DATA == *"Online"* ]]; then
  RESPONSE=true
else
  RESPONSE=false
fi

#response for custom variable to use
echo $RESPONSE

Then setup the custom variable to use this script & provide the stream name you want to check for e.g.:

- You'll want the check interval at 1 second. - The command should be the location of the script followed by the stream name

You can then set up a stream push for both the "normal" stream and the "fallback". The fallback stream will need the rules for the custom variable:

The end result would be something like this:

This would have the normal live stream push whenever it's active, while supressing the fallback stream from pushing to the same target. Once the live stream is offline the fallback would kick in.

Now this isn't exactly 100% perfect, there's a slight gap and overlap possibility for both streams, though it should stay within 1-2 seconds of each other. Does make me wonder though, we should just add stream "x" being active to the variables to make this slightly easier...