pepperdash/Essentials
1
0
Fork 0
mirror of https://github.com/PepperDash/Essentials.git synced 2026-02-10 02:05:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Connection based routing (markdown)

hvolmer
2020-02-11 18:12:48 -07:00
parent 88587db424
commit 83b1cae06f
1 changed files with 6 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
Connection-based-routing.md

@@ -2,7 +2,7 @@
#### TL;DR
Routing is defined by a connection graph. A wiring diagram. Route-able devices are sources, midpoints, or destinations. Devices are connected by tie lines. Tie lines represent the cables connecting devices, and are of type audio, video or both. Routes are made by telling a destination to get an A/V/AV route from a source.
Routing is defined by a connection graph. A wiring diagram. Route-able devices are sources, midpoints, or destinations. Devices are connected by tie lines. Tie lines represent the cables connecting devices, and are of type audio, video or both. Routes are made by telling a destination to get an audio/video/combined route from a source.
#### Summary
@@ -35,29 +35,28 @@ All of the above routes can be defined in source list routing tables, covered el
#### Ports
Ports are logical representations of the input and output ports……………………………
Ports are logical representations of the input and output ports on a device.
#### Source
A source is a device at the beginning of a signal chain. For example, a set-top box, or a camera. Source devices typically have only output ports.
Source devices in Essentials must implement IRoutingOutputsor IRoutingSource
Source devices in Essentials must implement `IRoutingOutputs` or `IRoutingSource`
#### Midpoint
A midpoint is a device in the middle of the signal chain. Typically a switcher, matrix or otherwise. Examples: DM chassis; DM-TX; DM-RMC; A video codec. These devices will have input and output ports.
Midpoint devices must implement IRoutingInputsOutputs. Midpoints with switching must implement IRouting.
Midpoint devices must implement `IRoutingInputsOutputs`. Midpoints with switching must implement `IRouting`.
#### Sink
A sink is a device at the end of a full signal path. For example, a display, amplifier, encoder, etc. Sinks typically contain only input ports. They may or may not have switching, like a display with several inputs. Classes defining sink devices must implement IRoutingSinkNoSwitching or IRoutingSinkWithSwitching.
A sink is a device at the end of a full signal path. For example, a display, amplifier, encoder, etc. Sinks typically contain only input ports. They may or may not have switching, like a display with several inputs. Classes defining sink devices must implement `IRoutingSinkNoSwitching` or `IRoutingSinkWithSwitching`.
#### Tie-line
A tie-line is a logical representation of a physical cable connection between two devices. It has five properties that define how the tie-line connects two devices. A configuration snippet for a single tie line connecting HDMI output 1 on a Cisco RoomKit to HDMI input 1 on a display, carrying both audio and video, is shown below.
```
```json
{
"sourceKey": "ciscoSparkPlusCodec-1",
"sourcePort": "HdmiOut1",