Skip to main content

Assets

Assets are the individual media or data-backed items that SVRunner can schedule for playback on screens.

When To Use Assets​

Use an asset when you need to add a single piece of content to the system.

Common examples:

  • a single video clip
  • a still image
  • a media item that will be reused across multiple events

If you need a reusable ordered group of assets, use an Asset Block instead.

Supported Workflow​

The normal asset workflow is:

  1. Create the asset from the assets list.
  2. Upload a file or provide the source information required by the selected asset type.
  3. Review the detected media information.
  4. Set the playback and organizational fields.
  5. Save the asset.
  6. Add the asset to an event sequence when it is ready to schedule.

Creating An Asset​

Open the Assets page and use the Create Asset action.

After the asset is created, it appears in the assets list and can be edited in the sidebar or detail view.

Assets List Stub screenshot: assets list in grid or list view with a few representative assets and visible filters. Save final image at packages/docs/screenshots/app-assets-list.png.

Recommended source formats from the previous operator documentation:

Video FilesImage Files
HEVC (H.265), H.264 MP4JPEG, PNG

Other formats may work depending on the deployment, but these are the formats that should be preferred for predictable playback.

Important Asset Fields​

Name​

The Name is a human-readable label for operators.

  • changing the name does not rename the original uploaded file
  • use names that are easy to identify later in searches and event editing

Duration​

The Duration controls how long the asset is played.

  • by default, the asset uses the detected duration of the uploaded file
  • if the configured duration is shorter than the source file, playback stops early
  • if the configured duration is longer than the source file, the asset loops until the configured duration is reached

Tags​

Use Tags to organize the asset library.

  • tags make it easier to locate assets later
  • use a consistent tagging scheme across operators

Info​

The Info section typically reflects source file characteristics such as:

  • filename
  • resolution
  • duration
  • media type
  • size

Operators should review this information after upload to make sure the correct file was selected.

Asset Sidebar Stub screenshot: asset sidebar or detail panel showing name, duration, tags, and media info after an upload. Save final image at packages/docs/screenshots/app-asset-sidebar.png.

Operational Notes​

Upload Delay​

Large files may take time to upload and process.

note

Depending on file size and network conditions, the preview for a new asset may not appear immediately.

Reuse​

Assets are intended to be reused.

  • avoid uploading duplicates when an existing asset can be scheduled again
  • prefer tags and naming discipline over creating near-identical copies for convenience

Metadata Discipline​

Good metadata reduces scheduling mistakes.

  • make names specific
  • apply tags consistently
  • verify duration before using an asset in time-sensitive schedules

Extensions​

Some deployments use Extensions to add custom fields or validation to assets.

  • extension-defined fields may be required before an asset can be considered complete
  • these fields are deployment-specific and should be documented by administrators

See Extensions.

Common Mistakes​

  • uploading the wrong file and not checking the detected metadata
  • setting an incorrect duration for a time-sensitive asset
  • failing to save after editing
  • using inconsistent tags across operators
  • creating duplicate assets instead of reusing existing ones