Yatoshi Video playback
Technical index
Contents index

Pack Contents: Every Component, the Formats and What Replaces It

A reference list rather than a distribution point. Each row names a component the bundle registered, the formats it handled, and the maintained package that covers the same ground now.

Components and Their Modern Equivalents

Filters registered by the pack across its release history, grouped by the job each did.
ComponentRoleFormatsCovered today by
Matroska splitter Splitter MKV, MKA LAV Splitter
MP4 and MOV splitter Splitter MP4, M4V, MOV LAV Splitter
AVI and OGM splitter Splitter AVI, OGM LAV Splitter
MPEG-4 ASP decoder Video decoder XviD, DivX, MPEG-4 Part 2 LAV Video
H.264 decoder Video decoder H.264, AVC LAV Video
MPEG-2 decoder Video decoder MPEG-2, DVD video LAV Video
AC3 and DTS decoder Audio decoder AC3, E-AC3, DTS LAV Audio
AAC decoder Audio decoder AAC, HE-AAC LAV Audio
Vorbis and FLAC decoder Audio decoder Vorbis, FLAC LAV Audio
Subtitle renderer Renderer SRT, SSA, ASS, VobSub Player-internal renderer
Windows Media module Optional WMV, WMA Present in Windows
QuickTime module Optional MOV, legacy Apple codecs LAV Video and LAV Audio

How to Read This List When a File Will Not Play

The table is organised by job rather than by format on purpose, because the job is what the symptom tells you. A file that refuses to open at all points at the splitter row for its container. A file that opens with one blank track points at a decoder row, and which row depends on whether the blank track is the video or the audio one. Text that never appears points at the renderer row, which is a separate stage again and the reason subtitle problems survive so many decoder installs.

Working from a symptom to a row takes one step through the diagnostic index, and from a row to a fix takes one more, because the right-hand column names something that is still maintained. The historical component is only ever the identification; it is never the recommendation.

The optional modules deserve a second look when a file is genuinely unusual. Those were the parts a general installation of the era would not have had, so a file that used to need one is a file using something outside the mainstream set. That is a much narrower starting point than the container extension, which frequently says nothing at all about what is inside.

Why the Splitter Column Matters More Than It Looks

Three splitters cover almost everything the bundle was used for, and they are the components most often blamed for the wrong thing. Matroska was the demanding one: a container that can hold several video tracks, a dozen audio tracks, chapter structures, attached fonts and both text and image subtitles asks considerably more of a splitter than an AVI does, and a splitter that handles it partially produces failures that look like decoder faults.

A partially handled container is the reason a file can play with the wrong audio track selected, or lose its second audio track halfway through, or open with no subtitle tracks listed when the file demonstrably contains them. None of that is a decoding problem, and installing decoders will not touch it. Recognising it early saves the usual cycle of adding components until something changes.

The modern replacement column collapses to a single name for all three splitter rows, which is the clearest illustration of what changed. One component now does the whole job, is maintained, and cannot compete with itself. That consolidation, more than any single format gaining support, is what made the bundle unnecessary. The archive entry covers the release history and the reasoning behind the original split.

Which of These Formats Are Still Encountered

A small external optical drive connected by cable to a closed laptop
Twelve components are listed here across three roles. Every one of them is covered today by a single maintained filter set.

The twelve rows do not age at the same rate, and separating them explains why some old files still open anywhere while others need thought. The container splitters have aged best: MKV and MP4 are more common now than when the bundle shipped, and AVI survives in archives. Anything that can read those three covers the great majority of files a reader will meet.

Among the video decoders, H.264 and MPEG-2 remain entirely ordinary, the first because it is still in wide use and the second because it is what every DVD contains. The MPEG-4 ASP row is the genuinely historical one: XviD and DivX encodes were the standard for downloaded video for roughly a decade and then stopped being produced almost entirely. Files in that format are now specifically the ones that fail on a fresh machine, because nothing has a reason to ship support for a format nobody encodes any more.

The audio rows split the same way. AC3 and DTS are alive in anything sourced from a disc, AAC is the default in modern recordings, and Vorbis has been largely displaced by Opus in new files while remaining common in older MKV releases. The two optional modules are the extinct end of the list: Windows Media formats are read natively by Windows and encountered mainly in old recordings, and the legacy Apple codecs that needed the QuickTime module are the single most likely thing to defeat a current player without one of the maintained filter sets installed.

Where to Get the Maintained Equivalents

Every component in the list above is covered by one of these. All are free.
SoftwareWhat it replacesSource
VLCEverything, for watching. Decodes internally, asks the system for nothing. videolan.org
mpvThe same, for a keyboard-driven player with no interface to speak of. mpv.io
LAV FiltersEvery splitter and decoder row above, in one system-wide install. github.com/Nevcairiel
MPC-HCThe player half, for anyone who wants the DirectShow chain rather than internal decoding. github.com/clsid2
K-Lite Codec PackA bundle, still maintained, if a single installer is genuinely wanted. codecguide.com
MediaInfoNot a decoder. Reports which codecs a file actually contains, which is the first step. mediaarea.net

One caution that applies to all of them: install one, not several. The whole failure mode documented on this page comes from two components registering a decoder for the same format and the operating system arbitrating between them by merit value.

Questions about the component list

Are the installers for these versions available here?

No, and deliberately not. Nothing on this site distributes decade-old unsigned executables for a system they were not built for. The value in the list is identification: knowing which component read a format tells you what a stubborn old file needs, and the maintained equivalent in the right column supplies it.

How can the components on an existing machine be listed?

A filter manager reads the registered DirectShow filters and shows them with their merit values. Anything appearing twice for one format is a conflict, and the merit value decides which one wins. That listing is also the fastest way to find out what an old bundle left behind after an uninstall.

Do optional modules matter for identifying an old file?

They matter most, because they were the parts a general installation would not have. A file that needed the QuickTime module is a file using an Apple codec that Windows never read natively, which narrows the search considerably compared with knowing only that it is a MOV.

Is a splitter needed separately from a decoder?

Yes, and confusing the two sends troubleshooting in the wrong direction. A splitter separates a container into tracks; a decoder turns one track into frames or samples. A missing splitter means the file will not open at all, while a missing decoder means it opens and one track stays blank.

Does removing an old bundle restore a working system?

Usually, though not always completely. Uninstallers of that era frequently left filters registered, so a system can keep preferring a component whose files are gone. Listing the registered filters after an uninstall and clearing the orphans is the step that finishes the job.

Published