You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<th*ngFor="let bus of socketService.busOptions">{{bus.label}}</th>
485
+
<th*ngFor="let bus of socketService.busOptionsVisible">{{bus.label}}</th>
485
486
<thstyle="min-width: 100px;">Name</th>
486
487
<th></th>
487
488
<thstyle="min-width: 200px;">Description</th>
@@ -490,7 +491,7 @@ <h3>
490
491
</thead>
491
492
<tbody>
492
493
<tr*ngFor="let device of socketService.devices; index as index" [class.text-muted]="!device.enabled">
493
-
<td*ngFor="let bus of socketService.busOptions" [style.background-color]="deviceBusColors[device.id].includes(bus.id) ? bus.color : '#FFFFFF'"></td>
494
+
<td*ngFor="let bus of socketService.busOptionsVisible" [style.background-color]="deviceBusColors[device.id].includes(bus.id) ? bus.color : '#FFFFFF'"></td>
494
495
<td>
495
496
<small><b>{{ index + 1 }}</b></small> {{ device.name }}
By default busses are unlinked. That means the device will be (for example) in PVW if it is in PVW in <b>any</b> Device Source. All busses you select here will only be in that bus if it is in PVW across <b>all</b> Device Sources.
639
+
By default busses are unlinked. That means the device will be (for example) in Preview if it is in Preview in <b>any</b> Device Source. By linking, all busses you select here will only be in that bus within Tally Arbiter if it is in Preview across <b>all</b> Device Sources.
Copy file name to clipboardExpand all lines: docs/docs/usage/sections/sources.md
+38-30
Original file line number
Diff line number
Diff line change
@@ -6,49 +6,35 @@ sidebar_position: 2
6
6
Sources represent all of the tally data that is generated. This is usually your video switcher or mixing software. Multiple sources can be added and they can all be different types.
7
7
8
8
The following source types are supported:
9
-
*TSL 3.1/5.0 UDP/TCP (Ross switchers, Streamstar, FOR-A, etc. - any device that uses the TSL UMD protocol)
9
+
*Analog Way Livecore Image Processors
10
10
* Blackmagic ATEM
11
11
* Blackmagic VideoHub
12
+
* Grass Valley Contribution Tally
13
+
* Newtek Tricaster
12
14
* OBS Studio
15
+
* Open Sound Control (OSC)
16
+
* Panasonic AV-HS410
13
17
* StudioCoast VMix
18
+
* Riedel SimplyLive
14
19
* Roland Smart Tally
15
20
* Roland VR-50HD-MKII
21
+
* Ross Vision (through GV Contribution Tally Protocol)
16
22
* Ross Carbonite/Carbonite Black/Carbonite Black Solo/Carbonite Ultra/Graphite
17
-
* Newtek Tricaster
18
-
* Open Sound Control (OSC)
19
-
* Panasonic AV-HS410
20
-
* Analog Way Livecore Image Processors
21
-
* Riedel SimplyLive
23
+
* TSL 3.1/5.0 UDP/TCP (Ross switchers, Streamstar, FOR-A, etc. - any device that uses the TSL UMD protocol)
22
24
23
25
When you add a source and the connection to the tally source (video switcher, software, etc.) is successfully made, the source will be green. If there is an error, the source will be red. Look at the logs for more error information.
24
26
25
-
## TSL 3.1 UDP/TCP
26
-
Your switcher or service that uses this protocol must be configured to send the data to Tally Arbiter at the port you specify.
27
+
## Analog Way Livecore Image Processors
28
+
You will need the IP address of the device, and the port (standard port is 10600).
27
29
28
30
## Blackmagic ATEM
29
31
You will need the IP address of the ATEM. The ATEM can only have 5 simultaneous connections, so you may need to disconnect another connection in order for Tally Arbiter to connect to the ATEM.
30
32
31
33
## Blackmagic VideoHub
32
34
You will need the IP address of the VideoHub. You can choose to have any destination be configured as a preview bus, program bus, or both. Enter multiple destination routes by separating them with commas.
33
35
34
-
## OBS Studio
35
-
For OBS Studio v27 (or older) the `obs-websockets` plugin must be installed and configured in order for Tally Arbiter to connect. You can get the plugin here: https://github.com/Palakis/obs-websocket/releases.
36
-
37
-
For OBS Studio v28 and later is `obs-websockets` included with OBS Studio. Note that the included `obs-websockets` in OBS Studio uses port 4455. This will cause a port conflict with TallyArbiter. In OBS Studion can an alternative port be configured in Tools -> WebSocket Server Settings. An alternative is to re-configure Tally Aribiter with another port by editing the [config file](../../usage/control-interface.md).
38
-
39
-
You will need to supply the IP address, port, and password configured in the OBS Websockets plugin.
40
-
41
-
## StudioCoast VMix
42
-
You will need the IP address of the computer running VMix.
43
-
44
-
## Roland Smart Tally
45
-
You will need the IP address of the Roland switcher.
46
-
47
-
## Roland VR-50HD-MKII
48
-
You will need the IP address of the Roland switcher.
49
-
50
-
## Ross Carbonite Models
51
-
You will need the IP address of the Ross Carbonite switcher. Your Carbonite must be configured to send the data to Tally Arbiter at the port you specify. All Ross products use the TSL 3.1/5.0 protocols, however this specific source type allows you to process tally information by specific supported busses (ME1, MME1, Auxes, etc.) regardless of the "OnAir" setting that is configured on the Carbonite itself.
36
+
## Grass Valley Contribution Tally
37
+
It's an older protocol sir, but it checks out. Any Grass Valley switcher that uses this protocol. Choose whether the data is arriving via TCP or UDP, and the port you are sending data on.
52
38
53
39
## Newtek Tricaster
54
40
You will need the IP address of the Tricaster.
@@ -66,12 +52,34 @@ OSC paths must be one of the following:
66
52
67
53
The device source address should be sent as an integer or a string. Send one argument of any type (integer, float, or string). If you send multiple arguments, they will be ignored.
68
54
55
+
## OBS Studio
56
+
For OBS Studio v27 (or older) the `obs-websockets` plugin must be installed and configured in order for Tally Arbiter to connect. You can get the plugin here: https://github.com/Palakis/obs-websocket/releases.
57
+
58
+
For OBS Studio v28 and later is `obs-websockets` included with OBS Studio. Note that the included `obs-websockets` in OBS Studio uses port 4455. This will cause a port conflict with TallyArbiter. In OBS Studion can an alternative port be configured in Tools -> WebSocket Server Settings. An alternative is to re-configure Tally Aribiter with another port by editing the [config file](../../usage/control-interface.md).
59
+
60
+
You will need to supply the IP address, port, and password configured in the OBS Websockets plugin.
61
+
69
62
## Panasonic AV-HS410
70
63
You will need the IP address of the switcher. Multicast must also be enabled on the switcher and your network in order to receive the tally data, therefore Tally Arbiter and the Panasonic device must reside on the same subnet.
71
64
72
-
## Analog Way Livecore Image Processors
73
-
You will need the IP address of the device, and the port (standard port is 10600).
74
-
75
65
## Riedel SimplyLive
76
66
You need to configure TSL in the SimplyLive backend to send the data to Tally Arbiter at the port you specify.
77
-
Uses an TSL v5 UDP connection internally.
67
+
Uses an TSL v5 UDP connection internally.
68
+
69
+
## Roland Smart Tally
70
+
You will need the IP address of the Roland switcher.
71
+
72
+
## Roland VR-50HD-MKII
73
+
You will need the IP address of the Roland switcher.
74
+
75
+
## Ross Vision (through Contrib Tally)
76
+
Some of Ross's older Vision models use the Contribution Tally protocol instead of TSL.
77
+
78
+
## Ross Carbonite Models
79
+
You will need the IP address of the Ross Carbonite switcher. Your Carbonite must be configured to send the data to Tally Arbiter at the port you specify. All Ross products use the TSL 3.1/5.0 protocols, however this specific source type allows you to process tally information by specific supported busses (ME1, MME1, Auxes, etc.) regardless of the "OnAir" setting that is configured on the Carbonite itself.
80
+
81
+
## StudioCoast VMix
82
+
You will need the IP address of the computer running VMix.
83
+
84
+
## TSL 3.1 UDP/TCP
85
+
Your switcher or service that uses this protocol must be configured to send the data to Tally Arbiter at the port you specify.
0 commit comments