Use these recovery steps when Virtual.ink is misbehaving but you do not want to jump straight to a full wipe.

## Targeted resets

Start with the narrowest reset that matches the problem:

| Section | Reset action | What it affects |
| --- | --- | --- |
| Dashboard | Reset dashboard | Dashboard tiles and UI preset layouts |
| Quick Nav | Reset Quick Nav | Quick Nav presets and shortcut-bar layout |
| Effects | Reset effects | Live effect parameters |
| Effects presets | Reset effects presets | Saved effect preset groups and cycling state |
| Live Setup | Reset live setup | Camera, live view, saving, replay, and related capture values |
| Virtual.ink | Reset Virtual.ink | Reapplies the current Virtual.ink factory defaults in one pass |

These resets are the safe first line of recovery. They are meant to restore behavior without deleting datasets or other local media.

## Destructive recovery actions

The lower danger-zone actions remove local data and should only be used intentionally.

| Action | What it deletes | What it keeps |
| --- | --- | --- |
| Reset all settings | Saved app, module, and UI settings files | Datasets, media files, and asset files |
| Full wipe | Local settings, datasets, generated assets, queue history, backup records, and share logs | External backup destinations |

After either destructive action, Virtual.ink reloads its current factory defaults.

## Send logs

The Send Logs panel prepares a diagnostic bundle for support. Use it right after reproducing the problem so the logs still contain the relevant state.

## Debug overlay

For live-session diagnostics, use the debug overlay from Live View instead of leaving the canvas. Press `D` to inspect frame rates, GPU status, device capability details, and other real-time information.

## Low frame rate on hybrid-GPU laptops

On laptops with both Intel integrated graphics and an NVIDIA GPU, the display is often wired through the Intel side by default. That can force an expensive cross-GPU copy path and drag the app down to very low frame rates.

The fix is to switch the laptop into discrete-GPU mode when the machine supports a MUX switch.

Common examples:

| Brand | App | Setting |
| --- | --- | --- |
| ASUS ROG / TUF | Armoury Crate | GPU Mode -> dGPU / Ultimate |
| MSI | MSI Center | GPU Switch -> Discrete GPU |
| Lenovo Legion | Lenovo Vantage | Hybrid Mode -> Off |
| Razer | Synapse | System -> GPU Mode -> Dedicated |
| HP Omen | Omen Gaming Hub | GPU Mode -> Discrete |

If the laptop has no MUX switch, run Virtual.ink on an external display connected directly to HDMI or DisplayPort, these outputs often route straight to the NVIDIA GPU.

## Second camera stuck at very low FPS

If the second feed runs around 4 to 5 fps instead of 25 fps, the capture device is usually a low-cost HDMI dongle based on the MacroSilicon MS2109 chip.

Two common fixes:

- Lower the second camera to 720p so the dongle can sustain the bandwidth.
- Replace the dongle with a quality capture card.

Virtual.ink resets and diagnostics

A factory reset returns the app to its shipped defaults. Choose the least destructive method that matches the problem. A reset can remove settings, datasets, generated assets, queue history, and other local files, so keep a backup before continuing.

These instructions apply to both **Virtual.ink** and **Xangle Camera Server**. Replace `<app>` below with `virtualink` or `cameraserver`.

## Method 1: Reset from the app

Use this method when the app launches and you can open **Troubleshooting** from the app menu.

1. Open **Troubleshooting**.
2. Choose **Reset all settings** to delete saved JSON settings in the active working folder while keeping datasets and assets.
3. Choose **Full wipe** only when you also want to remove the local datasets and asset files.
4. Confirm the action and restart the app if it does not reload automatically.

The reset restores the current shipped defaults. It does not delete files in an external backup destination. When the default working folder is active, the reset also removes its `locations.json`; when a custom working folder is active, the global `locations.json` remains in the default app root.

## Method 2: Create a new working folder

Use this method when you want a clean workspace but want to preserve the existing workspace for reference.

1. Open the app's working-folder or location settings.
2. Add or select a new folder as the active working folder.
3. Restart the app when prompted.

A new working folder is scaffolded with `config` and `datasets` subfolders. The app then reads settings from the new folder instead of the previous one. The old folder remains on disk, so it can be restored later by selecting it again.

Working-folder choices are recorded in the app's global locations file:

