Smart Transcode | PV4 Help Centre

The Smart Transcode feature within CONTENT ensures your media assets are optimized for management, delivery, and playback across any system or device. It converts files into the required formats and resolutions, maintaining quality while reducing manual workload and complexity.

Key functions

Automated Transcoding
Convert media into optimized formats for any target system or device, without manual intervention.
Preset Profiles
Use predefined settings for common output requirements to save time and ensure consistency.
Custom Profiles
Create tailored profiles for unique venue specifications or specialized workflows.
Batch Processing
Transcode multiple files simultaneously to streamline large-scale content preparation.

Supported variables

Video Parameters	Codec Bitrate Resolution Frame Rate Aspect Ratio Pixel Format
Audio Parameters	Codec Selection Bitrate Sample Rate Channels
Container Formats	Select from supported container formats for compatibility.
Advanced Options	Keyframe Interval Color Space Conversion Compression Level

Monitoring and status

Real-Time Progress
Track transcoding progress and estimated completion times.
Error Handling
Receive alerts for failed transcodes and retry options.
Performance Metrics
View resource usage to optimize processing speed.

Transcode configuration

Jobs

Jobs represent individual transcoding tasks triggered either manually or automatically. Each job logs its status, progress, and origin (including whether it was initiated by an automatic rule). Jobs can include video, audio, and normalization steps combined into a single workflow. Automatic jobs appear in the job log with indicators showing they were rule-based.

The Jobs tab of the Smart Transcode window displays all active jobs and their current status while in progress. Once successfully completed, a job remains visible for two hours. Failed jobs remain visible for one week.

Presets

Presets are the building blocks of Jobs — each one is an FFmpeg operation (or combination of operations), written as a JSONata expression, that defines the output format and processing parameters. For manually initiated Jobs, users are prompted to select which preset to use. For automated Jobs, presets are selected when building rules.

Presets can be enabled or disabled globally and are tagged for applicable asset types (video, graphics, etc.). Advanced presets can include padding or scaling logic for non-standard screen sizes.

Preset settings
Name	Purpose: The full descriptive name of the preset. Example: `HAP Alpha Video Preset`
Short Name	Purpose: A concise identifier for quick reference in lists or UI elements. Example: `HAP-A`
Description	Purpose: Explains the preset's function and intended use case. Example: "Converts video to HAP Alpha format for transparency support, maintaining original resolution."
File Type	Purpose: Specifies the asset type the preset applies to (e.g., Video, Audio, Graphics). Options: `Audio` `Font` `Graphic` `Video`
Requisite Type	Purpose: Indicates the type of output file generated. Options: `Derivative` `Hi Res Preview` `Thumbnail` `Web Preview`
Preset Type	Purpose: Categorizes the preset as Audio, Video, or Normalization. Options: `Audio Preset` `Video Preset` `Normalization Preset`
Expression	Purpose: The underlying configuration or script block of JSONata that defines the preset's behavior. Example: `(\n $outputPath := " " & jobFolderPath & "/" & $join([file.id, transcodeJob.id, 'mov'], '.');\n\n {\n "inputPath": ("-i " & signedUrl & " "),\n "audioFilter": "-an",\n "outputPath": $outputPath\n }\n)` Content note: the live Create/Edit Preset panel currently labels this field Transcode instead of Expression.

Automatic Conditions

Automatic Conditions are checks run against a file at upload time, to determine if an Automatic Rule should apply to it. Common checks include matching a codec, comparing resolution (height, width, or both against a threshold), and checking for an alpha channel.

Automatic condition settings
Name	Purpose: A clear, descriptive title for the condition. Example: `Resolution Greater Than`
Description	Purpose: Explains what the condition checks and when it should be used. Example: "Checks if the asset's resolution exceeds a specified width or height threshold."
Expression	Purpose: The specific check being performed — e.g., does the codec match, does the resolution meet a threshold, does the file have an alpha channel.
Inputs	Purpose: The value(s) being checked against — e.g., a codec name, or a height/width threshold. Each input has its own Label, Variable Name, and Description.
Result	Purpose: Whether the file meets the condition (yes/no), which determines whether the attached Automatic Rule proceeds.

Automatic Rules

Automatic Rules combine Presets and Automatic Conditions into reusable logic applied at a Content Folder level. Key points:

Rules can be applied globally or at folder level, with inheritance and overrides.
Multiple rules can coexist; each rule creates one derivative.
If multiple rules succeed, multiple transcodes occur.
Preset priority within a rule is top-down; the first matching preset wins for each type (video/audio/normalization).
A rule can have multiple criteria blocks. Each criteria is its own named group pairing specific Presets with specific Automatic Conditions — all of that criteria's conditions must pass (AND logic) for its paired preset(s) to fire.
A rule can be set to automatically select its newly transcoded file as the asset's selected file once the transcode job completes.

Rules can be toggled for auto-selection or manual review.

Automatic rule settings
Name	Purpose: A clear, descriptive title for the rule. Example: `High-Resolution HAP Q Conversion`
Description	Purpose: Explains the rule's purpose and when it should be used. Example: "Automatically converts video assets to HAP Q format if resolution exceeds HD and normalizes audio when present."
Criteria	Purpose: One or more named criteria blocks attached to the rule. Each criteria has its own Name and Description, plus its own Presets (which preset(s) to apply) and Conditions (which Automatic Conditions must pass for those presets to fire).
Automatically select transcoded file	Purpose: When enabled, the file produced by this rule's transcode job becomes the asset's selected file as soon as the job completes.