AV Sources

In Space CE configurations, the AV Sources section defines the sources that can be shared to room destinations. Each AV Source object carries the rendering information for the touch-panel interface (label, icon, help text) and the routing actions that fire when the source is selected. You configure this section whenever a room gains a new input, such as a room PC, a lectern laptop plate, a wireless presentation appliance, or a document camera.

Key concepts

Term	Meaning
Encoder	The device (or device endpoint) that captures a source’s video and audio and makes it available for routing. On AVoIP systems this is a network encoder; on a matrix system it may be an input on the matrix.
Video sync	The presence of a live video signal on an input. Space CE uses sync detection to know when a laptop has been plugged in, or when a source has gone away.
Matrix vs switcher	A matrix routes any input to any output independently, so a matrix input switch only fires when the destination has a matching output switch on the same matrix device. A switcher selects one input for its single output, so a switcher input switch fires on any routing of that source.

Field reference

Field	Description	Required	Default
ID	Unique identifier for the source.	Yes	-
Label	Display label shown on the interface.	Yes	-
Remote Label	Label used when the source is presented on a linked (remote) room’s interface. Falls back to Label if unset.	No	Label
Type	Source category. Determines the icon shown on the interface.	Yes	-
Encoder ID	Device ID of the encoder whose stream is shared when this source is routed.	No	-
Secondary Encoder ID	Device ID of a secondary encoder to route alongside the primary (e.g. a separate audio or content encoder).	No	-
Audio Encoder ID	Device ID of a dedicated audio encoder for this source.	No	-
Audio Source ID	ID of the audio fader associated with this source, used for volume rendering and control.	No	-
Has Audio	Whether the source carries audio.	No	true
Selectable Without Sync	Allows the source to be selected even when no video sync is detected.	No	true
USB Routable	When enabled and routed to a USB Routable destination, the source’s USB devices are paired to the destination’s USB devices.	No	false
Visibility	Controls when the source appears in the interface list (e.g. Always Visible).	No	Always Visible
Mutually Exclusive Group	Group name; selecting one source in a group affects availability of others in the same group.	No	-
Condition	Expression string that gates routing for this source. See Conditional Routing.	No	(empty)
Help Text	Help text shown on the interface.	No	-
Input Switch	List of switching actions performed when the source is routed. See below.	No	-
Video Sync Devices	List of sync-detection definitions. See below.	No	-
Available Destinations	List of destination entries (each with a Destination) restricting where this source may route.	No	-
Destination Groups	Groups the source can be routed to. Only used in rooms with AV Destinations / Destination Groups defined.	No	-

Input switches

Input switches define the switching actions triggered when the source routes to a destination. A matrix input switch fires only when routed to a destination that has a matching output switch on the same matrix device. A presentation-switcher input switch fires on any routing of the source.

Input switch fields

Field	Description	Required	Default
Switcher ID	Device ID of the switching device that performs the action.	Yes	-
Type	Switch type. See the full set below.	Yes	-
Input	The target input on the switching device. Used by the standard routing types.	Conditional	-
Value	The payload for the non-standard types.	Conditional	None
Gateway Controlled	Whether the switch is actioned through a gateway rather than directly.	No	false
Condition	Expression string that gates this specific switch. See Conditional Routing.	No	(empty)
ID	Optional identifier for the switch entry.	No	-

Input switch types

The Type field accepts the following values:

• Audio
• Video
• AudioVideo
• Usb
• Preset Recall
• Stream Set

Which fields to use and when

• Switcher ID and Type are always required on every input switch, regardless of type.
• Standard routing types (Audio, Video, AudioVideo) use the Input field to name the input to select. Set Input and leave Value unset for these types.
• Non-standard types (Usb, Preset Recall, Stream Set) use the Value field to carry their payload (for example a preset name or a stream identifier). Set Value and leave Input unset for these types. Value defaults to None when omitted.

Input values

Common examples of input identifiers (the exact set a device honours is driver-dependent):

DisplayPort1, DisplayPort2, HDMI, Hdmi1, Hdmi2, Hdmi3, Hdmi4, Android, AirMedia, InputA, InputB, InputC, InputD, InputE, InputF, Network, Stream1, Stream2, and numeric inputs such as 1 through 16. This is not a closed set: a driver may accept other identifiers.

Video sync devices

Video sync devices define how sync is detected for the source. A source is treated as synced if any listed device reports sync. Sync-detection capability varies by device.

Video sync device fields

Field	Description	Required	Default
Device ID	Device that reports sync detection. The key Sync ID is accepted as an alias for Device ID.	Yes	-
Device Input	The input on the device to watch for sync.	No	-
ID	Optional identifier for the sync entry.	No	-

Worked example

A room PC connected by HDMI on its own encoder, plus a document camera that recalls a DSP preset and sets a decoder stream when routed.

{
  "AV Sources": [
    {
      "ID": "source.pc",
      "Label": "PC",
      "Type": "PC",
      "Encoder ID": "dev.encoder.pc",
      "Has Audio": true,
      "Selectable Without Sync": true,
      "Visibility": "Always Visible",
      "Input Switch": [
        { "ID": "pc.switch.1", "Switcher ID": "dev.switcher.1", "Input": "Hdmi1", "Type": "AudioVideo" }
      ]
    },
    {
      "ID": "source.doc.cam",
      "Label": "Visualiser",
      "Type": "Document Camera",
      "Encoder ID": "dev.encoder.1",
      "Input Switch": [
        { "ID": "doccam.preset", "Switcher ID": "dev.dsp.1", "Type": "Preset Recall", "Value": "preset.present" },
        { "ID": "doccam.stream", "Switcher ID": "dev.decoder.1", "Type": "Stream Set", "Value": "MANUAL.6" }
      ]
    }
  ]
}

In this example the PC uses an AudioVideo switch with Input set to Hdmi1. The Visualiser stacks two non-standard switches: a Preset Recall and a Stream Set, each carrying its payload in Value with no Input.

Related Articles

• AV Destinations
• Default Routes and Hot Plug Routes
• Conditional Routing
• Creating a Space CE Template