- Virtual.ink: `%USERPROFILE%\\xangle\\virtualink\\locations.json`
- Xangle Camera Server: `%USERPROFILE%\\xangle\\cameraserver\\locations.json`

The active folder can also be a custom path outside these default roots. The `locations.json` file stays in the default app root even when a custom working folder is active.

## Method 3: Rename the working folder in Windows Explorer

Use this method when the app does not launch or its settings UI is unavailable. Close the app completely first.

1. Close Virtual.ink or Xangle Camera Server.
2. Open the default app folder:
   - Virtual.ink: `%USERPROFILE%\\xangle\\virtualink`
   - Xangle Camera Server: `%USERPROFILE%\\xangle\\cameraserver`
3. Rename the folder to a backup name, such as `virtualink_backup` or `cameraserver_backup`.
4. Launch the app again.

The app creates a new default folder with a `config` directory and a `datasets` directory. Keep the renamed folder until you have confirmed that the app works and that you no longer need its settings or files.

If a custom working folder is active, use the path shown in the app's location settings instead of the default path. Renaming only the default root will not reset that custom folder.

## What is and is not reset

The working folder contains the active `config` and `datasets` data. Depending on the app and modules in use, it can also contain `assets`, `archives`, and `backup` directories.

- **Reset all settings** removes JSON settings files from the active working folder and preserves datasets and assets.
- **Full wipe** removes settings, datasets, and local asset contents.
- Renaming a working folder preserves everything in that backup folder until you delete it.
- `locations.json` is stored in the default app root and tracks known working folders and the active custom folder. If a custom working folder is active, reset its location list separately by removing the relevant entries from this file; if the default working folder is active, **Reset all settings** and **Full wipe** already remove the file.

Do not delete the default app folder while the app is running. If the app still does not start after a reset, keep the renamed backup and contact support with the application logs.


Factory reset

| 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 |
| --- | --- |
| Ctrl + , | Toggle dashboard layout editor. |
| Ctrl + L | Cycle dashboard display mode (normal / locked / minimal). |
| Escape | Close the dashboard layout editor. |

Dashboard & layout

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

- 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

- 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

| 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 |
| --- | --- |
| 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. |
| ↑ / ↓ | 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 |
| --- | --- |
| 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

- 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

- 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

- 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

- 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

- 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

- 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

- 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

- 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

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

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

## Saving videos

For short clips, ideally under 30 seconds, internal recording and instant replay work well, this is the common path for photobooths and short animations:

1. Open **Live**.
2. Press the record button, or the record hotkey (default "b"), to start recording.
3. Press it again to stop.
4. Set a predefined recording time from **Dashboard / Actions** if you'd rather not time it manually.

For longer recordings, such as live performances, saving externally is usually more efficient:

