Streaming fallback

From SOUND4wiki
Revision as of 14:31, 5 November 2020 by Camille (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This shows a way to have a fallback Streaming on SOUND4 Stream x2/x4/x8 processors.

Principle

This will use the onboard Ethernet to send and receive Livewire GPIO.

The Main process will send a GPO (called GPI in Livewire) to inform when it detects no Audio.

The Fallback process will receive this information as a GPI (called GPO in Livewire) and Enable the Streaming accordingly.

General Setup

Use 2 computers each with a SOUND4 processor and Streaming extension.

Provide both with audio (either Livewire/AES67 input, or Automation software playing directly on it).

Configure the same streams on both cards, but put only first On.

The 2 cards' Ethernet ports must be on the same network, and could be directly connected without a switch. They must be configured either in DHCP or with a fixed IP.

This needs the SOUND4 Streaming Extension 2.4.16 to detect audio presence.

NOTE: to have working GPIOs on cards, you need a recent enough board version (>=1.5) and driver (Windows>=2020-07-15, Linux>=2.14) and server (>=4.1.77).

Main setup

In Setup->GPIO, configure one Pin of One Livewire Port GPI to send Stream Audio Detected Equal to No, like this for instance:

Streaming Fallback Livewire GPI setup.png

You may add a Delay Before Action to limit the concurrent streaming.

Which results in this:

Streaming Fallback Livewire GPI.png

Fallback setup

In Setup->GPIO, configure the Livewire GPO Port 1 Config with Livewire snake mode. Supposing that main process board has IP 192.168.4.82 and you used Livewire port 1 for main, you need to put "192.168.4.82/1"

Then, on the same pin number you configured on the Main processor, for Action select "Stream General" and Value "On" and for Action Off select "Stream General" and Value Off.

Streaming Fallback Livewire GPO setup.png


Which results in this:

Streaming Fallback Livewire GPO.png

Advanced error handling

We do not have a way to check a heartbeat to detect if the Main processor is shutdown and does not send updates, so there is currently no way to start the Fallback in this case.

However, you can start it also if the Main stream is software put Off.

For this, add a second pin to the Main processor sending "Stream Status" equal to "Off".

On the Fallback, add a rule on the pin with Action "Stream general" value "On".

This way, setting the Stream General to Off on the main will automatically start the Fallback also.