Blog EVD Guides PC Playback
EVD on the PC: Software Playback Realities

PC playback was promised, then politically toxic

Enhanced Versatile Disc (EVD) was sold as a living-room format, but E-World also listed a PC player among its five software packages. That software mattered commercially and strategically. Contemporary Chinese coverage names a product line that included a “VCD/DVD/EVD播放器” package, and English Wikipedia notes that prototype software players were already being presented in April 2004. By late 2005 a licensed unofficial beta existed under the 影海风雷 EVD player name, developed by Beijing Shengshi Longtian under licence from E-World and released as an unofficial beta on 29 October 2005. Chinese Wikipedia records that no official release had followed by 10 December 2005.

The same December 2005 window is when the PC player became a political problem inside the EVD camp. Zhang Baoquan feared that a working PC player would expose EVD’s encryption. Jindian Global announced a switch toward AACS. That split is treated in the history and standards posts of this series; the practical consequence for software archives is blunt. No copy of either the E-World-linked PC player or the 影海风雷 beta has been found in public software archives. Collectors therefore cannot today verify period PC behaviour against the discs they hope to preserve.

Official and licensed software that is missing

Software Detail Source
“VCD/DVD/EVD播放器” One of E-World’s five software packages PjTime
影海风雷 EVD player Licensed beta from Beijing Shengshi Longtian; unofficial release 29 Oct 2005; no official release as of 10 Dec 2005 Chinese Wikipedia
Prototype software players Presented April 2004 English Wikipedia

PjTime’s 2007 overview of EVD lists five E-World software packages that together describe how the format was supposed to be mastered and consumed: DVD-to-EVD conversion, AC-3-to-EAC conversion, the OGT subtitle authoring system, the EVD digital video disc authoring system, and the PC player package. Only the player row belongs in this post, but the full set explains why the missing PC software is not a minor collector inconvenience. Without the player binary, encryption behaviour, container expectations and ExAC audio handling remain opaque even if a disc image exists.

The April 2004 prototype presentations and the October 2005 unofficial beta prove that a PC path was under active development during EVD’s commercial years. They do not prove that ordinary buyers ever received a finished, supported desktop player. Absence from public archives is not proof that no private copies survive in old OEM bundles or collector hard drives; it is only proof that researchers working from open repositories cannot reproduce the period soft-player experience.

What the encryption fear implies for soft decode

Zhang Baoquan’s reported fear that a PC player would expose EVD’s encryption is the clearest period statement that shipping discs were not meant to be casually demuxed on a PC. If that fear was well founded, then even recovering a 影海风雷 installer would not automatically yield a clean open description of the container. It might still be the best available oracle for how titles, keys and streams were arranged. Until such a binary surfaces, open-source tooling can only attack the pieces that are already public: VP6 decode, generic MPEG-2 High Level decode, and ordinary UDF disc imaging.

Open-source support today

Component Status Source
VP6 decoder libvp62 appeared March 2006; part of FFmpeg stable from 0.5 (March 2009) VP6 Wikipedia
MPEG-2 MP@HL decoding Supported by FFmpeg, VLC, mpv Common player stacks
ExAC / EAC audio No open decoder known –
EVD encryption No open implementation known –
EVD container / file layout Undocumented –

If shipping EVD video is MPEG-2 based, as later EE Times coverage of the 2006 relaunch argued, the video elementary stream itself would be decodable once decrypted and demuxed. The blocking problems named in the research set are the proprietary encryption, the undocumented container and ExAC (also written EAC in some E-World material) audio. Those three gaps sit in front of any FFmpeg or VLC success story. Soft-decode support for MPEG-2 MP@HL in modern players is therefore necessary but nowhere near sufficient.

VP6 support in FFmpeg has a clear chronology: libvp62 appeared in March 2006, and VP6 landed in FFmpeg stable from version 0.5 in March 2009. That timeline is only relevant to EVD if a VP6-based EVD disc exists. Launch-era English press (EDN, November 2003) announced On2 VP5/VP6 as the video story; later EE Times reporting described MPEG-2 MP@HL for commercial discs. Those are source disagreements kept side by side elsewhere in this series. For PC playback planning, the practical rule is simple: the VP6 decoder in FFmpeg does not prove that any pressed EVD title will open as VP6, and an MPEG-2 High Level path does not prove that an encrypted EVD file will demux cleanly.

What a modern PC can and cannot do

