## Naming

Structured naming rules keep datasets and exports readable at scale, so files stay searchable and don't need manual cleanup after a busy event. Available on Pro and Pulse.

## Backup

Backup writes secondary copies automatically, so an important capture isn't lost to a single point of failure (a full disk, a dropped drive, a corrupted file). Available on Pro and Pulse.


Naming & backup

- 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.


Choose station roles

- 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.


Keep stations on task

- 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.


Pre-event checklist

- 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.


Register and identify screens

| Shortcut | Action |
| --- | --- |
| Ctrl + , | Toggle dashboard layout editor. |
| Ctrl + L | Cycle dashboard display mode (normal / locked / minimal). |
| Escape | Close the dashboard layout editor. |


Dashboard & layout

| Shortcut | Action |
| --- | --- |
| Ctrl + Shift + mouse wheel | Zoom into the area under the cursor. |
| Ctrl + Shift + 0 | Reset magnification to 1x. |
| Escape | Reset magnification to 1x. |


Screen magnifier

| Shortcut | Action |
| --- | --- |
| Ctrl + Shift + H | Go to the dashboard. |
| Ctrl + 1 … 9 | Jump to Quick Nav slot 1–9 (configurable in Quick Nav settings). |
| Ctrl + Shift + O | Open the current page in an external browser. |

Quick Nav presets are configured in Settings > Quick Nav. Each preset can hold up to 9 pages mapped to Ctrl+1 through Ctrl+9.


Navigation

| Shortcut | Action |
| --- | --- |
| F11 or Alt+Enter | Toggle window fullscreen (or browser fullscreen in a web session). |
| Ctrl + Shift + F9 | Cycle demo window size presets (16:9 / 9:16 / 1:1). |
| PageUp | Toggle black screen overlay (for long-exposure photography). |
| Escape or click | Dismiss the black screen overlay. |


Window & display

| Shortcut | Action |
| --- | --- |
| ← / → | Previous / next dataset. |
| ↑ / ↓ | Previous / next frame. |
| PgUp / PgDn | Previous / next iteration. |
| G | Go to frame number. |
| Scroll wheel | Zoom in / out (at cursor). |
| Click + drag | Pan (when zoomed). |
| Double-click | Toggle fit ↔ 100%. |
| + / − | Step zoom in / out. |
| 0 | Fit to screen. |
| 1 | 100% zoom (1:1). |
| F | Cycle fit mode (fit / width / height). |
| B | Cycle background (black / white / checker). |
| C | Cycle guide overlay (off / crosshair / 3×3 / 4×4). |
| ? | Show / hide shortcuts. |
| Escape | Close inspector. |

These shortcuts are active when the Frames inspector is open.


Frames inspector

| Shortcut | Action |
| --- | --- |
| 0 … 5 | On the dataset detail page, clear or set the saved star rating. |
| Escape | Cancel pending transfer, dismiss bulk-action bar, or exit selection mode. |
| Ctrl + , | Open Library settings. |


Library

| Shortcut | Action |
| --- | --- |
| ← / → | Previous / next dataset. |
| 0 … 5 | Clear or set star rating on the current dataset (0 = clear, 1 = one star, 5 = five stars). |
| Escape | Close settings panel, or go back. |
| Ctrl + , | Open Quickview settings. |

Rating shortcuts work on the Quickview page and on the Quickview dashboard tile.


Quickview

| Shortcut | Action |
| --- | --- |
| F10 | Capture a JPG screenshot of the app window immediately. |
| Ctrl + F10 | Capture a JPG screenshot of the app window after a 2-second delay. |
| F7 | Start recording the app window. While recording: pause or resume. |
| F8 | Stop recording and save the clip. |

Recordings are saved in the active working folder under sessions/, each in its own folder named after its final MP4. Screenshots are saved separately under screenshots/.

Demo camera overlay shortcuts work after the overlay is configured. Camera 1, Camera 2, and Both view cycling becomes available once Camera 2 is running.

