On the backside of the controller, you find a 3G-SDI in and out BNC plug. Route the return feed to the camera through this connection to insert CCU data on the signal.
If you use the Blackmagic 3G-SDI Arduino Shield for camera control the following outputs are supported: 720p50, 720p59.94, 720p60, 1080i50, 1080i59.94, 1080i60, 1080p23.98, 1080p24, 1080p25, 1080p29.97, 1080p30, 1080p50, 1080p59.94 and 1080p60, but the camera doesn´t have to be running the same video format as the program input, so you can use cameras in Ultra HD while the camera protocol is sent over HD signal to the camera.
The RCP Mini controls any Blackmagic camera that supports CCU over the return SDI feed. This includes the Micro Studio Camera 4K, Studio Cameras and the URSA Mini (+ Pro). The CCU data is inserted on the SDI return feed.
The RCP Mini has the same form factor (width and height) as the Sony RCP-1000 series. Depth is slightly larger.
Dimensions (W x H x D): 68 x 244 x 140 mm (top of joystick)
Weight: 0.770 kg
The RCP Mini feature a push button on the top of the joystick that will bring up the source on a local monitor. This can be achieved in three ways:
The device will ship with a great default configuration that make it work out of the box. However, the unit will run on the SKAARHOJ UniSketch OS which will provide a fantastic online configuration tool to change, extend or limit the functionality of the controller including shift levels, controller states and presets to add flexibility and conditions and which ensures new features and hardware supports will be available through software upgrades from SKAARHOJ over time.
This is an example of a RCP Mini with a setup of 4 different states. The functionality we are looking at here is for Encoder1 (Enc1).
By pressing on button 1-4 you select between the 4 different states named "WHITE", "BLACK", "GAMMA" and "CAM". For each of these states you can set the functionality of all the hardware interface components on the RCP Mini.
This allows you to set different functions under different conditions, making it possible for you to configure the RCP Mini just as you would like.
Below we provide some information for setting up the RCP Mini. As the methology is the same as for the RCP the explenation is taken from the RCP page.
Please notice we have recently published a "Strategies for Blackmagic Design Camera Control" white paper with additional information about Blackmagic Design Camera Chains. Please see this document for additional information.
Here we present some of the principles for how you can control cameras via the RCP. One setup does not necessarily rule out another. Please contact us for questions.
Arduino Shield Vs. ATEM
The RCP is able to send CCU data in two ways; either through the Arduino Shields SDI out connector or via a connected ATEM switcher. What you prefer is up to you. Using the ATEM route is known to work with any recent ATEM firmware to this date and doesn't require new cabling, but since an ATEM can only have a limited number of clients connected, it won't scale beyond a few cameras with an RCP dedicated for each camera. Using the SDI in/out to insert CCU data on the return signal is the BMD endorsed way, but it requires you to cable the return feed accordingly through the RCP.
Camera Control via ATEM
The RCP is connected either directly to the ATEM Switcher via ethernet or via a network switch/hub. You need an SDI return feed to the camera (for instance a AUX channel) to relay CCU parameters to the camera from the ATEM Switcher. This setup is similar to using the ATEM Software Control Panel.
Camera Control via Blackmagic Shield
The Blackmagic Arduino Shield makes it possible to relay CCU information to cameras directly without the need of an ATEM Switcher. The RCP is designed to control 1 camera at a time, but it can control multiple cameras if you use a SDI Distribution unit (or something similar like a Videohub), to distribute the SDI CCU control signal to multiple cameras (up to 10).
Camera Control via Blackmagic Shield and ATEM
You can control a camera directly via the Blackmagic Shield while the tally (and more) information from the ATEM is relayed to the camera. For this you need to route an output from the ATEM to the RCP.
With the DB-9 you can connect an external trigger and control external devices. Furthermore you can use the DB-9 connector as GPI in order to relay tally information to cameras connected.
Get the RCP Mini with a 35mm multi turn dial (aluminium knob) instead of the joystick. The RCP Mini controller will be fitted with the joystick, if this option is not selected.
In the manual you can find more information about the configuration, the menu system, joystick override, data channels, cabling and more.
Please also refer to the "Strategies for Blackmagic Design Camera Control" document for additional information.
You either place your order by PayPal or by email and pay by bank transfer - please read the "Pricing, Terms and Conditions" page for more details.
We have tested Blackmagics fiber converter products in general to work with SDI output. This includes the Mini Converter, ATEM Camera Converter, ATEM Studio Converter and ATEM Talkback Converter 4K. The only product we know does not work is the Studio Fiber Converter/Camera Fiber Converter. This product is not compatible with their own 3G-SDI shield which is the component we use inside the RCPs and other products. While the Studio Fiber Converter/Camera Fiber Converter will forward shading data from an ATEM switcher it will not do so for the 3G-SDI shield.
Bottom line is this: We cannot change this situation, only Blackmagic Design can decide to upgrade either the Studio Fiber Converter/Camera Fiber Converter or the 3G-SDI Arduino Shield to make it work. At this point we can suggest that you rather connects a controller to an ATEM switcher which will work as the master for sending out the shading data. You might employ a cheap ATEM switcher for only this purpose.