Is the encoded media already acceptable?
Use this workflow when video and audio quality are already right and the task is packaging, track layout, metadata, or container compatibility rather than a full transcode.
Elysia Tools
Navigation
Workflow Playbook
Inspect streams, remux containers, trim by timestamp, mux tracks, softmux subtitles, embed cover art, and batch rewrap media while preserving source quality.
New to this workflow? Follow the steps in order, starting with the first tool below. Already know what you need? Jump straight to the matching step — every tool in this workflow is listed in the comparison table.
First tool: Stream Probe Report
Hubs
| Tool | What it does | Category |
|---|---|---|
| Stream Probe Report | Readable stream and codec report for media files. | Media |
| Media Metadata to JSON | Extract audio/video metadata as JSON with ffprobe. | Media |
| Stream Smart Remux | Rewrap media containers with stream copy. | Media |
| Stream Passthrough Trimmer | Stream-copy trimming. | Media |
| Video Smart Mux | Combine video with external audio using copy mode. | Media |
Hubs
| Batch Rewrap |
| Batch remux media files with stream copy. |
| Media |
| Video Dual Audio Merger | Mux two audio tracks into one video in copy mode. | Media |
| Video SRT Softmux | Add selectable SRT subtitles without burning them in. | Media |
| Cover Art Embed | Embed cover artwork without re-encoding media. | Media |
This workflow is for media files that are already encoded well enough to keep. The goal is to inspect what is inside the container, decide whether stream copy is safe, and then package deliverables without spending time or quality on a full transcode. stream-probe-report gives a human-readable overview, while media-metadata-to-json preserves the same evidence in a structured form that can be compared or attached to a delivery note.
Once the streams are understood, pick the smallest operation that solves the delivery problem. stream-smart-remux is the right first stop when the file only needs a new wrapper such as MP4, MKV, MOV, or WebM. stream-passthrough-trimmer is useful when a keyframe-aligned time cut is acceptable. For repeated packaging, batch-rewrap applies the same copy-based container change across many files, while video-smart-mux adds one external audio stream to a single video without touching the original picture.
Delivery often depends on track presentation as much as codec choice. video-dual-audio-merger builds alternate-language or commentary packages, video-srt-softmux adds selectable captions, and cover-art-embed attaches artwork for music, podcast, or MP4 presentation. A finished package should be re-opened in the target player or ingest system to confirm track order, language labels, subtitle visibility, cover art, duration, and compatibility.
Workflow playbook
Create a readable stream report and export ffprobe metadata as JSON so container, codec, bitrate, duration, chapter, language, subtitle, and attachment details are known before any packaging operation.
Remux into a compatible container or trim a timestamp range with passthrough copy when keyframe alignment is acceptable, avoiding a CPU-heavy transcode when the encoded streams can be preserved.
Use smart muxing when one video needs an external audio track, and batch rewrap when multiple finished files need the same stream-copy container change and ZIP delivery.
Create dual-audio packages, softmux selectable SRT subtitles, and embed cover art into compatible audio or video containers while keeping the main media streams intact.
Use this workflow when video and audio quality are already right and the task is packaging, track layout, metadata, or container compatibility rather than a full transcode.
Choose MP4 or MOV only when codecs and subtitles are compatible. Prefer MKV when unusual audio, subtitle, attachment, or multi-track layouts need fewer container restrictions.