> Note: the demo-camera-overlay shortcut table from the original in-app help (camera bubble position/resize/zoom keys) is app-shell specific and was intentionally left out of this first migration pass; it can be added as its own page once its module ownership is confirmed.


Screeva

## What this export contains

- Export from Share Settings Logs to download a CSV of email queue recipients.
- Each row includes recipient email, dataset folder, status, sent date, plus configured custom fields.
- The export reflects queue history and filters, so apply your date and state filters before exporting.

## Why teams use it

- Post-event handoff to marketing or CRM systems.
- Delivery auditing for sent versus failed batches.
- Field-level analysis when custom form data is captured during sharing.

## Good practice

- Export at least once during rehearsal to validate field mapping.
- Keep a final export snapshot at event close for reporting and recovery workflows.

Download email list

## Core email flow

- Use email sharing when guests should receive a delivery link after operator confirmation.
- Keep templates, subject line, and reply-to aligned with the event brand before the first capture.
- Use required terms and custom fields only where compliance or follow-up needs justify the extra steps.

## Controls that affect delivery quality

- Enable multiple recipients only when operators are expected to send one capture to several contacts.
- Keep direct download available when email inbox access may be delayed on site.
- Verify SMTP sender configuration and test against real inbox providers before launch.

## Queue operations

- Monitor queue state for sent, pending, uploading, and failed jobs.
- Use queue details to inspect dataset path, attached files, subject preview, and rendered email body.
- Retry failed items from queue actions after fixing config or connectivity issues.


Email sharing

## What offline QR mode changes

- Offline QR mode bypasses cloud relay delivery and serves files from the local machine.
- The share modal shows two QR codes: one for joining Wi-Fi and one for opening the local download page.
- This mode is intended for venues with unstable internet or fully offline operations.

## Setup requirements

- Configure a dedicated sharing hotspot and set the expected Wi-Fi SSID in Share Settings.
- Keep the sharing station and guest phones on that same local network segment.
- Test with real phones before doors open. Do not rely on desktop browser simulation for this mode.

## Operational cautions

- If guests cannot join Wi-Fi, the download QR will still fail even if the code scans correctly.
- If the station sleeps, reboots, or changes network, retest both QR codes immediately.
- Use portal delivery instead when links must remain reachable after the local station is gone.


Offline QR sharing

## Define the output set before opening Share

- Decide which outputs are actually needed at handoff: image, video, combined media, thumbnail, and any print-specific version.
- Keep output naming clear so operators can quickly identify what is guest-facing versus archival.
- Use Process recipes to lock branding, overlays, framing, and ratio choices before the first live capture.
- Keep the output list lean. Too many variants slow down review and increase wrong-action clicks at the station.

## Match outputs to the delivery path

- QR and direct download should point to files that are light enough for phone delivery on event Wi-Fi.
- Email delivery should use the same branded files guests expect from QR, unless you intentionally send a different variant.
- Printing should have its own prepared source strategy (input, processed, both, or auto) so print quality is predictable.
- Portal delivery is best when links must stay valid after the booth machine powers down.

## Operator checklist before doors open

- Confirm one complete flow for each promised action: QR, email, print, and portal link when enabled.
- Confirm filenames and sorting make sense when multiple outputs are attached to the same capture.
- Confirm terms and custom fields only collect what the event actually needs.


Plan deliverables

## When portal delivery is the right choice

- Use portal delivery when links must remain active after the local sharing station is offline.
- Use it for events where guests often open media later, not only on-site.

## Dependencies to verify

- Confirm internet reachability and relay connection from Share Status.
- Confirm the app has a valid login session. Invalid or expired sessions can block relay startup.
- Keep offline QR mode disabled when you need cloud relay behavior, because offline mode bypasses relay delivery.

## Operational notes

- Run a full phone test from scan to final open link before guests arrive.
- Keep one operator check focused on relay and portal status after any network change.


Portal delivery

