DeviceJockey Guide

Scenes

Scenes organize complete, independent configurations for different workflows and environments.

Complete configurations

Switch your whole setup at once.

Different tasks may require different interfaces, panels, items, and connection settings. A scene keeps everything required for one workflow together. You can prepare separate scenes for OBS Studio, Logic Pro, camera control, mixing, lighting, or any other environment you operate.

Scenes are independent from one another. Only one scene is active at a time. Its interfaces are the ones currently available, and its panel items access only those interfaces.

Separate workflowsKeep unrelated controls and connections in independent configurations.
Change environmentsStore different addresses, ports, and other connection settings for each location.
Switch quicklyActivate the complete setup you need without rebuilding panels or interfaces.

What belongs to a scene

All parts of a workflow stay together.

Interfaces

Connections and settings for the devices and applications used in this scene.

About interfaces →

Panels and items

The control surfaces and controls prepared for this workflow.

About panels →

Macros

Sequences of actions that belong to the scene and its connected environment.

About macros →

Swaps

Named runtime values and their organizing SwapTables for this scene.

About Swaps →

Examples

When separate scenes are useful.

Different applications

Use one scene for OBS Studio and another for Logic Pro or a Grass Valley camera system.

Different locations

Keep separate interface settings when the same equipment uses different networks or addresses.

Different tasks

Separate operation, setup, monitoring, and troubleshooting into focused configurations.

Import and export

Reuse and share complete scenes.

Scenes can be exported and imported. This lets you back up a configuration, move it to another device, share it with other users, or use an existing scene as the starting point for a new workflow.

Create one clear purpose per scene.

A focused scene is easier to understand, maintain, and operate than a configuration that tries to cover unrelated workflows.

Getting started

Build a scene for one workflow.

1

Define the purpose

Choose the workflow or environment this scene should support.

2

Add interfaces

Configure the required devices, applications, and connection settings.

3

Create panels

Add the control surfaces and items needed for the workflow.

4

Test the scene

Activate it and verify its connections, commands, events, and controls.