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: