Virtual.ink documentation

Delivery is the post-capture output and distribution module.

Use it when the work is no longer about capturing media, but about preparing, organizing, and delivering the result to guests, clients, staff, or downstream production workflows.

What Delivery Handles

Delivery brings together five practical jobs:

• sharing outputs by QR code, email, download, or print
• configuring the share form and delivery behavior
• processing datasets into branded or formatted outputs
• organizing work by event
• managing reusable production assets used by recipes

Main Pages

Page	Best for	Main actions
Share	operator or guest delivery workflows	QR sharing, email delivery, download, print, multi-select sharing
Share Settings	configuring how delivery works	media selection, terms, custom form fields, email template, queue review, printing
Process	automated output preparation	create recipes, auto-run renders, monitor queue, manage render steps
Events	activation or session organization	create events, rename, hide, set current event
Assets	reusable production files	upload, preview, organize, and delete overlays, intros, LUTs, and similar files

Typical Workflow

1. Select or create the current event.
2. Configure process recipes and upload reusable assets.
3. Let new datasets arrive from capture or import.
4. Process those datasets automatically or manually into the required output formats.
5. Deliver the result by QR code, email, direct download, or print.
6. Check queue state, logs, and connectivity if delivery fails.

Share

Share is the delivery page most operators feel first.

It presents recent datasets in a configurable grid and can expose actions such as:

• QR sharing
• email sharing
• direct download
• printing
• multi-dataset selection when the preset allows it

Depending on the preset, QR codes can appear as overlays or sidecars, and card taps can trigger the primary sharing action directly.

Share Settings

Share Settings controls the rules behind the Share page.

This includes:

• whether video, snapshots, and thumbnails are shared
• whether multiple email recipients are allowed
• custom fields shown in the email form
• terms and conditions shown in the form
• editable email templates and subjects
• email queue visibility and retry handling
• offline QR behavior and related connectivity settings
• printing behavior, copy limits, and preferred printer selection

Process

Process is the recipe-driven rendering page.

Recipes can auto-run when a recording finishes and can define:

• output format, resolution, framing, fps, and quality
• watermark and overlay steps
• LUTs
• intro and outro clips
• soundtrack attachment

The page also shows render jobs and shared assets used by those recipes.

Events

Events lets operators group work by activation, client, session, or production block.

Operators can create events, rename them, hide older ones, and mark one as the current event used by the active workflow.

Assets

Assets is the reusable file library for Delivery recipes.

Typical asset categories include:

• overlays
• video overlays
• intros
• outros
• LUTs
• soundtracks

These files are shared across recipes, and deleting an asset can affect existing recipe presets.

Operational Notes

• Share and related delivery services can start in the background automatically.
• Process progress is broadcast live so queue views can update without a manual refresh.
• Asset changes can also refresh live when files are uploaded or deleted.
• Some deployments use offline QR download flows.
• Some delivery capabilities can be limited by the active license tier or entitlements.

Used By

• Virtual.ink
• Sharing Server