The IP address or host name of CCS one or MCP 450 on the network reachable from the iPhone or iPad.
DeviceJockey Interfaces
Grass Valley Camera Interface
Control camera functions and reflect their current values on a custom DeviceJockey panel.
System architecture
CCS one or MCP 450 connects both networks.
Grass Valley cameras and control panels communicate within the C2IP camera network. A CCS one or MCP 450 provides the XML gateway to the public network. DeviceJockey connects to that gateway, not directly to an individual camera.
The gateway is the interface target.
Use the IP address and XML Control port of CCS one or MCP 450 in the DeviceJockey interface settings.
Setup
Start XML Control before connecting.
1
Prepare the gateway
Open CCS one or MCP 450 and start XML Control.
2
Add the interface
Add a GV Camera interface to the scene containing your camera-control panel.
3
Enter gateway settings
Configure host, port, application name, protocol version, and the required response level.
4
Enable interfaces
Switch on interface connections and confirm that DeviceJockey appears in the XML Control client list.
Interface settings
Identify DeviceJockey to the XML gateway.
The port configured for XML Control in the Grass Valley gateway.
The client name with which DeviceJockey identifies itself to the gateway.
The XML protocol version expected by the gateway configuration.
Select Never, Always, or Error only according to how the gateway should return command responses.
Devices and functions
Select from information provided by the gateway.
Commands and events identify a camera by its camera number or device name, or by its device ID. When the interface is connected, the selection buttons can load connected devices and available functions from the gateway. The function list also provides the value range expected by Grass Valley.
Choose the camera.
Select a connected camera from the gateway list or enter its camera identifier manually. Swaps can make the selection dynamic.
- Address by
- Camera number or device name, or device ID
- Source
- Connected device list
Choose the camera parameter.
Select the Grass Valley function and use its documented range when configuring Value or Range behavior.
- Examples
- Color matching and camera settings
- Source
- Function information from the gateway
Use the provided ranges.
The value range is specific to the selected Grass Valley function. Do not assume that every camera parameter uses the same minimum and maximum.
Core commands
Send fixed, continuous, or relative values.
Send a configured value to a selected function on a selected camera.
Map the position of a slider or rotary item between the minimum and maximum expected by the camera function.
Change the current camera value by a relative amount instead of setting an absolute value.
Ask the user for a value when the command runs and send the entered value to the camera function.
Requests and subscriptions
Retrieve current values and gateway information.
Ask the gateway for the current value of a selected camera function.
Subscribe to updates for a selected camera function.
Subscribe to updates associated with the selected device.
Request available information for a selected Grass Valley function.
Request information about devices connected through the gateway.
Select a device from the connected-device list and write its chosen identifier to a Swap.
Events and feedback
Reflect the confirmed camera state.
Grass Valley events evaluate values returned through the interface. Use matching events so a panel follows changes made from DeviceJockey, an OCP, or another controller in the camera system.
React when the selected device and function report the configured value.
Map the current camera value into the range of a slider, rotary item, or another supported property.
Display a returned function value or option as an item label. Supported formatting can use a Script.
Allow or protect supported item interaction based on a matching Grass Valley value.
React to supported CCS API grouping and naming information.
A command is not feedback.
Use an event or a value request to show what the camera system has confirmed, including changes made at an OCP.
Example
Control and monitor camera red gain.
1
Add a slider
Create a slider on a panel in the scene containing the connected GV Camera interface.
2
Add GV Range
Assign a GV Range command to the Slider action and select the camera and red-gain function.
3
Use the function range
Copy the minimum and maximum shown for that function into Slider Bottom and Slider Top.
4
Add feedback
Add a GV Range event to the Slider action using the same camera, function, minimum, and maximum.
In Live Mode, moving the DeviceJockey slider changes red gain. When red gain changes elsewhere, the event moves the slider to the current value reported by the camera system.
Advanced commands
Work with raw XML and CCS metadata when required.
Send a complete raw XML message to the gateway for functions not covered by a standard command.
Insert a mapped item value into the {$value} placeholder of a raw XML message.
Send supported CCS API grouping information.
Send supported CCS API naming and location information.
Raw XML requires protocol knowledge.
Prefer the standard device and function commands when they cover the required camera control.
Troubleshooting
If the GV Camera interface does not work.
Check XML Control.
Confirm that XML Control is running on CCS one or MCP 450.
Verify host and port.
Compare the DeviceJockey interface settings with the current public-network settings of the gateway.
Check the client list.
A connected DeviceJockey client should appear in the XML Control window.
Check network reachability.
The iPhone or iPad must be able to reach the public-network side of the gateway.
Refresh device information.
Reconnect before opening device and function lists when the camera system has changed.
Compare function and range.
Use the exact function identifier and the minimum and maximum provided for that function.
Check the addressing method.
Confirm whether the command or event uses camera number or device name, or device ID.
Review the response level.
Use the response behavior required for the gateway workflow and inspect the interface log for errors.