UniSketch Device Cores
UniSketch Device Cores
To get an overview of all the SKAARHOJ controllers and their Device Core configurations please visit https://cores.skaarhoj.com/
To get an overview of all the SKAARHOJ controllers and their Device Core configurations please visit https://cores.skaarhoj.com/
In 1-4 Binary. Please see the section
Triggering actions from binary inputsin the Installation and Operation Manual
In 1-4 Binary. Please see the section
Triggering actions from binary inputsin the Installation and Operation Manual
8-pin protocol. The CNA-1 may also be needed for protocol conversion on ethernet alone (since Sony cameras may not natively understand SSCP, but only SNP (Sony Network Protocol). With this device core the camera acts as a TCP server and the SKAARHOJ controller connects to it as a TCP client.
8-pin protocol. The CNA-1 may also be needed for protocol conversion on ethernet alone (since Sony cameras may not natively understand SSCP, but only SNP (Sony Network Protocol). With this device core the camera acts as a TCP server and the SKAARHOJ controller connects to it as a TCP client.
SKAARHOJ controllers already support many broadcast devices. Some are very mature and full featured, others still just basic, some are in beta versions and yet others are just planned at this stage. Here is an overview of the available device cores and their states. You add device cores to your controller on cores.skaarhoj.com. Also, please send us your suggestions for more!
In alpha mode a device core is partially implemented. Something will work and can be tested. It’s also likely that it will contain more bugs than a beta or mature device core. It’s very much work-in-progress. Therefore, we invite you to contact us if you are interested in an alpha-state device core. Like with planned device cores we need real world users to inform (and sometimes pay for) our development decisions.
In beta mode a device core is fully implemented and working. However it’s not considered mature yet simply because of time and the likelyhood that some features are still lacking and needs to be fixed.
A device core is promoted to mature state when time and experience tells us that it has a history of functional coherence. It’s probably not perfect - nothing ever will be - but it’s considered stable.
When device cores or actions are “planned” they are introduced on cores.skaarhoj.com for inspiration of the global community of SKAARHOJ UniSketch users. In this phase everything is in a conceptual phase, in other words; nothing actually works yet. A device core will progress to alpha state when enough users or other business arguments promotes it on the development todo list and we begin to implement working features. When a device core is planned and you are interested in it, please tell us about it! We are most likely looking for users who can help us guide (and sometimes pay for) the development. We won’t implement something nobody will ever use.
Third party cores are those device cores which have their functionalities implemented by third parties. To allow such implementation to happen, Skaarhoj controllers run in 'Raw Panel' mode and let external application or hardware to control them. Because of this, we can not expose actions and let you configure the controller using these device cores. They are purely a representation of third party capabilities. You will need to follow instructions given by these third parties to integrate your controller with their solutions.