Devices

Onlyview can interact with a number of hardware devices via plug-ins. These devices are accessible in the Content dock -> OBJECTS tab.

PJLink can turn videoprojectors on and off; MatrixSwitcher lets you control the patching of video switcher from timelines or any other place.

There is also built-in support for the Elgato StreamDeck - you don’t need to create a device to use it.

Art-Net

Overview

The Art-Net device enables OnlyView to send and receive DMX512 lighting control data over Ethernet networks using the Art-Net protocol. Art-Net is an industry-standard protocol that allows lighting controllers, dimmers, and other DMX devices to communicate over standard network infrastructure.

Category: Communication Device
Hardware Requirements: Network interface connected to Art-Net network
Software Requirements: None (protocol handled internally)
Compatibility: Art-Net protocol version 3

Setup and Configuration

Network Configuration

Network Interface: Select the network interface that connects to your Art-Net network.

Net and Sub-Net: Art-Net uses a hierarchical addressing scheme: - Net: The top-level network identifier (0-127) - Sub-Net: Sub-network within the Net (0-15) - Combined with Universe (0-15), this creates the full Art-Net address

Emission Settings

Enable Emission: When checked, OnlyView will actively send Art-Net data to the network.

Sending Method: - Prefer unicast: Sends N times the data, once for each listener that registered for this address. Note that you don’t have to know the addess of the receiver: using the Art-Net protocol, OnlyView will know who is interested by this addess. - Always broadcast: Sends data to all devices on the network segment. This can flood the network.

Note that above a certain number of registered listeners, OnlyView forcefully uses broadcast.

Sending Frequency: Rate at which Art-Net packets are transmitted when data is changing (1-44 Hz). Higher frequencies provide smoother dimming but increase network traffic.

Idle Frequency: Rate at which Art-Net packets are sent when data is not changing (1-44 Hz). Maintains connection with receiving devices.

Universe Configuration

Configure up to 4 Art-Net universes (ports) simultaneously: - Universe: Local universe number (0-15) - Each universe can carry 512 DMX channels - Universes are combined with Net and Sub-Net to form the complete Art-Net universe address

Reception Configuration

Enable Reception: Allows OnlyView to receive Art-Net data from other controllers on the network.

Monitor Universes: Specify which Art-Net universes to monitor for incoming data.

Actions

Available Actions

Start DMX Record: Begin recording incoming Art-Net data to create cue sequences. - Parameters: None - Usage: Useful for capturing lighting states from other controllers

Stop DMX Record: Stop recording Art-Net data. - Parameters: None - Usage: Ends the current recording session

Send DMX Values: Transmit specific DMX channel values via Art-Net. - Parameters: Universe, Channel, Value - Usage: Send specific lighting commands from timeline cues

Timeline Integration

Art-Net actions can be triggered from Command Cues on any timeline: - Add a Command Cue to a timeline layer - Set the cue’s device action to the desired Art-Net action - Configure action parameters as needed - The action will execute when the timeline playhead reaches the cue

It’s possible to record input data (usually from a lighting console), then replay it in place of the console: - Place a Start Record CommandCue on the timeline, and select the path to the output .ovdmx file - Place a Stop Record CommandCue later on the timeline - Start the show - At the end, the .ovdmx will be created. Import it in the medialist - Drag&drop the media in the timeline - Edit the cue (double-clic) and select the output device (usually the one used for recording) - Remove the CommandCues (or disable their layer) to avoid re-recording. - When playing the show, Producer will now re-play the Art-Net content.

User Interface

Device Widget

The Art-Net device widget provides real-time monitoring and control capabilities:

Status Indicators: - Network Status: Shows connection status to the Art-Net network - Transmission Status: Indicates when data is being sent - Reception Status: Shows when Art-Net data is being received

Universe Monitors: Displays real-time channel values for monitored universes with: - Channel numbers (1-512) - Current DMX values (0-255) - Visual level indicators

ActionGraph Nodes

Art-Net Get Channel: Retrieves current value of a specific Art-Net channel - Inputs: Device, Universe, Channel - Outputs: Value (0-255) - Properties: Device selection, universe number, channel number

Art-Net Send Channel: Sends a value to a specific Art-Net channel - Inputs: Device, Universe, Channel, Value - Outputs: None - Properties: Device selection, universe number, channel number

Art-Net Copy Universe: Copies data from one universe to another - Inputs: Source Device, Source Universe, Target Device, Target Universe - Outputs: None - Properties: Source and target device/universe configuration