1. An external HDMI recorder, for example an [Atomos Ninja V](https://amzn.to/34trt4j).
2. A second computer with an additional HDMI-to-USB converter, recording through OBS or similar software (computer #1 running Virtual.ink -> HDMI to USB -> computer #2 running OBS).

## Saving individual frames

By default the last frame of a short clip becomes the thumbnail and an available image for sharing. Capture additional frames during a session with the snapshot hotkey (default Insert or Print Screen) or the Save button at the bottom of the live view.

- While recording, saved JPGs land in the same session folder as the current video.
- When not recording, a new folder is created each time you save a picture.


Resolution, duration & recording quality

Live effects are organized into tabs in the sidebar next to the live view. Every tab is tunable while the camera is running, no need to leave the live session, and the whole stack (minus Presets itself) can be saved and recalled from the **Presets** tab.

## Painting modes

Set in the **Motion** tab, separately for idle and while recording.

- **None**: 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, with adjustable trail length, decay speed, un-draw speed, and a trail shape (Even, Soft Tail, or Sharp Tail).

## Transform (symmetry)

Five symmetry modes, each with its own controls for folds, rotation, center point, spiral twist, hue-per-fold, radial zoom, auto-rotate, and wobble:

- **Mirror**, **Kaleidoscope**, **Pinwheel**, **Mandala**, and **Tiling** (grid of repeated tiles with adjustable columns/rows).

A stroke outline option switches strokes between neon-edge outlines and normal filled paint.

## Motion (whole-canvas animation)

Beyond the trail behavior above, the **Motion** tab can animate the whole canvas while painting: **Zoom** or **Gravity**, with a direction (up, down, left, right, or spiral) and adjustable length/speed. A separate **Wipe** sub-tab controls what happens when you trigger a reset: **Fade**, **Un-draw**, or **Rewind**, with duration and auto-pause options, plus an optional auto-wipe when a recording ends.

## Separation & Scene

**Separation** isolates the light painting from the rest of the scene, in **Light** mode (brightness-based, with light separation, softness, detail recovery, ambient preserve, and noise cleanup controls) or **Color** mode (keys a target hue with adjustable tolerance and minimum saturation).

Once Separation is active, Look, Transform, and Motion effects apply only to the isolated light, and the **Scene** tab unlocks separate effects for the background: dim, desaturate, blur, contrast, and tint (warm, cool, teal, rose, or green).

## Drift

Dissolve or distort the paint over time with a named drift effect: **Smoke**, **Wind**, **Ripple**, **Ember**, **Swirl**, **Bloom**, **Rise**, **Turbulence**, **Scatter (fly)**, **Drip**, or **Vortex**, each with its own parameters plus shared intensity, limit, ease curve, and fade-out controls. A painting mode must be selected in the Motion tab first.

## Look

Color and post-processing effects: hue shift, chromatic trails, edge glow, pixelate, warp, chromatic aberration, vignette, invert/negative, an "apply to lights only" toggle, accumulation blend mode, and a **Color Ramp** with about 30 built-in gradient presets (Fire, Ice, Synthwave, Neon, and similar).

## Shine

A source-based glow/star effect that detects bright points in the light and renders glints on top of them: effect type, threshold, minimum light size, max sources, radius, intensity, falloff, points, rotation/spin speed, color mode, blend mode, and optional trailing sparkle.

## Watermark

A branded overlay with adjustable opacity, scale, position, spacing, and blend mode, on eligible plans.

## Presets

Save the current combination of all the tabs above as a named preset, then recall it instantly during a live session. Presets can also auto-cycle sequentially or randomly instead of being triggered manually.

## Why trails sometimes have gaps

Light trails are captured through your camera's rolling shutter sensor, which scans a frame from top row to bottom row rather than exposing it all at once. Between frames there's a short blanking interval where the sensor resets and captures nothing. Any light movement that happens during that blanking interval is never recorded, no pixel in any frame catches that position.

The faster a light source moves, the further it travels during each blanking interval, so the gaps in the trail get wider. This is a physical limitation of the capture process, not a software issue. At 25 fps the blanking interval is only a few milliseconds per frame, but that's still enough to miss a segment of a fast-moving light.


Live effects and visual modes

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.

| Tier | Current web access |
| --- | --- |
| Starter | Web page unavailable |
| Basic | Available on this computer only |
| Pro / Pulse | Available on the local network |

## What it covers

Use Control Room when you want to adjust:

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

Current sections:

| Section | Purpose |
| --- | --- |
| Settings | FPS, resolution, and reset-all for console-managed values |
| Actions | Duration, countdown, cross-fade, reset-before, and paint-on-record |
| Transform | Symmetry, folds, tiling, and related geometry controls |
| Motion | Painting mode, decay timing, and canvas animation |
| Look | Hue shift, color ramp, pixelate, vignette, invert, and related post effects |
| Separation | Light separation, softness, detail recovery, ambient preserve, and cleanup |

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

Control Room

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

| # | 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.6 | My camera isn't on the [supported camera list](https://virtual.ink/supported-cameras/). Can it still work? | It needs to output clean HDMI (no overlays). Check your camera's manual, most cameras released after 2021 can do this. See the **Gear** category for the full hardware checklist. |
| 2.7 | How can I save my videos? | For short clips under 30 seconds, use the record hotkey ("b" by default) and instant replay, or set a predefined recording time from Dashboard / Actions. For longer recordings, save externally with an HDMI recorder like an Atomos Ninja V, or a second computer running OBS. See **Resolution, duration & recording quality** for the full walkthrough. |
| 2.8 | How can I save individual picture frames? | Use the snapshot hotkey (Insert or Print Screen by default) or the Save button at the bottom of the live view. Frames saved while recording land in the current session folder, otherwise a new folder is created each time. |
| 2.9 | Where can I find my saved images and videos? | From the dashboard, click the folder icon in Quickview (or ctrl-shift-e). From Live, click the folder icon on the replay video. On disk: `c:\users\%userprofile%\xangle\virtualink\datasets`. |
| 2.10 | What type of wireless remote control can I use? | A gamepad with a dedicated dongle plus a USB extension, or a Kokuyo Ela-fp1 finger trigger for hands-free use. See the **Gear** category for links. |
| 2.11 | Do I need internet to run Virtual.ink? | Only for three things: running on the Starter tier, validating your license at launch, and sharing videos from the sharing screen. The sharing station still works offline, reconnect later to clear the queue. |
| 2.12 | Why do my light painting trails sometimes have gaps? | Your camera's rolling shutter has a short blanking interval between frames where nothing is exposed. Light movement during that interval is never captured, faster movement means wider gaps. It's a sensor limitation, not a software bug. See **Live effects and visual modes** for details. |

2 — Capture & output

- 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

Virtual.ink isn't limited to this desktop app. It's also available on [Android](https://xangleapps.com), [iOS](https://xangleapps.com), and as a [plugin for Premiere and After Effects](https://xangleapps.com).

Did you know?

Virtual.ink runs from one live camera source. A second camera is optional, it feeds mashup renders (for example a behind-the-scenes shot next to the finished light-painting result on Basic and up), it does not combine with the main feed to build the live effect itself.

CPU, GPU, and storage needs scale mainly with your license tier's resolution ceiling: Starter (720p), Basic (1080p), Pro and Pulse (4K, plus ProRes recording).

**Windows**
- Windows 10 or 11, 64-bit
- Intel Core i5 or equivalent for 720p/1080p, Intel Core i7 or equivalent (or better) for 4K and ProRes recording
- Any modern integrated GPU (Intel Iris or newer) for standard use, a dedicated NVIDIA GPU is recommended at 4K and also enables hardware-accelerated recording (NVENC) for lower CPU load

**Mac**
- Apple Silicon (M-series) only, the current build does not run on Intel Macs
- A base M-series chip is enough for 1080p and most effects, a Pro/Max/Ultra chip helps for 4K and ProRes recording
- Recording uses Apple's built-in hardware encoder automatically, no dedicated GPU needed

**All configurations**
- 8 GB RAM minimum, 16 GB recommended for 4K or ProRes recording
- 700 MB available storage for the app itself, recording storage scales with resolution, quality preset, and duration, 4K ProRes files are especially large
- Internet connection for license login
- One dedicated USB 3 port per capture device (one for the main camera, a second only if you add the optional mashup source)

Computer requirements

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.

Not sure if your camera qualifies? Check the [supported camera list](https://virtual.ink/supported-cameras/) first. If it's not listed, check your camera's manual for a clean HDMI output option (no overlays, no on-screen display). Most cameras released after 2021 can output clean HDMI.

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

Camera and capture options

There are two practical ways to connect a camera to Virtual.ink. Both make the camera appear as a video input that the app can use in Live.

### Option 1: HDMI capture card

Connect the camera's HDMI output to a USB capture card, then connect the capture card to the computer.

This is the most reliable path for production use. It supports the widest range of cameras, resolutions, and frame rates, and it avoids most of the limits that come with vendor webcam utilities.

- Best fit for events, photobooths, and any setup that needs to stay stable for long sessions.
- Prefer USB 3 capture devices that expose stable 1080p25 modes.
- Use clean HDMI output with no focus boxes, menus, or camera overlays.
- For dual-camera setups, prefer one dedicated USB path per capture device.

Recommended capture cards:

| Device | Best for | Notes |
| --- | --- | --- |
| Inogeni 4K2USB3 | Preferred choice for Virtual.ink | Very stable, strong mode support, good fit for fixed 25 fps workflows |
| Magewell USB Capture HDMI | Best alternative | Reliable professional capture with low latency |
| Elgato HD60 X | Good fallback | Consumer device, still solid when passthrough also matters |
| Elgato Cam Link 4K | Single-camera fallback | Compact and common, less ideal for dual fixed-25-fps rigs |

Avoid generic HDMI-to-USB dongles sold under labels such as USB Video or HDMI Capture. They often expose unstable modes, ignore MJPG requests, or fall back to bandwidth-heavy formats that can collapse to very low frame rates.

### Option 2: Manufacturer webcam software over USB

Camera makers also offer webcam utilities that expose the camera directly over USB. This is simpler to wire, but it usually comes with lower resolution ceilings, fewer controls, and more compatibility risk.

- Canon, Sony, Nikon, GoPro, Fujifilm, Panasonic, and others all have some form of webcam workflow.
- In practice these utilities are best for lighter setups, teaching, or temporary rigs.
- HDMI capture is still the better default for event production.

Typical limitations:

- Resolution and frame rate are often capped below what the same camera can output over HDMI.
- Support varies by exact model, firmware, operating system, and utility version.
- Multi-camera support is often limited or locked behind a paid tier.

### Why 25 fps is usually the safer target

Virtual.ink does not benefit much from a capture path pushing far more frames than the app actually needs. In most real setups, a stable 25 fps feed is better than an unstable 50 or 60 fps feed.

- Lower bandwidth on USB and the host chipset.
- Fewer dropped or duplicated frames when running two cameras, recording, and preview together.
- Easier to keep both cameras on a predictable fixed-rate path.

If your device only exposes 1080p60 it can still work, but it is usually not the ideal match for a two-camera Virtual.ink rig.

Camera connection

**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. Two options that hold up well: a [gamepad with a dedicated dongle](https://amzn.to/2NzlFQs) with a [USB extension](https://amzn.to/2x5okYK), or a [Kokuyo Ela-fp1 finger trigger](https://amzn.to/2DhSgq6), which keeps both hands free.

**Internet connection**
An internet connection is only needed for three things: running on the Starter tier, validating your license each time the app launches (any tier), and sharing videos from the sharing screen. If you go offline mid-event, the sharing station keeps working, reconnect afterward to clear the send queue.

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

Recommended accessories

- 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

Live View is the main operator canvas in Virtual.ink. It is where you frame the camera feed, paint live, start capture, preview recent output, and open the right-side tools without leaving the canvas.

This is a native desktop surface, not a standalone browser page.

## What you see

The main surface shows the live camera feed with the light-painting render composited on top.

When no camera is selected, Live View shows a no-signal state. If you change the camera, codec, frame rate, or resolution, the feed can briefly drop into a transition state while the source reloads.

## Bottom dock

The floating dock gives quick access to the main live actions:

| Button | Action |
| --- | --- |
| Record / Stop | Start or stop the current capture |
| Paint on / off | Enable or disable light accumulation |
| Reset | Clear the current paint buffer |
| Snapshot | Save a still frame |
| Hide UI / Show UI | Collapse or restore on-screen controls |
| Fullscreen / Exit | Toggle fullscreen |

The dock also shows the current resolution and target versus live frame rate. During recording, a timer appears above it.

## Right-side rail

The rail on the right opens the desktop-only side panels:

- **Live Setup** for camera input, capture behavior, replay sizing, thumbnails, and file options.
- **Effects** for live image processing.
- **Debug** for diagnostics.
- The home badge returns to the dashboard.

Only one right-side panel stays open at a time.

## Inline replay

After capture finishes, Live View can keep the most recent saved result visible in the corner.

- `None` disables replay.
- `Small`, `Medium`, and `Large` keep the latest replay visible in the corner stack.

When replay is active, the latest playable dataset opens automatically, loops muted, and can be dismissed or expanded.

## Fullscreen replay overlay

Opening the replay expands it above the live canvas.

The overlay can show:

- the replayed media
- sharing actions such as email or QR
- media actions such as rating, delete, or archive
- basic dataset details such as resolution and timestamp

Useful keyboard behavior:

- `Escape` closes fullscreen replay.
- `Left Arrow` and `Right Arrow` move to the previous or next playable dataset.
- `Delete` archives the current replayed dataset and advances.

## Camera 2 picture-in-picture

When Camera 2 is enabled and set to **BTS**, Live View shows the second feed in the same corner area used by inline replay.

- The picture-in-picture size follows the same replay size setting.
- Camera 2 can be flipped together with Camera 1 or configured independently.
- This is useful for a behind-the-scenes or ambient angle while the main camera stays focused on the light painting.

## Countdown and debug overlays

Timed actions can show a large countdown before capture begins. During capture, the live timer switches into recording mode and shows the remaining time when the action is timed.

Press `D` to toggle the debug overlay. Use it when you need requested versus actual resolution, input and render frame rates, device capability details, GPU mode, or Camera 2 diagnostics.

## Display fit

Two fit modes are available from Live Setup:

| Mode | Behavior |
| --- | --- |
| Fill | Fills the window and may crop the edges |
| Fit | Preserves aspect ratio and can add letterboxing |

Live View

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

## Finding saved files on disk

- From the dashboard: click the folder icon in **Quickview**, or use the shortcut ctrl-shift-e.
- From **Live**: click the folder icon on the replay video.
- Directly on disk: `c:\users\%userprofile%\xangle\virtualink\datasets`


Media library

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

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

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:

| Button | Action |
| --- | --- |
| Record / Stop | Start or stop recording |
| Paint / Paint Off | Toggle light painting on or off |
| Reset | Clear the light-painting canvas |
| Snapshot | Capture a still frame |
| Hide UI / Show UI | Hide or show controls on the main screen |
| Fullscreen | Toggle fullscreen on the main screen |

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.

Remote Control

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

If a light-painting result shows a small gap or dark stripe where the trail briefly disappears, that is not a Virtual.ink bug. It is a normal limitation of video capture.

## Why photos behave differently

A long-exposure photo keeps the sensor collecting light continuously for the whole exposure. A moving light source can draw one uninterrupted trail.

Video does not work that way. At 25 fps the camera records 25 separate frames per second. Between frames the sensor has to reset before it can expose the next frame. During that reset window the light source can keep moving, but nothing is being recorded.

Virtual.ink can only stack the frames the camera actually sends. The positions that were never captured during those reset moments do not exist in the input, so the final trail can show a gap.

## This is a sensor limitation, not a software fix

This behavior comes from the camera capture process itself. A capture card does not cause it, and Virtual.ink cannot reconstruct light positions that never reached any frame.

Video light-painting is a trade-off: you gain live feedback and instant playback, but you accept that a faint gap can still exist between captured frames.

## How to make the gap smaller

The most effective control is shutter speed.

- At 25 fps, a shutter speed around **1/25 s** keeps the sensor open for most of each frame period, so the gap becomes as small as the camera allows.
- At **1/50 s**, the gap is larger.
- Faster shutter speeds make the gap more obvious.

If your camera and capture path support **50 or 60 fps**, those higher frame rates can also help because each frame period is shorter.

## Why some gaps look much worse

When the shutter speed is too fast, for example **1/100 s** or **1/200 s**, the sensor stays closed for most of each frame period. The light can travel a long distance before the next exposure starts, so the missing segment looks much wider.

If the gap looks extreme, check shutter speed before assuming there is a wiring or software issue.

## If the gap is still visible

Even with the slowest usable shutter speed, a small reset interval still exists. The gap may remain faintly visible depending on the movement, the background, and how much the light source blooms into the surrounding pixels.

What helps:

- Move more slowly so the light covers less distance during the reset interval.
- Use **1/25 s** at **25 fps** as the default starting point.
- If needed, retouch the gap afterward in a photo editor.

Why light trails can have gaps

- 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 | None, 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. |
| Transform (Symmetry) | A visual layout mode (Mirror, Kaleidoscope, Pinwheel, Mandala, or Tiling) applied to the live light painting. |
| Separation | Isolates the light painting from the rest of the scene (by brightness or by color), so other effects can target the light only. |
| Scene | Effects (dim, desaturate, blur, tint) applied only to the background once Separation is active. |
| Drift | A family of dissolve/distortion effects (Smoke, Wind, Ripple, and others) applied to the painted trail over time. |
| 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. |


Section	Reset action	What it affects
Dashboard	Reset dashboard	Dashboard tiles and UI preset layouts
Quick Nav	Reset Quick Nav	Quick Nav presets and shortcut-bar layout
Effects	Reset effects	Live effect parameters
Effects presets	Reset effects presets	Saved effect preset groups and cycling state
Live Setup	Reset live setup	Camera, live view, saving, replay, and related capture values
Virtual.ink	Reset Virtual.ink	Reapplies the current Virtual.ink factory defaults in one pass

Action	What it deletes	What it keeps
Reset all settings	Saved app, module, and UI settings files	Datasets, media files, and asset files
Full wipe	Local settings, datasets, generated assets, queue history, backup records, and share logs	External backup destinations

Brand	App	Setting
ASUS ROG / TUF	Armoury Crate	GPU Mode -> dGPU / Ultimate
MSI	MSI Center	GPU Switch -> Discrete GPU
Lenovo Legion	Lenovo Vantage	Hybrid Mode -> Off
Razer	Synapse	System -> GPU Mode -> Dedicated
HP Omen	Omen Gaming Hub	GPU Mode -> Discrete