• View Cart
    Shopping Basket CLOSE

    No products in the basket.

Blog CVD Guides Preservation & Ripping
, , , , , , , , , , , , , , ,
CVD Preservation, Ripping and Identification

Why CVD needs a two-layer archive

China Video Disc (CVD) shares the fragile sector model of VCD and SVCD. Form 2 sectors carry no Layer-2 ECC-only EDC and the CD’s CIRC. VCDImager warns that (S)VCD MPEG tracks “are more easily affected by scratches.” A preservation copy that only saves files from a mounted volume is therefore not an archive: it loses raw sector layout, error context and often wraps the MPEG in RIFF-CDXA that later tools misread as a plain program stream.

A good CVD archive has two layers. First, a raw, bit-exact disc image. Second, extracted playable MPEG program streams plus a structural description of the disc (INFO/ENTRIES/TRACKS, PBC, volume labels). The image answers “what was on the pressed or burned CD?”; the extracted streams answer “what can we play and remux tomorrow?” Copying files from a mounted disc satisfies neither question by itself.

Raw imaging

Tool Command / method Notes
cdrdao cdrdao read-cd --read-raw --datafile disc.bin --device /dev/sr0 disc.toc then toc2cue disc.toc disc.cue 2,352-byte raw sectors
CDRWin / IsoBuster / ImgBurn (Windows) Read to BIN/CUE in raw mode Record read errors
Any workflow Keep a log of read errors and retries Form 2 errors are not ECC-corrected

Raw mode matters because Form 2 payloads are not reconstructed by the same ECC path DVD and Mode 1 data enjoy. Retries and a written error log are part of the archival object, not optional debugging. Prefer imaging before heavy playback testing that might leave a marginal disc worse than you found it. On drives that struggle with Mode 2 Form 2, note the drive model in the read log: future re-reads may need a different mechanism even when the BIN already exists.

Structural extraction

vcdxrip “disassembles a given VCD or SVCD disc into a XML description and the contained MPEG program streams.” Run it against the image (vcdxrip --bin-file=disc.bin --cue-file=disc.cue) or against the drive. The resulting XML plus MPEG files can be edited and rebuilt with vcdxbuild. An Ubuntu Forums tip notes vcdxrip --nofiles extracts just the AVSEQ tracks as .mpg when you only need the elementary playback objects.

