Looking at registers for states and shift levels, using memory groups, multiple shift levels, advanced 4-way buttons, all by examples from a typical PTZ Fly configuration. Then on to creating a NewTek+Panasonic cameras combined configuration on the controller from scratch. Not everything is going totally smooth, but that’s life and the session reveals in all honesty how configuration often is a bit forth and back to find the way to make things work using the basic tool box of UniSketch.

Summary: The basic problem in this video is how to combine multiple device cores for PTZ control. Kasper will show how States can be used to help changing between camera brands along with the camera selector. It’s advanced because it shows how you can cleverly use the framework features of UniSketch to create this kind of advanced integration of multiple PTZ camera brands. First, a PTZ Fly is analysed for it’s default configuration. This includes discussing memory groups for camera selection (when multiple values is put into memory AA), an advanced extensions of the concept of memories from lesson 12. An advanced four-way button on the PTZ fly is also explored - the “Menu” button of the PTZ Fly. This is a four-way button that both changes states in two different registers as well as shift level when pressing the sides of the button. We are even discussing a bug in the implementation that makes the shift level go one too far (it should cycle only to the value 2 instead of 3). This key is an example of an advanced combination of Force HWC type and Transformations. This leads us to discuss State registers - a way to have multiple different states on a controller. In this case, the global state applies to the top encoders while a local state register is applied to the 6 buttons used for camera selection.
After discussing the default configuration for PTZ Fly, we will create a completely blank one including just two device cores: Panasonic PTZ and NewTek PTZ. After the firmware is updated we look at the serial monitor output to confirm the IP addresses. Then we will create a state for NewTek (default) and a state for Panasonic (state 1). After doing that Kasper assigns actions to the joystick in each state; the NewTek PTZ actions and the Panasonic PTZ actions respectively. The camera selection buttons are configured with both state selection as well as camera selection. This reveals a clash between camera 1 and 2 in the NewTek realm and Panasonic Realm. It turns out after some trial and error that we need to keep a paradigm of camera 1,2,3,4 instead of camera 1,2 and 1,2. This highlights that certain things are still candidates for improvements and easier handling in UniSketch while it still demonstrates the flexibility of the current software to work around even the most complex issues.
Finally Kasper demonstrates how we can still keep individual actions for each camera in the menus, even if they are very different (one being VISCA - NewTek - and another being proprietary HTTP request protocol - Panasonic). To obtain a menu function of the parameters, Kasper uses multiple shift levels to access multiple menu levels - this was necessary since states were already used for distinguishing between the cameras. It’s also evident that shift levels fall back to the default unless an action is defined which leads us to add “System: No Action” to encoders we want to remain blank.
Finally Kasper colors the panel so it’s easy to see the difference between the shift levels. Also, to still have access to presets, Kasper adds a new shift register to take care of that independently of the shift register used for the menu on the top encoders.
Generally this episodes is a tour-de-force in how you can use shift and state in various combinations to create advanced and dynamic behaviours on your SKAARHOJ panels.