A modern PC can image an EVD disc as ordinary DVD/UDF media, list files once the image exists, and probe large objects with ffprobe or MediaInfo. Those steps belong to the preservation post. They are not the same as playback. Playback requires decrypting whatever protection the disc uses, understanding the undocumented layout, and decoding ExAC/EAC if that is the audio track in use. None of those three capabilities has an open implementation in the sources reviewed for this series.

VLC, mpv and FFmpeg can play ordinary MPEG-2 High Level streams and can play VP6 when the container is known. They cannot substitute for the missing E-World PC player when the input is still an encrypted EVD title. Collectors who mount a disc and see unfamiliar directories should treat that as useful file-system evidence, not as a playable VIDEO_TS DVD. Genuine EVD discs are expected to use a non-VIDEO_TS structure; ordinary DVD labelled “EVD” in a modern shop listing will usually show VIDEO_TS with IFO/VOB and will play on any DVD deck.

Research posture for software hunting

The highest-value missing artefacts for PC work are copies of the 影海风雷 beta, any finished E-World “VCD/DVD/EVD播放器” package, and any OEM disc that bundled either. Secondary targets are screenshots, installer hashes, Help-file text and registry notes from period Chinese PC magazines. Tertiary targets are forum posts that describe menu trees or error messages from those players, even without the binary. Each of those classes can constrain how the undocumented container behaved without requiring a full reverse-engineering effort.

Until such material appears, the honest summary of EVD on the PC is: soft-player development was real in 2004-2005; an unofficial licensed beta existed; fear of encryption exposure helped fracture the content camp in December 2005; and no public archive currently holds the player. Open-source stacks cover VP6 and MPEG-2 High Level video in the abstract, but they do not cover EVD encryption, the EVD container or ExAC audio. PC playback of genuine 2004-2008 EVD titles therefore remains a research problem, not a weekend VLC recipe.


Further reading on historic video formats

If you want to learn more about historic video formats, get The History of Physical Video Formats from the Frontier by Stephen Driver on Amazon:

Blog CVD Guides PC Playback
CVD on the PC: Software Playback Realities

CVD was never a closed PC format

China Video Disc (CVD) differs from later Chinese high-definition formats in one practical respect that still shapes archives: an ordinary PC could always read the disc. Any CD-ROM drive that understands Mode 2 Form 2 sectors can read a CVD, and any software MPEG-2 decoder can play the elementary video and audio once the wrapper is handled correctly. VideoHelp’s Super Video CD overview states the same rule for SVCD and, by extension, CVD: playback works on computers with a DVD-ROM or CD-ROM drive plus a software decoder or player. There is no proprietary PC optical drive, no blue-laser dependency and no DRM layer comparable to later HD formats.

That accessibility is why CVD survived as a hobbyist and preservation topic long after dedicated launch decks vanished. It is also why file-copy mistakes are common: Windows will show playable-looking track names while still handing the user a RIFF-CDXA container rather than a plain MPEG program stream. The rest of this post separates period PC behaviour (1998-2005) from the modern software map, then focuses on the subtitle decoder gap that still trips identification work.

Period PC playback (1998-2005)

On a mounted CVD or SVCD, Windows typically exposes MPEG tracks as AVSEQnn.MPG files under /MPEG2, or as .DAT files under /MPEGAV. Those objects look like ordinary MPEG files in Explorer, but they are RIFF-CDXA wrapped. Players that understand CDXA-Windows Media Player with an MPEG-2 decoder pack, PowerDVD, WinDVD-could open them directly in the DVD-ROM era. Tools that expect a bare program stream will fail or play poorly until the wrapper is stripped with cdxa2mpeg or, better, with a structural ripper such as vcdxrip.

Hardware MPEG-2 decoder cards from the same period also handled CVD streams. C-Cube’s ZiVA family, sold into PC OEM channels including Dell according to C-Cube’s SEC filings, is the named bridge between CVD’s launch silicon story and desktop playback. A machine with a ZiVA-based decoder card could treat CVD the way it treated other MPEG-2 CD formats without waiting for CPU soft-decode performance to catch up. That continuity matters historically: the same vendor selling CVD/Chaoji decoders into Chinese living-room players was also selling MPEG-2 decode into Western PCs.

Subtitles were already a known weak point. Russil Wvong’s Video CD FAQ, updated March 2000, notes that some software players of the time “can’t show SVCD or CVD subtitles,” while others could. That split still matters: video may look fine while the CVD private subtitle stream is silently ignored. Period PC success therefore never meant “full authored experience,” only that the optical and MPEG layers were ordinary enough for consumer software.

Modern software map