## Enable printing in the right places

- Turn on printing in Share Settings, then enable the print action in the Share preset used at the station.
- Refresh the printer list and choose a preferred printer before the event starts.
- Set paper size and copy limits so operators cannot accidentally overload a printer line.

## Choose print source strategy

- Input: fastest path from original files.
- Processed: uses branded outputs from recipes.
- Both or auto: useful when some captures have processed files and others do not.
- Enable fallback to input when processed files might not be ready in time.

## Live print workflow checks

- Test single and bulk print flows from the actual Share station.
- Verify quantity prompts only if your team needs per-job copy overrides.
- Watch print job status (queued, printing, completed, failed) during early event traffic.

Printing

## When to use QR sharing

- Use QR sharing when guests scan from the station and complete delivery on their own phone.
- Use it for single captures or multi-select batches from the Share screen.

## Configuration points that matter

- Choose QR placement for operator clarity: overlay on media preview or hidden from inline cards.
- Tune QR size and overlay position so the code stays readable on your actual sharing display.
- Keep direct download enabled when guests should save files immediately after opening the share page.
- Enable "require email before QR" only when your event needs contact collection before phone handoff.

## Live-operation checks

- Confirm Share is enabled and relay status is connected when using cloud QR mode.
- Scan from at least one Android and one iPhone device on the event network.
- Confirm both single-item and bulk QR flows if operators will share multiple captures together.


QR sharing

## QR and offline QR failures

- Confirm Share is enabled, then confirm whether the station is in cloud relay mode or offline QR mode.
- For cloud mode: verify internet and relay connected status before blaming QR generation.
- For offline mode: verify hotspot availability, SSID accuracy, and that guest phones join the same local network.
- Test QR from real phones, not only desktop previews.

## Email delivery failures

- Check queue state first: pending, uploading, failed, or sent.
- Open the failed queue item and inspect error message, recipients, and attached files.
- Recheck SMTP sender settings, required fields, and template placeholders after any config change.

## Print failures

- Confirm printing is enabled in both Share Settings and the active Share preset.
- Confirm the selected printer is online and paper settings match the expected format.
- If processed-source printing fails, test with input or fallback mode to isolate recipe/output timing issues.

## Portal and link persistence failures

- Confirm relay service is running and authenticated.
- If session is invalid, sign in again and rerun a full end-to-end share.
- If offline QR mode is enabled, remember that portal relay delivery is bypassed.

## Missing recipient export

- Export email CSV from Share Settings Logs after applying the intended filters.
- If export is unexpectedly empty, confirm there are queue records in the selected state/date scope.


Sharing or delivery issues

## Full pre-event test sequence

- Capture one real sample and verify all expected outputs exist.
- Run one QR share from the station screen and open it on a real phone.
- Run one email share and confirm inbox delivery, template rendering, and link behavior.
- Run one print job if printing is enabled, including copy-count behavior when quantity prompts are enabled.
- Run one portal delivery validation when cloud relay mode is expected.

## Validate details, not only success

- Confirm filenames and output variants are understandable to operators.
- Confirm terms, custom fields, and required email gates match the event policy.
- Confirm timing is acceptable under normal venue network conditions.

## Record and fix before go-live

- Log every mismatch (wrong branding, missing output, failed queue item, broken QR, print error).
- Fix settings first, then rerun the same test path until results are stable.


Run a test share

## Resolution and duration

| License | Max resolution | Max recording duration |
| --- | --- | --- |
| Starter | 720p | 8 seconds |
| Basic | 1080p | 30 seconds |
| Pro | 4K | Host system limit |
| Pulse | 4K | Host system limit |

## Recording quality presets

- Four presets are available on every license: **Efficient**, **Standard**, **High**, **Maximum**.
- Efficient uses a higher CRF for smaller files, Maximum uses a near-lossless CRF suited for archival.
- Pro and Pulse can also record in **Apple ProRes 422 HQ (.mov)** for post-production in Premiere or DaVinci Resolve. ProRes files are significantly larger than H.264.
- A capture card that delivers uncompressed or low-compression input gives the best source quality regardless of the output format you choose.