Do not trust a plain file copy. On Windows, copying /MPEG2/AVSEQnn.MPG or /MPEGAV/*.DAT yields RIFF-CDXA-wrapped data. VCDImager’s documentation is blunt: people tend to think of these as MPEG files, but they are not. Strip the wrapper with cdxa2mpeg, or better, use vcdxrip so structure and streams stay paired. IsoBuster users can open the MPEG2 folder and choose “Extract but filter only M2F2 Mpg frames.” VCDGear also extracts MPEG from CDXA files. Those tools are recovery aids; the raw BIN/CUE remains the preservation master.

When both a pressed commercial disc and a hobbyist CD-R are in the same collection, keep extraction recipes identical so that later comparison of INFO.SVD, TRACKS.SVD and program-stream widths is not confused by tool differences. Rebuild tests with vcdxbuild are useful for verifying that the XML description is complete, but a successful rebuild does not replace the original raw image.

Identifying CVD vs SVCD vs XSVCD

Check CVD SVCD (Philips/IEC) XSVCD
INFO.SVD system ID “SUPERVCD” “SUPERVCD” “SUPERVCD”
Video width (ffprobe) 352 480 480 (or other)
Bitrate ≤ ~2.6 Mbps ≤ ~2.6 Mbps Often higher
Subtitle stream CVD-style private_stream_1 (VLC: “CVD subtitles”) OGT 0x70-series Either
TRACKS.SVD vcd-info may print “CVD interpretation (probably)” IEC layout Usually IEC
Sequence folder /MPEG2 or /MPEGAV /MPEG2 Either
Disc type Pressed (commercial, 1998-1999) or CD-R Pressed or CD-R Usually CD-R

Only the resolution is decisive for the CVD-versus-Philips-SVCD distinction in practice. Folder names and TRACKS.SVD layout are suggestive, not conclusive: a 352-wide “XSVCD” made in the West in 2003 is structurally a CVD. Commercial Chinese discs from mid-1998 labelled CVD, or Super VCD discs from late 1998 carrying 352-wide video, are the true period objects. System ID “SUPERVCD” appears on all three columns and therefore cannot settle the question alone.

Operational checklist: dump structure with vcd-info against the CUE or BIN; probe each extracted track with ffprobe -show_streams -show_format; open the same streams in VLC and note whether it reports CVD subtitles; photograph packaging and matrix/IFPI/SID codes before the disc is filed away. When vcd-info hints at a “CVD interpretation,” treat that as supporting evidence beside the 352-wide measurement, not as a substitute for it.

Archival packaging and documentation

  1. Keep the raw BIN/CUE (or TOC) and its read log.
  2. Keep vcd-info output as a text file.
  3. Keep ffprobe -show_streams -show_format -of json output for each track.
  4. Photograph the disc (both sides), inlay, case and any matrix / IFPI / SID codes.
  5. Hash the BIN and every extracted MPEG (SHA-256).
  6. Make lossless access copies: ffmpeg -i avseq01.mpg -c copy -map 0 out.mkv keeps video, audio and subtitle streams together. Transcode only for convenience copies.
  7. Record provenance: where bought, price, whether bundled with a player, and which brand of player actually plays it.
  8. For 1998-1999 commercial discs, also record whether the disc plays on players from different brands-evidence relevant to the contemporary “interference code” compatibility disputes.

Lossless Matroska access copies are for day-to-day playback and subtitle checks in VLC; they do not replace the raw image. If a private subtitle stream exists, -map 0 is what keeps it. Dropping to a video+audio-only remux for “simplicity” is a preservation error when CVD-style or OGT packets were present on the original. Hashing both the BIN and the extracted MPEGs lets you detect silent re-rips later without reopening every tool log.

Identification pitfalls

Hobbyist CD-Rs labelled SVCD, XVCD or XSVCD may be 352-wide CVD-structured discs, 480-wide IEC SVCDs, or over-rate XSVCDs. Commercial packaging that says 超级VCD may still carry 352-wide video from the Chaoji transition period. Conversely, a Western “SVCD” burn at 480-wide with OGT subtitles is not a period Chinese CVD even if a Chaoji player plays it. Bitrate above the ~2.6 Mbps community ceiling suggests XSVCD or a non-compliant hobby encode regardless of folder names.

PC Explorer copies that “play in VLC” can still be CDXA-wrapped; always confirm with a proper rip or cdxa2mpeg before declaring an archival MPEG. Players that ignore CVD-style subtitles can make a disc look subtitle-free when VLC would report otherwise. Standalone “plays / does not play” notes should name the player brand and model: 1998 interference-era discs may fail on rivals’ Chaoji machines while succeeding on the issuing brand. Guangming Daily and Wenzhai Bao coverage of late-1998 compatibility contests and “interference codes” is why cross-brand play notes belong in the archive package, not only in forum anecdotes.

Putting the workflow together

A minimal responsible pipeline for a newly acquired CVD or Super VCD candidate is: photograph and note provenance; raw-image with error log; vcdxrip (or IsoBuster M2F2 extract) to clean MPEGs plus XML; vcd-info and ffprobe sidecars; SHA-256 hashes; lossless MKV access copy; VLC subtitle check; optional hardware play notes across brands for commercial 1998-1999 discs. Only after that stack exists should the physical disc be treated as replaceable for routine viewing.

Preservation of CVD is therefore less glamorous than format archaeology and more like careful CD-XA work: protect the Form 2 sectors, refuse mounted-file illusions, measure 352 versus 480, and keep private subtitle streams attached to the program stream. Identification follows measurement; nostalgia labels on the jewel case do not. When later catalogue posts ask whether a survivor is “true period CVD,” the answer should be readable from this package-width, subtitle flavour, press-versus-burn medium, and any selective playback failures-without inventing titles the disc face never carried.

The same discipline applies when a disc arrives as a BIN/CUE from someone else. Re-run vcd-info and ffprobe yourself; verify hashes if the donor provides them; and do not assume their “CVD” label survived a width check. Community encodes from the early 2000s often used SatStorm’s 2,520 kbps half-D1 recipe under an SVCD authoring path-structurally CVD-like, commercially unrelated to 1998 Chinese pressings. Archival notes should say which case you have, in plain language, so the next reader does not merge hobbyist CD-Rs with period Chaoji stock.

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 EVD Guides Preservation & Authoring
, , , , , , , , , , , , , , , ,
EVD Preservation, Identification and Authoring

Authoring today is not a hobbyist path

Enhanced Versatile Disc (EVD) discs were not something end users burned at home with Nero-class tools. EE Times in 2006 described Jindian Global as “the only EVD disc maker.” PjTime’s overview of E-World’s professional software names the toolchain that sat behind that monopoly: DVD-to-EVD conversion, AC-3-to-EAC conversion, the OGT subtitle authoring system and the EVD digital video disc authoring system. None of those tools, and none of the SJ/T 11299 standard texts, are publicly available. Video and audio were protected by proprietary encryption.

A step-by-step hobbyist guide to making a playable EVD disc therefore cannot be written from current evidence. Anyone promising a modern “author your own EVD” recipe is either rebranding ordinary DVD authoring or inventing steps the public record does not support. The rest of this post covers what can still be done with existing discs and players: identification, imaging, documentation and hardware care.

Identifying a genuine EVD disc

Check Genuine EVD DVD labelled EVD
Publisher mark Jindian Global (今典环球), Zhongkai (中凯), China Film (中影), China Record (中唱), 山力, 飞仕, 盈艺 Any
Logo EVD logo on disc and case Often “EVD” only in listing text
Period 2004-2008 Any
Standard DVD player Should refuse or show no playable title Plays normally
PC file listing Non-VIDEO_TS structure (expected; undocumented) VIDEO_TS with IFO/VOB
版号 / ISRC Present on legitimate releases –

The modern retail keyword “EVD” on Chinese DVD players is not evidence of a genuine 2004-2008 EVD deck with LSI Logic decode silicon. The same caution applies to discs. A listing that only types “EVD” into the title field while the photographs show ordinary DVD artwork is a DVD until proven otherwise. Ask for publisher marks, an EVD logo on the disc face and case, and a short playback note on a known ordinary DVD player. A genuine title should fail or show nothing playable on that ordinary deck; a mislabelled DVD will play.

On a PC, expect a non-VIDEO_TS layout. The exact directory and file names remain undocumented, so the first public file tree from a commercial disc would itself be a research contribution. Presence of VIDEO_TS with IFO/VOB files is strong evidence that the object is ordinary DVD Video, regardless of how many times the seller wrote EVD in the advertisement.

Imaging an EVD disc on Linux

EVD is physically a DVD with a UDF file system, so ordinary DVD tools can image it. The commands below are standard DVD-imaging procedures. They have not been tested on an EVD disc by any source found for this series; treat them as a reasoned starting procedure, not as a verified EVD cookbook.

# 1. Identify the drive and disc
lsblk
sudo dvd+rw-mediainfo /dev/sr0

# 2. Make a sector image with error logging
sudo ddrescue -b 2048 -r 3 /dev/sr0 evd_title.iso evd_title.map

# 3. Hash the image
sha256sum evd_title.iso > evd_title.iso.sha256

# 4. List the UDF directory tree without mounting
7z l evd_title.iso > evd_title_filelist.txt
# or mount read-only:
sudo mkdir -p /mnt/evd && sudo mount -o ro,loop -t udf evd_title.iso /mnt/evd
find /mnt/evd -printf '%pt%sn' > evd_title_tree.txt

# 5. Probe any large media files found
for f in $(find /mnt/evd -type f -size +10M); do
  ffprobe -hide_banner "$f" 2> "$(basename "$f").probe.txt"
done

If the disc uses CSS-style drive authentication, ddrescue will report read errors on protected sectors. Record those errors rather than retrying indefinitely. Publishing the output of the file-tree and probe steps would be the first public documentation of the EVD file system. That publication value is why imaging belongs ahead of aggressive playback experiments that might leave a marginal disc worse than you found it.

Imaging on Windows

ImgBurn: Mode, Read, select the drive, choose a destination .iso, then Read. Keep the log. IsoBuster can inspect the UDF structure, export a file list (right-click, Extract / File list), and record sector ranges of large files. 7-Zip can open the .iso to list files. MediaInfo or ffprobe should be run on any large files to see whether they parse as MPEG-2 program or transport streams. Even a “does not parse” result is archival evidence when paired with the file tree and hash.

Documentation package for each disc

  1. Raw ISO image with read log and SHA-256 hash.
  2. File tree listing with sizes.
  3. ffprobe / MediaInfo output for all large files.
  4. Photographs of disc (both sides, including inner-ring matrix/SID codes), case, inlay and any EVD logo.
  5. Publisher, 版号, ISRC, price and purchase source.
  6. Playback test results on a genuine EVD player and on an ordinary DVD player.

The dual playback note is the cheapest authenticity filter. Ordinary DVD behaviour plus VIDEO_TS layout means you imaged a DVD. Refusal on a standard deck plus a non-VIDEO_TS tree plus a period publisher mark is the evidence pattern the identification table predicts for genuine EVD. Hashes and probe sidecars let later researchers compare finds without shipping discs.

Preserving players

Keep the original remote, manual, warranty or repair card and box. Those objects document model and date when the chassis sticker is incomplete. Record the LSI Logic chip marking and any firmware version shown in the setup menu. Store laser pickups away from heat; DVD-era pickups lose output with age. Test component HD output at 1080i and 720p with a display that still accepts analogue component video, and write down which timings worked.

Again, modern shop listings that print “EVD” on a portable DVD player are not substitutes for a documented 2004-2008 model with LSI Logic decode. Preservation notes should name the chip marking you saw, not the marketing keyword on a 2020s carton.

What would unlock EVD

  • The texts of SJ/T 11299.1-4 (disc, file system, A/V data, ExAC audio).
  • A copy of E-World’s EVD authoring system or the 影海风雷 PC player.
  • A published file tree and sample streams from a commercial disc.
  • The LSI Logic decoder part number and firmware from a genuine player.

Those four unlocks map directly onto the gaps that stop authoring guides and soft playback. Standards texts would define containers and audio; authoring or PC-player binaries would show how encryption and menus were applied; a published file tree would end speculation about directory layout; LSI Logic part numbers would tie living-room hardware to silicon documentation. Until they appear, EVD preservation work is imaging, photographing, hashing and refusing to invent playable DIY burns.

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: