Virtual.ink documentation

Process is the recipe-driven rendering page. It lets operators define output presets that automatically transform captured datasets into delivery-ready formats with branding, overlays, soundtracks, and color grading.

Who Uses This

• Photobooth operators who need every capture processed into a branded video with an intro, overlay, and soundtrack
• Photographers who want automatic format conversion and framing for client delivery
• Studio operators running batch rendering with specific quality and resolution targets

How Recipes Work

A recipe is a saved preset that describes exactly how a dataset should be processed. Each recipe defines:

Source and Output

Setting	Options	What it controls
Source	Video / Thumbnail / Media	Which input from the dataset to process
Format	MP4 / GIF / PNG / JPG	Output file format
Resolution	Native / 3:2 / 16:9 / 5:4 / 1:1 / 4:5 / 9:16	Output aspect ratio
Framing	Crop / Contain	How the source fits a non-native ratio (crop trims edges, contain adds bars)
FPS	Native / 12 / 24 / 25 / 30 / 50 / 60	Output frame rate (video formats only)
Quality	Low / Medium / High / Lossless	Compression level
Mute Video	On / Off	Strips audio from the output

Pipeline Steps

Each recipe can include a chain of compositing and post-processing steps applied in order:

Step type	What it does	Accepted file types
Watermark	Composites an overlay image on each frame	PNG
Video Overlay	Composites a video layer on top of the output	MP4, MOV, WebM
LUT	Applies a color look-up table for grading	CUBE
Intro	Prepends a clip before the main content	MP4, MOV
Outro	Appends a clip after the main content	MP4, MOV
Soundtrack	Replaces or mixes audio with a music track	MP3, WAV, AAC

Each step references a file from the Assets library. Steps can be individually enabled or disabled without removing them from the pipeline.

Watermark steps also support centered or bottom-edge placement, scale, opacity, and blend mode settings.

Auto-Run

Each recipe has an active/inactive toggle:

• Active: The recipe runs automatically whenever a new recording finishes. This is the default mode for event workflows where every capture must be processed immediately.
• Inactive: The recipe is saved but only runs when triggered manually.

Multiple recipes can be active at the same time, producing several output variants from a single capture.

Render Jobs

The Process page shows active and completed render jobs:

• Queued jobs waiting to be processed
• Jobs currently rendering (with progress)
• Completed jobs (success or error)

Render progress updates live without needing to refresh the page.

Shared Assets

A collapsible section at the bottom of the Process page shows the assets available to pipeline steps, organized by category. This provides a quick reference without switching to the Assets page.

Used By

• Virtual.ink
• Sharing Server