Resolution, duration & recording quality

## Painting modes

- **Off**: no trail, the frame just shows the live camera feed.
- **Continuous**: paint accumulates and stays on screen until you reset.
- **Decay**: paint accumulates but trails fade out over time instead of staying on screen.

## Mirror and layout modes

- 2x and 4x mirror
- Twisted butterfly
- 3x horizontal

## Reset and playback behavior

- **Crossfade**: adjustable 0 to 5 seconds, fades to black on reset instead of cutting instantly.
- **Slow down / speed up**: sliders that change trail accumulation speed live.
- **Rewind and boomerang**: alternate playback effects for the recorded result.

## Effects stack

The full live effects stack is organized into families you can combine: **Presets** (reusable looks), **Motion** (trail lifetime, whole-canvas animation), **Transform** (symmetry, tiling), **Drift** (paint aging/deformation), **Look** (color and post effects), **Shine** (source-based star/glow), **Separation & Scene** (foreground vs. background), and **Watermark** (branded overlay, on eligible plans). All of this is tunable while the camera is running, no need to leave the live session.


Live effects and visual modes

## 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.


Second display & browser device access

| # | Question | Answer |
| --- | --- | --- |
| 2.1 | What's the difference between the recording quality presets? | Efficient, Standard, High, and Maximum trade file size for quality, Efficient uses a higher CRF for smaller files, Maximum is near-lossless. |
| 2.2 | Why would I use ProRes instead of H.264? | ProRes 422 HQ (Pro/Pulse only) is better suited for professional post-production editing in Premiere or DaVinci Resolve. Files are significantly larger. |
| 2.3 | What's the difference between continuous and decay painting modes? | Continuous keeps the trail on screen until reset. Decay lets the trail fade out over time on its own. |
| 2.4 | Can I brand my output automatically? | Yes, from Basic and up. Save a watermark, intro/outro, and soundtrack as a render recipe and reuse it on every capture. |
| 2.5 | Where do backups get written? | Configure a backup destination from the Backup settings (Pro/Pulse). Captures are copied there automatically. |


2 — Capture & output

| # | Question | Answer |
| --- | --- | --- |
| 1.1 | What's the difference between the license tiers? | Mainly resolution (720p/1080p/4K), recording duration, and access to render/branding, naming, backup, and network-wide device access. See the License types category for the full breakdown. |
| 1.2 | Where do I check which license I'm running? | Open Settings, your current license tier is shown there. |
| 1.3 | Does Starter expire? | Starter is a free one-year entry tier. |
| 1.4 | Can I use a second display or another browser station on Basic? | Second-display monitor mode is available on Basic, but browser access to Virtual.ink from another device on the network requires Pro or Pulse. |


1 — License

- Open **Live** for the full-screen light-painting view. This is where you'll spend most of a session.
- Set **resolution** and **recording duration** before your first real capture. Starter is capped at 720p / 8 seconds, Basic at 1080p / 30 seconds, Pro and Pulse follow the host system's practical limits.
- Pick a **painting mode**: off, continuous trail, or decay (trails fade out over time instead of staying on screen).
- Adjust **crossfade** if you want the screen to fade to black between resets instead of cutting instantly.
- Trigger a capture from the keyboard, a Bluetooth presenter, or a gamepad, see the **Controls & mapping** category to set that up first.
- After a capture finishes, it lands in **Library** for review, and can be replayed instantly from **Player**.
- When you're happy with a result, send it to a guest from **Share** (QR or email) or hand it off from **Quickview**.

Once the basic flow feels comfortable, check the **Live capture** category for the full effects stack (mirror modes, shine, look, watermark) and **Render & branding** for branded exports.


Your first light-painting session

Use this as a hardware checklist before you install or run Virtual.ink: what's required, and what we recommend once you're past the minimum.

