media trained

which pipeline owns which deliverable, and how to verify media instead of trusting a successful exit code.

mental model

Route by output: imagegen for Codex-created bitmaps, ai-multimodal for analysis or audio/video generation, html-video for HTML templates, Remotion for React compositions, and media processing for existing assets. When more than one guide applies, run the container task first.

examples

Two command probes that check the toolchain itself:

ffmpeg -hide_banner -loglevel error -f lavfi -i testsrc2=size=64x64:rate=1 -frames:v 1 -f null -
magick -size 2x2 xc:red -format '%m %wx%h\n' info:

They exercise encoding and image creation without writing an artifact. They are not proof of a project video or generated image.

best practices

Inspect a source asset and the rendered output. Verify codecs, dimensions, duration, audio, and representative frames. For generated bitmaps use Codex alone and complete the global PNG -> WebP -> gallery -> open workflow. FFmpeg manual, ImageMagick CLI.

strengths

FFmpeg handles stream and codec work; ImageMagick handles deterministic still-image transforms. HTML-video has a working Hyperframes adapter for HTML templates; Remotion handles React compositions and frame timing. html-video upstream, Remotion docs.

weaknesses / pain points

A container muxer or successful command exit does not prove playback. Generation tools may create convincing but wrong text or composition; inspect each deliverable. Upstream html-video currently documents other engines as roadmap, so check list-engines before planning around them. html-video upstream.

gotchas

ffmpeg -c copy output.mp4 can preserve an incompatible source codec. Choose stream copy only after ffprobe confirms the input streams. FFmpeg stream copy.

known bugs

No version-specific defect is known. Provider model access, pricing, and media limits must be checked at use time; dated bundled reference values are not current guarantees.

troubleshooting

Missing MP4 metadata or blank frames mean the input or template is wrong: inspect the source streams, the render log, and actual frames, then rerender. A generated project bitmap that lives only in scratch is not delivered: convert it to WebP, place it at the consumer, update the gallery, and open the gallery.

practiced cases

FFmpeg 9.0 encodes a 64x64 synthetic frame to the null muxer with exit 0, and ImageMagick 7.1.2-29 prints XC 2x2 with exit 0. These probes check tool availability and command syntax only; a project render or generated image still needs its own visual check.

Read the media skill.