Player Disc (vcd://) Extracted MPEG CVD subtitles Notes
VLC Yes (vcd://, including images) Yes Yes – dedicated CVD subtitle decoder Best single check for CVD-style subs
MPC-HC / MPC-BE Build-dependent Yes Not verified Program streams play without trouble
mpv Not verified Yes Not verified Use extracted files
MPlayer Historically vcd:// tracks Yes – Legacy path
xine Full VCD support Yes – Code later moved toward VLC
ffprobe / ffmpeg n/a Yes Visible as private data Diagnostic use

VLC is the practical default for identification work. It accepts vcd:// input against physical discs and disc images, plays extracted MPEG program streams and ships a dedicated CVD subtitle decoder documented on the VideoLAN wiki. Plugin lists for VLC builds explicitly include that CVD decoder. For a quick “is this really a CVD with CVD-style subtitles?” check, VLC is the one tool that answers both the video and the private-stream questions without a separate muxing step.

MPC-HC and MPC-BE play extracted program streams reliably; disc-protocol support and CVD subtitle behaviour are build-dependent and not verified across the whole family. mpv is likewise verified for extracted files rather than for native VCD protocol or CVD subtitle decode. MPlayer historically offered vcd:// track selection. xine’s VCD support matters historically because, per Wvong’s FAQ, the developer of that player-independent VCD code later moved the same work into VLC-the lineage behind much of VLC’s VCD handling today. ffmpeg and ffprobe do not replace a player for subtitles, but they show private data streams and confirm frame size, MPEG-2 video and MP2 audio parameters when you are classifying a rip.

Why CVD subtitles need a special decoder

CVD subtitles are only useful if the player understands the reverse-engineered CVD subtitle format, not merely “some private stream.” VLC’s dedicated decoder is the maintained open implementation most often cited for that format. SVCD’s competing subtitle flavour is Overlay Graphics Text (OGT). VCDImager accepted private_stream_1 IDs 0x70-0x73 for OGT in 2001 after a request from the DVD2SVCD authors-evidence that Western SVCD tooling standardised on OGT while Chinese CVD practice also carried the older CVD-style packets. The exact private_stream_1 sub-IDs used by CVD-style bitmaps (sometimes assumed as 0x00-0x03) remain unverified against a corpus of pressed discs; treat that as an open research question when logging ffprobe output.

For archiving, keep subtitle streams inside the program stream, or remux losslessly to Matroska with a full stream map (for example ffmpeg -map 0), so they remain decodable in VLC even when other players ignore them. Burning subtitles into the picture solves compatibility at the cost of switchability and bitrate. Extracting only the video and primary audio without the private stream permanently loses selectable CVD subtitles for any future decoder.

Practical PC workflow today

A sensible modern path separates three jobs: mount or image the disc, extract clean program streams, then verify playback and subtitles. Imaging and structural extraction belong with preservation practice; on the playback side, prefer VLC against either the image via vcd:// or against MPEG files produced by vcdxrip / cdxa2mpeg rather than against Explorer copies of AVSEQ*.MPG. If VLC reports CVD subtitles, record that fact in the archive notes-it is stronger identification evidence than folder names alone, because INFO.SVD system ID “SUPERVCD” is shared with Philips SVCD.

When VLC plays video but shows no subtitles, do not assume the disc has none. Confirm with ffprobe whether a private stream exists; try an alternate subtitle flavour if the disc was authored as SVCD OGT; and remember Wvong’s 2000 warning that subtitle support has always been uneven across PC players. MPC-family builds that play the picture cleanly may still be silent on CVD-style text. Width from ffprobe (352 versus 480) remains the decisive CVD-versus-SVCD check even when subtitle decode fails.

What PC playback does not prove

Successful PC playback does not prove a Western standalone DVD player will accept the same disc. Standalone compatibility rates for CVD remain contested community estimates-claims in forum memory range from roughly 30% of NTSC players to effectively all SVCD-capable decks-and those figures are not PC software results. PC success also does not prove a file copy is archival: RIFF-CDXA wrappers copied from a mounted volume are convenience objects, not bit-exact Mode 2 Form 2 images. Conversely, a PC that fails to show CVD subtitles does not prove the subtitle stream is absent-only that the chosen decoder path does not implement CVD-style private packets.

CVD on the PC is therefore best described as “always readable, not always fully decoded.” Mode 2 Form 2 readability and MPEG-2 soft decode cover the picture and sound for nearly any machine of the last twenty-five years. CVD-style subtitles, CDXA unwrapping and honest identification of 352-wide versus 480-wide SVCD still require tools that were written with those Chinese-era details in mind. VLC, VCDImager-family rippers and ffprobe form the short modern toolkit; PowerDVD/WinDVD and hardware ZiVA cards explain how the same discs worked when CVD was new. For a preservation session, treat PC playback as the verification layer after a raw image exists-not as a substitute for imaging-and log which player build reported CVD subtitles so later readers can reproduce the check.


Further reading on historic video formats

If you want to learn more about historic video formats, get The History of Physical Video Formats from the Frontier by Stephen Driver on Amazon:

Blog CBHD Guides PC Playback
CBHD on the PC: Playback Realities

Dedicated hardware first

Research passes found player software support outside dedicated CBHD hardware virtually nonexistent for ordinary consumers. Standard PC players-PowerDVD, VLC and contemporaries-did not support pressed CBHD discs. No Windows or Mac drivers or public PC CBHD decoder catalogues turned up. PowerDVD 7.x and early 8.x, WinDVD and TotalMedia Theatre handled HD DVD and AACS, not DKAA or FSM discs. Home playback of commercial CBHD software required Shinco or TCL players running their Linux-based firmware.

That historical finding has a careful caveat: one pass warns that “there were no PC decoders” has not been proven as an absolute. CBHD PC playback software and a CBHD emulator remain unresolved research targets rather than confirmed absences. Until such software surfaces, the practical statement stands: living-room and study use meant owning a CBHD deck.

Conflicting claims about PC drives reading sectors

One research pass states that computer HD DVD drives-Xbox 360 External HD DVD Drive, LG GGW-H20L, Toshiba SD-H4532-work at the SCSI/ATAPI command layer and, connected to a modern computer, can read raw sectors of a physical CBHD disc without firmware modification, passing encrypted or unencrypted AVS/DRA data to the operating system. Tools such as MakeMKV or specialised drive utilities could then extract streams, with FFmpeg (libxavs builds) decoding AVS video.

Other passes contradict the easy-read story. CBHD’s 4-6 FSM modulation differs from HD DVD’s 8-12 ETM. HD DVD players do not play CBHD. A drive needs FSM-capable channel hardware such as the Novatek NT90912 if the front-end must demodulate the CBHD channel correctly. No pass cites a controlled test of an HD DVD PC drive against a real CBHD disc. Treat sector-read claims as hypotheses until someone publishes a dump log.

What a successful PC read would still leave undone

  1. UDF parse and CBHD-specific directory conventions.
  2. CETC navigation interpretation.
  3. DKAA or AACS decryption.
  4. AVS and DRA demux/decode.
  5. Playlist and menu behaviour matching living-room players.

Sector access is only the first gate. Even if an HD DVD PC drive returned bytes, those bytes are not a finished movie file.

Playing material after rip or decrypt

Once elementary streams are available outside DRM:

  • AVS video decode: FFmpeg cavs (Jizhun profile) into mpv, MPC-HC via LAV Filters, probably VLC.
  • AVS transcode: FFmpeg with libxavs.
  • DRA audio: Tsinghua thesis codec (tianyigeng/DRA-Audio-System) or conversion; commercial Synopsys/Tensilica DRA IP exists in silicon, not as desktop apps.
  • DKAA: no decryption software found.
  • AACS international titles: standard AACS research path applies.

Mainline FFmpeg still lacks DRA. AVS+ (broadcast profile) support was only proposed in a 2026 RFC and is not merged. Confusion with FFmpeg’s unrelated game-format avs decoder remains a documentation trap.

USB and network as the documented “PC content” route

Original hardware already offered file-based playback that does not require burning CBHD discs:

  • Shinco CBHD-9100: front USB plays TS and MP4 files and 1080p video; loads external subtitles. Documented as the only realistic home-content route on original hardware in one pass.
  • Shinco HD-3700U: AVI from USB flash drives; Ethernet network playback from remote media servers and shares per factory manual.

Those paths use the player’s SoC decoders on ordinary files. They do not prove that a DVD burner can produce a pressed-compatible CBHD volume. For archivists who own a working deck, USB/network ingest is the low-friction way to watch modern encodes on period silicon without solving FSM mastering.

Emulation and firmware as PC-adjacent work

Dumping player firmware is a PC task even when playback stays on hardware. The TCL THBD-1008 stores firmware in a Spansion S29GL256N 32 MB NOR flash-an explicit dump target. Firmware may contain CETC parsers, file-system parsers, codec libraries, DRM implementation, hardware register definitions and strings naming internal file structures. No CBHD firmware files, update discs (升级光盘/固件) or public dumps were found in the passes.

HD DVD firmware archives (hddvd-revived catalogue, hd-dvd.org, Internet Archive Toshiba update sets, AVForums European Toshiba dumps, Reddit r/HDDVD emulator threads) are useful comparison material because the THBD-1008 reuses Toshiba HD-A30 lineage boards. They are not CBHD firmware. Generic drive cross-flash tutorials (LG/Renesas, MakeMKV UHD flashing, DVDFab guides) likewise transfer technique, not CBHD bitstreams.

Practical workflow sketch for researchers

  1. Obtain a commercial CBHD disc and at least one working player (ideally Shinco CBHD-9100 and TCL THBD-1008).
  2. Photograph optical pickup labels before scavenging donors.
  3. Attempt sector imaging with candidate blue-laser drives; record whether FSM hardware is present (e.g. Novatek NT90912 lineage).
  4. If bytes emerge, parse UDF and compare directory trees against CBHD_TS / HVDVD_TS / ADV_OBJ hypotheses and against DCA Book 3 assumptions.
  5. Separate AACS titles from DKAA titles before attempting decrypt.
  6. Decode AVS with cavs; route DRA through the thesis codec.
  7. Use USB file playback on the 9100/3700U for non-disc test encodes.

Until a published drive test resolves the FSM read conflict, do not plan a preservation pipeline that assumes any Xbox 360 or LG HD DVD drive will image CBHD. Plan for the possibility that only FSM-aware Chinese combo mechanisms or instrumented player dumps will yield clean sector images.

Summary table

Question Status
Retail PC CBHD player software Not found; absence not fully proven
PowerDVD / WinDVD / TMT CBHD support No
HD DVD PC drive reads CBHD sectors Claimed by one pass; contradicted by FSM analysis; untested
AVS decode after decrypt Yes via FFmpeg cavs
DRA decode Thesis codec / conversion only
DKAA decrypt on PC None found
USB file playback on hardware Documented on CBHD-9100 and HD-3700U

PC work on CBHD is therefore mostly imaging, firmware analysis and post-decrypt transcoding-not dropping a disc into a Windows tray and pressing Play.

Why living-room software never appeared

CBHD launched into a China-first retail strategy with Shinco and TCL Linux players as the intended clients. CHDA did not need a PowerDVD SKU to sell bundles at GOME. International PC decoder vendors already carried HD DVD and Blu-ray roadmaps; adding DKAA, CETC and FSM-aware drive support for a format with tens of thousands of players was unattractive. The result is an archival gap: ripped AVS may play in mpv today, but the path from pressed disc to remux still crosses undocumented DRM and possibly undocumented channel hardware.

Gemini’s claim that unmodified Xbox 360 External HD DVD, LG GGW-H20L or Toshiba SD-H4532 drives can pull raw CBHD sectors must be tested publicly before pipelines depend on it. Claude and ChatGPT passes insist FSM demodulation is a hardware property of chips such as Novatek NT90912. If those passes are right, PC imaging requires FSM-aware fronts. If Gemini is right, ordinary HD DVD ATAPI drives already return useful bytes and the remaining work is UDF, CETC and DRM. Until a hex dump and drive model are published together, preserve both hypotheses in lab notes.

Player USB paths as controlled experiments

When researchers encode AVS with libxavs and copy TS/MP4 files to USB for the CBHD-9100, they test SoC decode without claiming to have authored a CBHD disc. The HD-3700U’s Ethernet share playback similarly exercises network stacks documented in its factory manual. Those experiments are valuable and should not be conflated with ImgBurn-to-DVD+R claims about CBHD_TS trees. Keep lab logs explicit about which gate was tested: file decode, UDF parse, navigation accept, or pressed-media channel read.

Firmware on the bench

Dumping the THBD-1008 Spansion S29GL256N yields a 32 MB artefact that may contain CETC parsers, filesystem parsers, codec libraries, DRM code and hardware register strings. No public dump is known. Comparative HD DVD firmware sets from hddvd-revived, hd-dvd.org, Internet Archive Toshiba archives and AVForums European threads help map Toshiba-lineage structures on the THBD-1008 board but must not be flashed onto CBHD units casually-GPIO and memory maps differ enough that cross-flashing is described as a brick risk. Treat firmware work as read-only analysis until write procedures are understood.

Recommended lab notebook columns: disc title and whether domestic/international; player model; drive model and chipset markings; imaging tool and sense data; UDF volume identifiers; top-level directories observed; encryption indicators; elementary codec FourCCs after demux; player USB file tests as a separate row. That discipline prevents one successful USB playback from being misread as proof that DVD+R authoring works.


Further reading on historic video formats

If you want to learn more about historic video formats, get The History of Physical Video Formats from the Frontier by Stephen Driver on Amazon: