Learn how to process media using RMS Console. The Transforms and Jobs will help you convert your uploaded assets into ready-to-use media files.
In this article:
Before you begin
Media processing allows you to prepare your content for different delivery scenarios. With RMS Console, you can submit tasks like transcoding videos to different formats, extracting thumbnails, adding closed captions, and more. Decide what result you want to achieve, and the following steps will help you get there:
1. Upload a media file to the asset
2. Select or create a Transform - a template that defines how media will be processed
3. Create a Job for uploaded media using your selected Transform
4. Monitor your Job's progress
5. Use a processed output for publishing
Transforms
A Transform includes one or more presets that define the specific processing tasks for your media. Think of a Transform as a recipe for how your media will be prepared for playback, storage, or distribution.
Transform creation in the RMS Console currently supports creating only one output per transform. As a workaround, submit a subsequent job for the output asset to achieve the desired result (e. g. apply an AudioAnalyzer preset to the processed media).
You can select from your existing Transforms or create new Transforms when you need specialized processing options:
Select a Transform
1. Navigate to the Transforms list to view all available transforms.
2. Filter by name to find transforms. Search requires exact matching text.
3. Select a Transform to view its associated Jobs.
Click View outputs to see the transform's preset and JSON:
A detailed JSON is visible for custom presets. For the Standard built-in presets, only the template name will be displayed:
Create a new Transform
If you need a different Transform from those available, create a new one with the following steps:
1. Navigate to the Transforms list and Click + Create Transform.
2. Pick a Standard built-in preset or a Custom JSON preset tab.
- To add a Built-in preset, select the option in the dropdown list.
- To add a Custom JSON preset, paste your JSON preset. Use Insert sample to populate an editable JSON preset sample or Format JSON to auto-edit your code.
RMS supports many transform configurations, but some custom presets may need adjustments. If a preset does not work as expected, request help from Ravnur support.
3. A Transform name will be generated (named as CustomPreset_{timestamp}). Optionally, change the name of your transform and add a transform description.
4. Click Create transform.
The ability to delete transforms from the Console will be available soon.
Jobs
Jobs are used to process media files. A job applies specific transformations to your input files to produce the desired output. These transformations can include format conversion, metadata extraction, thumbnail creation, and more.
Create a job
1. Submit a Job in one of the following ways:
- Open the Transforms tab and click plus sign + Create job.
- Open the Assets > Asset details page and click plus sign + Create job.
2. Select your input asset using one of these methods:
- Click Select an existing asset to choose from previously uploaded assets.
- Click Upload an asset to upload a new media file directly.
If you created a job from the Asset details page, the input asset is already selected.
3. Select a Transform from the dropdown list.
4. Configure output and job settings:
- Output asset name: Use the auto-generated name (InputAssetName_Output_{timestamp}) or enter a custom name for the automatically created output asset. You can also select your existing asset instead.
- Job name: Use the auto-generated name (InputAssetName_Job_{timestamp}) or enter a custom name.
Asset storage account is autoselected based on the Primary storage account set. If you need the output saved explicitly into a different storage account, change it via the dropdown menu. Note that you need to add a storage account to the RMS Console first.
5. Click Create job.
You can also start a Job using an External URL instead of the asset. The base URI should be a valid HTTPS URL that links directly to the media file (not a webpage containing the media).
Jobs Lifecycle
When you submit a job, it appears immediately in the Jobs tab, where you can monitor its progress. Select a Transform to view its associated Jobs.
The system processes your media through several stages. To check a job's current status, click on Refresh to see the latest updates - status does not update automatically. Filter jobs by job name (requires exact matching text) or by job status.
Understanding Job Status
- Queued: Job is waiting to be processed.
- Scheduled: Job has been scheduled for processing.
- Processing: Job is actively being processed.
- Finished: Job has completed successfully.
- Error: Job encountered an issue during processing. Try troubleshooting it.
- Canceling: If you (or another user) manually canceled the job, it transitions to this status before automatically updating to Cancelled.
- Canceled: The job has been canceled and processing has stopped.
After processing, the output asset content can be published, downloaded, or used for additional transformations. You can access it quickly by clicking View outputs on the corresponding job.
Troubleshooting
If a job shows an Error status, click the View Error button to see the complete error stack.
This will open a detailed error popup showing the specific error message:
Address the error-specific issues. If the error persists or isn't clear enough:
- Make sure the file isn't corrupt and the format is supported.
- Try resubmitting the job.
If your job remains in Queued status longer than usual:
- Resource availability: If all concurrent job workers are busy processing other jobs, new jobs will remain in the queued state until resources become available. There's nothing to do but wait.
- Scaling: If jobs remain in the scheduled state for extended periods, consider increasing the vCPU quota to allow more scaling and speed up job initiation.
- Azure downtime: If there are issues with Azure infrastructure, jobs may remain queued. You can monitor Azure Status and Service Health. Once Azure resolves the issue, the job will automatically resume.
If problems persist after troubleshooting, please contact Ravnur.