|
|
In Raw Panel mode the controller will work as a TCP Client connecting to a server IP address on port 9923. The server receives simple action commands when buttons, encoders, faders etc are activated. In return the server sends button colors and display content. The API is documented as “UniSketch TCP Client†on our GitHub repository. In Raw Panel mode, all the logic is placed on the server, which is typically a custom written software application. |
|
|
|
A example sketch utilising the "UniSketch Raw Panel" Device Core by using sytem action such as "UniSketch Raw Panel: Flag". To be used in combination with "2x8 GPIO TCP Server" configuration to link two SKAARHOJ controllers together. |
|
|
|
A example sketch utilising the "TCP Server" Device Core by using sytem action such as "System: Flag" with Feedback Flag settings as well. To be used in combination with "2x8 GPIO UniSketch TCP Client" configuration to link two SKAARHOJ controllers together. |
|
|
|
A example configuration for routing with "Joystick Override". This is used for RCPs connected to a KUMO where you want to keep track of the order of GPI INs in a queueing system and let routing fallback accordingly. The "Hold Group x" action is used for routing instead of just "Hold Down". When no GPIs are held down the routing will fall back to the routing set in "Virtual 1" (Input 16 to Output 1). |
|
|
|
Reflects ATEM 1ME Program Source 1-8 on GPI Out 1-8. Sets ATEM 1ME Program Source 1-8 on GPI In 1-8. |
|
|
|
Just like the "ATEM Connectivity" configuration but with a extra GPIO module. Reflects ATEM 1ME Program Source 1-16 on GPI Out 1-16. Sets ATEM 1ME Program Source 1-16 on GPI In 1-16. |
|
|
|
Input 1-4 control Program select 1-4, Input 5 controls Audio Up on Cams 1-4, Input 6 controls Audio Down on Cams 1-4, Input 7 controls Audio Up on Master, Input 8 controls Audio Down on Master |
|
|
|
A system for a PTZ operator with 2 x SmartView Duo monitors and 1 x SmartView 4K monitor. ATEM provides tally and the AW-RP120/AW-RP150 is used for PTZ control. The goal is to get tally on the monitors from the ATEM and on the SmartView 4K tally should only be enabled when a selected camera on the AW-RP120/15 matches the same camera in the ATEM. Routing to the SmartView 4K based on selected camera on the AW-RP120/15 is not part of this configuration. Please see https://github.com/SKAARHOJ/Support/tree/master/Manuals/Tutorials for a Tutorial PDF |
|
|
|
Configuration for setting PRV/PGM on ATEM based on PRV/PGM state on TriCaster TC1. Utilizes Virtual Hardware Components. PRV/PGM 1-8 are set - can be extended. |
|
|
|
Configuration using the "In1-4 Binary" component to do ATEM AUX routing based on GPI from the Panasonic AW-RP50 and AW-RP120. Routing actions can be changed to Blackmagic VideoHub, AJA KUMO Router and more. |
|
|
|
An example configuration of using Inputs 1-8 to send red/green GPI tally to 4x BMD cameras. Meant to be paired with an Eth-SDI Link for SDI output. |
|
|
|
A example configuration for routing with the Panasonic AW-RP1xx. Configuration performs a video routing on AJA KUMO Routers by utilizing Virtual Hardware Components. Routes camera 1-10 for Input 1-10 to Output 1 on the KUMO. Routing actions can be changed to include additional groups or to perform routing on other Device Cores. Control via IP. |
|
|
|
A example configuration for routing with the Panasonic AW-RP1xx. Configuration performs source selection on a Blackmagic ATEM Switcher for AUX Channel 1-2 by utilizing Virtual Hardware Components. Sets sources 1-10 on AUX1 for Panasonic Group 1. Sets sources 11-20 on AUX2 for Panasonic Group 2. Routing actions can be changed to include additional groups or to perform routing on Blackmagic VideoHub, AJA KUMO Router and more. Control via IP. |
|
|
|
Test Configuration for PTZ Cruise Control via Foot Pedal |
|
|
|
A example sketch utilising Virtual Hardware Components to illustrate sytem actions such as Synthesized Trigger, Flags and Flags Conditions. Sets GPI Outs based on specific Routing Conditions. |
|
|
|
A example configuration with routing of several sources and fallback routing when GPI1 and GPI2 are closed/released. |
|
|
|
A example configuration for routing with "Joystick Override". This is used for RCPs connected to a VideoHub where you want to keep track of the order of GPI INs in a queueing system and let routing fallback accordingly. The "Hold Group x" action is used for routing instead of just "Hold Down". When no GPIs are held down the routing will fall back to whichever routing the VideoHub had before GPIs where triggered. In other words it is not set in this config. |
|
|
|
A example configuration for routing with "Joystick Override". This is used for RCPs connected to a VideoHub where you want to keep track of the order of GPI INs in a queueing system and let routing fallback accordingly. The "Hold Group x" action is used for routing instead of just "Hold Down". When no GPIs are held down the routing will fall back to the routing set in "Virtual 1" (Input 16 to Output 1). |
|
|
|
Special Raw Panel configuration to work best with the SKAARHOJ Blue Pill. |
|