What we know

In the last few years, a lot of useful information has appeared about the secrets of DCC. Old magazine articles, press conference handouts, course material for technicians who needed to repair DCC recorders, service manuals and service bulletins, and datasheets have shown up on the Internet in digital form, and the DCC Museum has managed to get in contact with several people who worked on DCC behind the scenes.

At this point, I'm not sure what the question is, but here are  a couple of answers:


All prerecorded tapes have information on them, encoded as ITTS (Interactive Text Service) data. This is a protocol that was originally designed for digital audio broadcasts, and is also in use on Sony's CD-Text system. The IEC standard for S/PDIF digital audio explicitly mentions how ITTS information is encoded in an S/PDIF digital output signal of a DCC recorder.

Most prerecorded tapes have an inlay that mentions that this "DCC-Text" feature can be seen with a recorder that's equipped to decode the service. There was never such a recorder, but prototype recorders have shown up that appear to have hardware to do this. Unfortunately that hardware is non-functional.

Also, several ITTS decoders have shown up in the world. These were boxes made in the UK with two microcontrollers and a Teletext decoder chip. Reverse-engineering of the ITTS decoder is underway: apparently one microcontroller extracts the ITTS stream from the subchannels (with help of an S/PDIF decoder IC) and passes it to the other microcontroller which generates a few pages of information that are shown on a screen by a Teletext decoder. Apparently these ITTS decoder boxes were used by music production companies to verify that the ITTS information was correctly encoded. There are several signs that these boxes were prototypes; for example the software for the microcontrollers is stored in separated EPROMs and the microcontrollers are just regulary 8032's. In a production version, Philips would surely have used a different version of this Intel microcontroller that would have made it difficult or impossible to extract the firmware. Also the box has no labels that a production model would have.

The ITTS decoder is connected to the digital output of a DCC recorder and the ITTS information is decoded from the subchannels in the S/PDIF signal. Unfortunately the ITTS decoder doesn't work with third generation recorders. We speculate that either (A) Philips and Matsushita gave up on the idea of ITTS altogether because it was too much work and they figured no-one would pay extra for it, or (B) it was simply impossible to implement it in the third generation firmware because e.g. the ROM was full with firmware to edit song names, or they simply ran out of time, or (C) the third generation recorders still generate ITTS information on the output but it uses a different format that the ITTS boxes don't understand. If the latter is true, we will find out.

The SAA2023/SAA3323, and Where We're Going

The SAA2023 and SAA3323 chips are the Drive Processor (DRP) chips for third generation recorders. Together with a microcontroller, they are the heart of the electronics of those recorders. The two chips are identical except for the supply voltage: stationary recorders use the SAA2023 (5V) and portable recorders use the SAA3323 (3.3V). As I mentioned above, this chip is extremely well documented.

The datasheet for the DRP chips shows exactly how a microcontroller can read and write AUXINFO and SYSINFO. AUXINFO is the auxiliary information that's encoded in the 9th track, such as label markers and song titles on Super User tapes. SYSINFO is the information that's stored and multiplexed with the music stream. It appears that SYSINFO is where all the interesting secrets are, such as SCMS (copy protection) information, pre-emphasis information, time code, table of contents, and ITTS data.

We have to keep in mind that this is 1995 technology, and there was no reason for engineers to design the SYSINFO protocol in a way that would be difficult to decode and encode. So we speculate that it's possible to use a logic analyzer to "listen in" on an SAA2023 or SAA3323 to find out what it has to say to the microcontroller when it's playing a prerecorded tape.

So what's the best way to do this? Well, step 1 is get into the system and the DCC-175 and PC-link cable will let us do that. We don't have the means or the time to reverse-engineer the PC-link cable. But we do have a logic analyzer to connect to the cable that goes between the parallel port plug and the DCC-175. It should be possible to "listen in" on that, and find out what the computer sends to the recorder to do things such as start playing, start recording, send line input to the PC, or put text on the DCC-175 screen. We also know that the DCC-Studio program reads the table from tape. Maybe once we know what the existing commands are, we can speculate on what other commands might be. We know the DRP records SYSINFO at the same time as audio, so even though DCC-Studio doesn't make it possible to write a continuous Table of Content, it's not unlikely that it sends SYSINFO data too.

The next step once we figure out how the PC-link cable talks to the DCC-175, is to try and replace the parallel port plug with a microcontroller. Interestingly enough, this should be the easy part. With the knowledge we have about the schematic of the DCC-175, we already know that we can probably connect a fast microcontroller like the Parallax Propeller; the hard part is to make it talk to the DCC-175 and be understood. Eventually, it should be possible to let a Propeller read all the information (audio, AUXINFO and SYSINFO) from a tape and store it on an SD card. And if we can figure out how to get that information back into the DRP, we can record our own prerecorded tapes.