HTTP Client

The HTTP Client device allows OnlyView to send HTTP requests to external web servers and APIs for integration with web services, REST APIs, and other HTTP-based systems.

Setup

To configure an HTTP Client device:

  1. Access the Devices section
  2. Click Add Device and select HTTP client
  3. Configure the device settings:
    • Device name: Enter a descriptive name for this HTTP client
    • Base URL: The server address (e.g., http://192.168.1.200:8000)
    • Authentication: Optional HTTP authentication settings
      • Method: Choose “None” or “Basic”
      • Login: Username for Basic authentication
      • Password: Password for Basic authentication

HTTP Messages

The HTTP Client device can send multiple predefined messages, each with its own configuration:

Message Configuration

For each message, configure: - Name: User-friendly name for the message - Endpoint: The specific path to call (e.g., /setStatus) - Method: HTTP method - GET, POST, or PATCH - Output data (POST): Request body data for POST/PATCH requests (e.g., JSON data like {on: "1"})

Response Validation

Each message can optionally validate the server response: - Check result: Enable to validate the response content - Expected result: Text that must be present in the response for success (e.g., {success: "1"})

The device widget in UserScreens will show green when requests succeed (HTTP 200) and the expected response is received (if validation is enabled). Otherwise, it appears red.

Periodic Status Checks

Enable automatic periodic status checks: - Periodically check status: Enable automatic checking - Period: Check interval in seconds (1-3600) - Message to send: Which configured message to use for periodic checks

Actions

The HTTP Client device supports one action type:

Send HTTP Message

Sends one of the configured HTTP messages to the target server.

When creating this action, select which predefined message to send from the dropdown list.

ActionGraph Node

The HTTP Client device includes an ActionGraph node for integration into automation workflows:

HTTP Sender Node

Properties: - Device: Reference to the HTTP Client device configuration

Input Slots: - Endpoint: HTTP endpoint path (string) - Verb: HTTP method like GET, POST, etc. (string) - Body: Request body content (string)

Input Events: - Send request: Triggers the HTTP request

Output Slots: - Error code (200 : OK): HTTP status code from response (integer) - Data: Response body content (string)

Output Events: - Next (immediately after): Fired immediately when request is sent - On success: Fired when request completes successfully (HTTP 200) - On error: Fired when request fails or returns an error status

The node sends an HTTP request using the connected device configuration when the “Send request” input event is triggered. The input slots allow you to dynamically specify the endpoint, HTTP method, and request body, overriding the device’s predefined messages.## HTTP Client

HTTP Server

The HTTP Server device allows OnlyView to receive HTTP requests from external systems, enabling integration with web applications, control panels, and other HTTP clients that need to trigger actions or send data to OnlyView.

Setup

To configure an HTTP Server device:

  1. Access the Devices section
  2. Click Add Device and select HTTP server
  3. Configure the device settings:
    • Device name: Enter a descriptive name for this HTTP server
    • Port: The TCP port to listen on (up to 66000)

The HTTP server will listen on all network interfaces (0.0.0.0) on the specified port, making it accessible from any device on the network.

ActionGraph Node

The HTTP Server device provides an ActionGraph node for handling incoming HTTP requests in automation workflows:

HTTP Server Receiver Node

Properties: - Device: Reference to the HTTP Server device configuration - Endpoint (regex): Regular expression pattern to match incoming request paths - Example: /.* matches all paths - Example: /test matches exactly “/test” - Example: /test/.* matches “/test” and any sub-paths

Output Slots: - Endpoint: The full path of the received HTTP request (string) - Verb: HTTP method of the request (GET, POST, PUT, PATCH, DELETE) (string) - Body: Request body content (string)

Output Events: - Message received: Fired when an HTTP request matching the endpoint pattern is received

The node monitors incoming HTTP requests to the configured server device. When a request is received that matches the endpoint regex pattern, the node outputs the request details and triggers the “Message received” event.

Custom UI

The HTTP Server node displays helpful information in the ActionGraph editor: - Shows example endpoint patterns - Displays regex syntax help - Shows any regex validation errors

Use Cases

The HTTP Server device is commonly used for:

Technical Notes

Matrix Switcher

Overview

The Matrix Switcher device enables OnlyView to control professional video matrix switchers via TCP/IP network connection. This allows remote switching of video routing configurations and management of switching presets during shows.

Category: Communication Device
Hardware Requirements: Network interface connected to matrix switcher
Software Requirements: None (protocol handled internally)
Compatibility: Barco Matrix Pro HD-SDI, BlackMagic VideoHub

Setup and Configuration

Network Configuration

Device Type: Select your matrix switcher model from the dropdown: - Barco Matrix Pro HD-SDI: Professional video matrix with HD-SDI inputs/outputs - BlackMagic VideoHub: BlackMagic’s video routing switcher series

IP Address: Enter the IP address of your matrix switcher. The device must be accessible on the same network as OnlyView.

Connection Process

  1. Ensure your matrix switcher is connected to the network and powered on
  2. Configure the switcher’s IP address according to your network setup
  3. In OnlyView, add the Matrix Switcher device and enter the correct IP address
  4. OnlyView will automatically connect and discover the switcher’s configuration (number of inputs/outputs, current routing, labels)

Actions

Available Actions

Take Preset: Recall a previously saved routing configuration. - Parameters: Preset name (selected from available presets) - Usage: Execute complex routing changes instantly during show operations

Timeline Integration

Matrix Switcher actions can be triggered from Command Cues on any timeline: 1. Add a Command Cue to a timeline layer
2. Set the cue’s device action to “Take Preset” 3. Select the desired preset from the dropdown list 4. The routing change will execute when the timeline playhead reaches the cue

User Interface

Device Widget

The Matrix Switcher device widget provides the following control and monitoring:

Status Indicators: - Connection Status: Visual indicator showing network connection to the matrix switcher - Device Name: Displays the connected switcher’s model name

Routing Grid: Interactive visual grid showing current signal routing: - Inputs: Listed vertically on the left side - Outputs: Listed horizontally across the top - Crosspoints: Click to change routing connections - Current Routes: Visual indicators showing active signal paths

Preset Management: - Preset Dropdown: Shows all available routing presets - New: Create a new preset based on current routing configuration - Save: Update the selected preset with current routing state - Take: Immediately execute the selected preset routing - Delete: Remove the selected preset from memory

Preset System

Creating Presets: 1. Configure desired routing using the grid interface or external switcher controls 2. Click “New” to create a new preset 3. Enter a descriptive name for the routing configuration 4. Click “Save” to store the preset

Managing Presets: - Edit Routing: Make routing changes via grid clicks or switcher front panel - Update Preset: Select existing preset and click “Save” to update with current routing - Recall Preset: Select preset from dropdown and click “Take” for instant switching

Label Management: - Input and output labels are automatically synchronized from the switcher - For compatible switchers, labels can be edited directly through OnlyView - Custom labels improve preset readability and operational efficiency

OSC

Overview

The OSC device enables OnlyView to send and receive OSC (Open Sound Control) messages over UDP networks. OSC is a network protocol for communication between computers, sound synthesizers, and other multimedia devices that is optimized for modern networking technology.

Category: Communication Device
Hardware Requirements: Network interface connected to OSC network
Software Requirements: None (protocol handled internally)
Compatibility: OSC 1.0 specification

Setup and Configuration

Network Configuration

Output Configuration: - Send to everybody (broadcast): Broadcasts OSC messages to all devices on the selected network interface - Broadcast Interface: Select the network interface to use for broadcast messages - Send to a specific IP: Sends OSC messages directly to a specified IP address - Receiver IP: Target IP address for unicast messages

Port Configuration: - Output Port: UDP port number for sending OSC messages (default: 7000) - Input Port: UDP port number for receiving OSC messages (default: 7001)

Built-in OSC Commands

OnlyView responds to several built-in OSC message formats: - /ov/quickkey/[id] 1: Execute a QuickKey by ID number - /ov/timeline/[id]/grandmaster [0-100]: Set timeline grandmaster level (0-100%)

Actions

Available Actions

Emit Message: Send a custom OSC message with specified path and value. - Parameters: OSC Path, Data Type (Integer/Float/String), Value - Usage: Send custom OSC messages to external applications or devices

Timeline Integration

OSC actions can be triggered from Command Cues on any timeline: 1. Add a Command Cue to a timeline layer 2. Set the cue’s device action to “Emit Message” 3. Configure the OSC path and value parameters 4. The OSC message will be sent when the timeline playhead reaches the cue

ActionGraph Nodes

OSC Input

Purpose: Receives OSC messages from the network and outputs the contained values. - Inputs: Device (OSC device selection) - Outputs: Value (Float or Vec3 depending on received message type) - Properties: - Device: Select the OSC device to monitor - OSC Path: The OSC address pattern to listen for (e.g., /osc/1/fader1)

This node listens for incoming OSC messages matching the specified path and forwards the received values to connected nodes. It only supports simple messages:

OSC Full Input

Purpose: Advanced OSC input node that dynamically creates outputs based on the received message structure. - Inputs: Device (OSC device selection) - Outputs: Dynamic outputs created based on received OSC message structure - Properties: - Device: Select the OSC device to monitor - OSC Path: The OSC address pattern to listen for

This node automatically adapts its output structure based on the complexity of incoming OSC messages, creating multiple outputs for multi-parameter messages. Click “Update outputs”; and on the next message, the node will have output slots that match the message’s parameters.

Note that the parameters of OSC messages are not names, so Onlyview can’t give meaningful names to these output slots. Instead, the slots are named according to the type of the parameter (“i” for an integer parameter, etc)

OSC Output

Purpose: Sends OSC messages to the network with various data types. - Inputs: Integer, Float, Vec3, Quaternion, Color, String - Outputs: None - Properties: - Device: Select the OSC device for sending - OSC Path: The destination OSC address (e.g., /mixer/channel/1/volume) - Send Event: Trigger to send the message

Connect data from other nodes to the input slots, configure the OSC path, and trigger the Send Event to transmit the message. You only need to connect one slot; if you connect more, several messages will be sent.

TUIO Output

Purpose: Specialized OSC output for TUIO (Tangible User Interface Objects) tracking data. - Inputs: Trackings (tracking data from tracking devices) - Outputs: None
- Properties: - Device: Select the OSC device for sending - TUIO Configuration: Settings for TUIO message format

This node converts tracking data from devices like OptiTrack or BlackTrax into standardized TUIO messages for multi-touch and tangible interface applications.

Overview

The PJLink device enables OnlyView to control professional video projectors that support the PJLink network protocol. This allows remote power management, shutter control, input selection, and status monitoring of projectors during shows.

Category: Projection Control Device
Hardware Requirements: Network interface connected to PJLink-compatible projector
Software Requirements: None (protocol handled internally)
Compatibility: PJLink Class 1 and Class 2 compatible projectors

Setup and Configuration

Network Configuration

Device Name: Enter a descriptive name for the projector (e.g., “Stage Left”, “Main Screen”).

IP Address: Enter the IP address of your PJLink-compatible projector. The projector must be accessible on the same network as OnlyView and have PJLink protocol enabled.

Connection Process

  1. Ensure your projector is connected to the network and powered on
  2. Enable PJLink protocol in the projector’s network settings
  3. Configure the projector’s IP address according to your network setup
  4. In OnlyView, add the PJLink device and enter the correct IP address and set a descriptive device name
  5. OnlyView will automatically connect and begin monitoring projector status
  6. In a UserScreen, go in edit mode, then drag&drop the device in the userscreen, relock. The device will show the monitoring status.

Actions

Available Actions

Power On: Turn on the projector (lamp ignition). - Parameters: None - Usage: Power up projectors before show start

Power Off: Turn off the projector (standby mode). - Parameters: None
- Usage: Safe shutdown of projectors after shows

Shutter Open: Open the projector’s shutter (enable video output). - Parameters: None - Usage: Allow video signal to be displayed

Shutter Close: Close the projector’s shutter (black video output). - Parameters: None - Usage: Temporarily blank video output while keeping projector running

Set Input: Change the projector’s active input source. - Parameters: Input type (RGB, Video, DVI, Storage, Network) and input number (1-9) - Usage: Switch between different signal sources connected to the projector

Timeline Integration

PJLink actions can be triggered from Command Cues on any timeline: 1. Add a Command Cue to a timeline layer 2. Set the cue’s device action to the desired PJLink command 3. Configure action parameters as needed (for input switching) 4. The projector command will execute when the timeline playhead reaches the cue

User Interface

Device Widget

The PJLink device widget provides comprehensive projector control and monitoring:

Status Indicators: - Connection Status: Visual indicator showing network connection to the projector - Device Name: Displays the projector’s configured name - Power Status: Visual indicator showing lamp on/off state - Shutter Status: Visual indicator showing shutter open/closed state

Control Buttons: - Power On: Immediately power on the projector - Power Off: Immediately power off the projector (standby mode) - Shutter Open: Open the projector shutter to display video - Shutter Close: Close the projector shutter to block video output

Lamp Information: - Lamp 1 Hours: Current operating hours for the primary lamp - Lamp 2 Hours: Current operating hours for the secondary lamp (if equipped)