Register and identify screens

• Open the station page on each tablet, TV, kiosk, or operator browser, then confirm it appears online in Devices.
• Give each station a practical name based on its physical location, such as Share counter, Replay TV, or Staff tablet.
• Keep the Devices page open during setup so you can see which screens are connected before guests arrive.

Choose station roles

• Use a sharing station at the guest handoff point so staff can confirm a result, show the QR code, or send the email.
• Use a replay station on a larger screen when guests or staff should browse finished sessions.
• Use kiosk or guided mode for public-facing screens that should stay on a narrow, event-specific flow.

Keep stations on task

• From Devices, send a station to the correct event page instead of walking to the screen and typing a URL by hand.
• For public screens, keep the station pinned to its event role so guests cannot wander into operator-only parts of the app.
• If a screen shows the wrong page during the event, correct it from Devices and confirm the physical display updates.

Pre-event checklist

• Test every station on the real event network before doors open, especially tablets, TVs, and older browsers.
• Confirm power, screen sleep settings, fullscreen mode, Wi-Fi or Ethernet stability, and the station name shown in Devices.
• Walk the real guest flow once: capture, review, share, scan QR, open the link, and replay the result on the intended screen.

Second display & browser device access

Second-display monitor mode

Send eligible dashboard tiles to a connected HDMI monitor from the dashboard's monitor icon. Available from Basic and up.

Browser-based device pages

• Basic keeps browser access to Virtual.ink on the licensed computer only.
• Pro and Pulse extend that access to other devices on the same local network, useful for a remote trigger, a separate operator station, or a guest-facing control screen.

Full screen & hide controls

Full-screen mode and hidden controls remove operator interface chrome from the display guests actually see, keeping public-facing screens clean. Available from Basic and up.

Control Room

Control Room is the browser-friendly live settings page exposed at /console when webpage access is allowed on the current license. The same surface still exists inside the desktop app, so web access rules do not remove it from the operator workstation.

Changes load from the Virtual.ink server and save back automatically, so Control Room behaves like a live editor rather than a submit form.

Access policy

This policy applies to the web page, not the desktop page inside Virtual.ink.

What it covers

Use Control Room when you want to adjust:

• capture format
• action timing
• symmetry and motion
• look and separation settings

Current sections:

What it is not

Control Room is not a full clone of the desktop operator UI.

It does not handle camera device selection, MJPG toggles, the native live canvas, the desktop debug overlay, or every desktop-only effect surface.

Use Live Setup for input-device configuration and capture layout. Use the desktop Effects sidebar for the full effects stack.

Save and reset behavior

Changes save automatically after a short debounce. If a save fails, the page reloads the current server state so it does not drift away from the main app.

The Settings section includes a reset-all action for console-managed values. Each effect section also exposes its own reset action so one area can be cleared without affecting everything else.

These resets affect live values only. They do not reset Quick Nav, dashboard presets, or global app defaults.

Remote Control

Remote Control lets an operator trigger core Virtual.ink actions from the same desktop app, a dashboard tile, or an eligible browser session on the same computer or local network.

This is useful when the main machine is across the room, mounted in a rig, or when more than one person needs to trigger recording during a session.

Access policy

• Inside the desktop app, Remote Control can appear as its own page or as a dashboard tile.
• Starter does not expose a standalone web page.
• Basic keeps the web page available on this computer only.
• Pro and Pulse can expose the web page on the local network.

How to connect

1. Confirm that the current tier allows webpage access.
2. Open a web browser on the target device.
3. Go to the app address shown in the header.
4. Open the Remote Control page.
5. Log in with the same credentials as the main machine if prompted.

Actions from the remote device are reflected on the main screen immediately.

Available controls

The remote page shows large touch-friendly buttons:

Record and Snapshot are disabled when saving is disabled on the current license. Hide UI can also be disabled by entitlement.

Standalone vs embedded

• Standalone layout: full-screen browser page on a phone or tablet with large touch targets.
• Embedded layout: desktop page or dashboard tile inside Virtual.ink.

Both layouts expose the same core actions. UI presets can still load different control layouts for different tiles or shared links.

Practical notes

• Any modern browser is enough, no app install is required.
• Multiple devices can connect at the same time.
• If the connection drops, the page should reconnect automatically when the network returns.