## Computer requirements

**Single camera**
- Intel Core i5 or equivalent for 720p
- Intel Core i7 or equivalent for 1080p
- Intel Iris or any modern integrated GPU

**Dual camera**
- Intel Core i7 or equivalent
- Intel Iris or modern integrated GPU for standard use, dedicated GPU (NVIDIA or AMD) recommended for heavy effects

**All configurations**
- 8 GB RAM
- 700 MB available storage
- Windows 10 or 11 (64-bit)
- Internet connection for license login
- One dedicated USB 3 port per capture device

## Camera and capture options

Virtual.ink works with any camera that outputs a clean HDMI signal and any standard HDMI capture card. HDMI capture generally gives the most flexibility and the best image quality. If you already have a camera and capture card, there's a good chance they'll work, request a free trial before purchasing to confirm compatibility with your specific hardware.

**Option 1: HDMI capture**
- Single camera: any camera with clean HDMI output, plus a compatible HDMI capture card.
- Dual camera: two cameras with clean HDMI output, plus two compatible HDMI capture cards.

**Option 2: Camera through USB**
- Simpler setup, with more limited image quality and control than HDMI.
- Canon: Windows only, up to 1024 px wide over USB. The simplest setup path. Compatible models include most Canon DSLRs, some newer mirrorless models (M50, R, RP, M6ii), and some PowerShot models (G7xiii, G5xii).
- Sony: works with cameras that include a built-in webcam mode, usually up to 1280 px wide.
- GoPro: direct USB can reach 1920x1080 on models such as the GoPro 10, 11, 12, and 13.
- Only one camera can run over direct USB, but it can be combined with a second camera connected through HDMI capture.

**Option 3: Webcam**
- Logitech Brio, or any webcam that lets you control settings manually.

## Recommended accessories

**Remote control**
The included remote works for testing and short-distance use, roughly within 2 meters of the computer. For performances, outdoor setups, or photobooths, a dedicated presenter or controller holds up better at distance.

**Cables, tripods, and brackets**
A camera bracket makes two-camera setups easier to align and keep steady. An L-shaped or angled HDMI cable saves space and lets you mount two cameras closer together, match the angle to your camera body's port orientation. A lightweight tripod keeps the rig portable for event work.

**External recorder**
For recordings longer than about a minute, keep the main computer focused on the light-painting process and record externally, either with a second computer and capture card, or a dedicated external recorder.

**Light-painting tools**
Light-painting tubes, kits, liteblades, squares, and whips: https://lightpainting.store


Gear

- Open **Button Mapping** to see and change what each key, presenter button, or gamepad input does.
- Map the core actions you'll use most during a session: trigger capture, reset, pause/resume, and playback.
- A Bluetooth presenter (the kind used for slideshow remotes) works well for a solo operator who needs to trigger a capture from a distance.
- A gamepad is a good fit when several actions (trigger, reset, effect switching) need to be reachable without looking down at a keyboard.
- Test the full mapping once before an event starts, not mid-session when a guest is waiting.


Keyboard, presenter & gamepad mapping

| License | Resolution | Duration | Recording format | Render/branding | Naming & backup | Device network access |
| --- | --- | --- | --- | --- | --- | --- |
| Starter | 720p | 8 seconds | H.264 (Standard) | No | No | No |
| Basic | 1080p | 30 seconds | H.264 (Standard) | Yes | No | Local machine only |
| Pro | 4K | Host system limit | H.264 + ProRes 422 HQ | Yes | Yes | Local network |
| Pulse | 4K | Host system limit | H.264 + ProRes 422 HQ | Yes | Yes | Local network |

Pulse includes the same production toolset as Pro, plus direct access to the Xangle team for support and roadmap feedback.

Check your current license from **Settings**.


License types

