MKV can combine several video, audio, subtitle, chapter, and attachment tracks. Echoryte validates the Matroska family and requires real speech audio before creating a synchronized transcript.
Where this workflow fits
- Long-form video programs
- Multilingual media archives
- Chaptered lecture recordings
Matroska and WebM are not synonyms
Matroska is deliberately flexible, while WebM constrains a subset of the family. Because the demuxer response can include both names, the ingest boundary uses the validated upload extension and stream evidence instead of rewriting MKV as WebM.
Choose the intended audio track
A feature or lecture may include original audio, dubbed tracks, descriptions, and commentary. Confirm the program before transcription, then check speaker labels and chapter transitions against the picture.
Before you upload
- Check the active audio language and commentary flags in a media inspector before upload.
- Keep chapter and production notes available when speakers or scenes change across a long program.
Limits worth knowing
- Multiple audio programs can make the wrong language or commentary track appear to be the primary stream.
- Embedded subtitles are separate assets and are not treated as proof of what the selected audio says.
Questions from the workflow
Why is an MKV not automatically called WebM?
WebM is based on Matroska, so FFprobe can report a shared family name. Echoryte retains a validated .mkv extension rather than assuming every Matroska-family file is WebM.
Reviewed sources
- IANA Media Types registry · checked 2026-07-20
- RFC 9559: Matroska media types · checked 2026-07-20