Dynamic Assets

A dynamic asset is a named container that holds versioned content. Use it to swap media — language tracks, updated sponsor logos, seasonal variations — without editing timelines. Timeline cues reference the dynamic asset, not a specific file. The active version determines which media plays.

When you add a version, cues referencing the dynamic asset pick up the change. The Director coordinates the change across all Runners without a running Producer.

How It Works

A dynamic asset appears in the Assets window as a folder marked with a recycle icon. The folder holds its version assets.

A dynamic asset keeps at most two versions: the active version (the most recently added) and the previous version. When you add a new asset, it becomes the active version. The former active version becomes the previous version. The former previous version is removed automatically.

The active version is always the one used by cues that reference the dynamic asset.

What Happens During a Version Swap

When a new version is added, a coordinated update flows through the system.

The Director reads asset versions and broadcasts upgrades over its Runner connection.

Asset Substitution During Downloads

The version swap happens without a visible interruption during playback. Asset Transfer describes how the Runner downloads and substitutes the new version.

Categories

When creating a dynamic asset, choose a category. The category restricts which file types the dynamic asset accepts.

• Visual — image, video, and SVG content.
• Audible — audio and video content.
• Display Data — projection mapping data such as MPCDI.

The category sets a hidden folder-name suffix (_dyn_visual, _dyn_audible, or _dyn_display). It is fixed when the dynamic asset is created.

Creating a Dynamic Asset

There are two ways to create a dynamic asset.

From scratch:

1. Right-click in the Assets window.
2. Choose New, then Create Dynamic Asset.
3. Enter a name and select a category (Visual, Audible, or Display Data).
4. Click Save.

An empty dynamic asset folder is created. Add versions to it.

From an existing asset:

1. Select an existing asset (not a folder) in the Assets window.
2. Right-click and choose New, then Create Dynamic Asset.
3. The existing asset becomes the first version. The asset's type sets the category.

Adding Versions

To add a version to an existing dynamic asset:

• Drag and drop — drag a file onto the dynamic asset folder.
• Create Version — select the dynamic asset or a version, right-click, and choose New, then Create Version. The dialog sets the version name, frame rate (for video), and color space. Create Version can also re-encode the version to a different codec. See Asset Properties.
• Move into folder — drag an existing asset into the folder. WATCHOUT clones the asset, because versions cannot be moved into a dynamic asset.

Versions sort by creation time, newest first. The newest version is the active version.

Version Structure

A dynamic asset keeps the active version and the previous version (see How It Works).

Automated workflows that update a dynamic asset repeatedly — such as the Asset Watcher or the Web User Interface — always keep exactly two versions.

Automatic File-Based Updates

Enable Automatically Update Assets in the show settings to let the Producer track the source files of imported assets. When a source file changes, the Producer creates a new version and starts the upgrade pipeline described above. The two-version rule still applies.

This works together with the Asset Watcher. The watcher detects new files in watched folders. Automatic update detects changes to existing source files.

Managing Versions

• Delete a version — select the version inside the folder and delete it. If the dynamic asset is used on the timeline, at least one version must remain.
• Revert — the active version is always the newest by creation time. Remove newer versions to fall back to an older one.

Use Cases

Best Practices

• Use the Latest Asset Version setting for cues that should auto-update. Use Fixed for cues that must never change, such as safety instructions or calibration patterns.
• Match resolution and duration between versions to avoid unexpected cropping or timing mismatches.
• Test version swaps during rehearsal. Confirm that all Runners receive and switch to the new version.
• Keep source files accessible when using Automatically Update Assets. The Producer reads the original file path to detect changes.
• Check Asset Transfer status after a swap. Confirm all Runners downloaded the new content before showtime.
• Use the same codec and color space across versions to avoid re-optimization delays.

Limitations

• A version asset cannot be placed on the timeline directly. Use the parent dynamic asset. The Producer blocks adding a managed version to the timeline by itself.
• The category is fixed at creation. A visual dynamic asset cannot become audible later.
• Folders and compositions cannot be converted to dynamic assets.
• A dynamic asset keeps only two versions (see How It Works).
• Automatic update needs the Producer. Version distribution works without it, but detecting source-file changes needs the Producer running.

Related

• Asset Manager — asset pipeline overview and optimization stages.
• Asset Properties — create a version with a different output codec.
• Asset Transfer — how versions are distributed to Runners and how substitution works.
• Asset Watcher — automated file detection that triggers dynamic asset updates.
• Web User Interface — browser-based upload for adding versions remotely.
• Asset Manager Issues — troubleshooting optimization, transfer, and asset problems.