- Mashups combine two sources into one render, for example the behind-the-scenes camera on one side and the finished Virtual.ink result on the other.
- Use a **9:16 vertical** layout for Stories, Reels, Shorts, and other social-first formats.
- Use a **16:9 horizontal** layout for venue monitors, recap screens, and standard playback displays.
- Choose top-and-bottom or side-by-side depending on which source should feel dominant in the frame.
- Like other render output, mashups are recipe-based, so you can queue a vertical social cut, a horizontal venue version, and a clean archive export from the same capture.

Available from Basic and up.


Mashup layouts

- **Library** is where captured sessions land for review, rating, and reuse.
- Grid columns are adjustable, a wall of thumbnails for fast event review, or a narrower grid for slower client-facing selection.
- Sort order can be newest-first or oldest-first.
- Star ratings let you filter down to favourites instead of scanning every dataset.
- These layout choices live in UI presets, so a preset link can reopen the library in a known configuration on another screen (a review station, for example).


Media library

- **Player** replays a finished result for guests or clients right after capture, without leaving the app or hunting for a file.
- Mute on playback when the player drives a silent reveal screen or venue monitor.
- Slideshow behavior can be: off, all captures, the last 5, the last 10, or random.
- Star-based filters restrict the player to rated favourites.
- Contain mode preserves the full frame, cover mode fills the screen, pick based on the display you're driving.
- Like the library, playback settings live in UI presets, one preset can behave like a looping guest reveal, another like a curated client-review player.


Playback player

## Watermarks and branded frames

- A small PNG watermark works as a classic logo bug, placed lower-left, lower-center, or lower-right.
- A full-frame branded overlay PNG (same aspect ratio as the output) covers a full sponsor frame or decorative border instead of a simple logo.
- Watermark scale, opacity, and blend mode are all adjustable, so branding can stay subtle or bold.

## Intros, outros, soundtrack, overlays

- An MP4 or MOV **intro** clip plays before the capture, useful for sponsor/event branding.
- An **outro** clip plays after, useful for a logo or call-to-action.
- An MP3, WAV, or AAC **soundtrack** turns the output into a more complete social/presentation asset.
- A **video overlay** layers animated graphics on top of the result when a static watermark isn't enough.

## Recipes

These controls live in the render pipeline. Once a branded finish is set up, save it as a recipe and reuse it on future captures instead of rebuilding it by hand. One raw session can feed several recipes at once (clean version, branded social cut, venue-ready playback version).

Available from Basic and up.


Watermarks, overlays, intros & outros

- Countdown, capture, and completion sounds give guests a clear sense of pacing without constant operator coaching.
- Use them to reduce how much verbal guidance an operator needs to give during a busy session.
- Configure which cues play and when from **Sound**.


Countdown & effect sounds

| Term | Meaning |
| --- | --- |
| Live | The full-screen light-painting view where a session actually happens. |
| Painting mode | Off, continuous, or decay, controls whether and how the light trail stays on screen. |
| Decay | A painting mode where trails accumulate then fade out over time instead of staying on screen. |
| Crossfade | The fade-to-black transition between one reset and the next, adjustable 0 to 5 seconds. |
| Mirror mode | A visual layout (2x, 4x, twisted butterfly, 3x horizontal) that duplicates and reflects the live frame. |
| Recipe | A saved render configuration (branding, format, layout) that can be reused across captures instead of rebuilt by hand. |
| Preset | A saved UI configuration (for example, Library grid columns and sort order, or Player slideshow mode) that can be reopened from a link. |
| Watermark | A logo or branded overlay applied to the output. |
| Mashup | A render layout that combines two sources (for example, behind-the-scenes camera and finished result) into one output. |
| ProRes 422 HQ | An Apple video codec available as a recording/output option on Pro and Pulse, suited for professional post-production editing. |
| Library | The page for browsing, rating, and managing saved captures. |
| Quickview | Fast single-image review of the latest capture or a chosen dataset. |
| Player | The replay screen used to show a finished result to a guest or client. |
| Frames | The grid inspector for reviewing individual frames within a dataset. |
