SIDDecode Tools and Techniques: Extracting Music Data from Commodore 64 Files

How SIDDecode Works: Step-by-Step Tutorial for Chiptune Enthusiasts

What SIDDecode is

SIDDecode is a tool that reads and interprets SID (Sound Interface Device) files—music files created for the Commodore 64’s SID chip—and converts their data into a form you can analyze, play back, or convert to modern formats. This tutorial walks through how SIDDecode processes a SID file and shows practical steps to inspect, decode, and export its audio or data.

Prerequisites

• A SID file (commonly .sid or .prg)
• SIDDecode installed (or a similar SID parsing tool)
• A hex editor or SID file metadata viewer (optional)
• Basic familiarity with command line (recommended)

1. Inspect the SID file header

SID files include a header that describes metadata and how to play the tune. Key header fields:

• Magic ID: identifies file as a SID (usually “PSID” or “RSID”)
• Version: format version
• Data offset: where the SID data begins
• Load address / init / play addresses: CPU addresses used by the player
• Number of songs, start song
• Play speed flags and metadata (name, author, released)

Step:

1. Open the file in SIDDecode or a hex viewer.
2. Read and verify the magic ID and version.
3. Note the data offset and load address for later mapping.

2. Load the SID driver and tune data

SID files bundle a small 6502 machine-code player (driver) and the tune data. SIDDecode separates these parts and maps them into a virtual C64 memory space so the player can be analyzed or executed.

Step:

1. Use SIDDecode’s load function to place the driver at the correct memory address.
2. Confirm the init and play routine addresses match header values.

3. Emulate the SID player (optional but common)

To reproduce audio exactly, SIDDecode can emulate the 6502 CPU and SID chip registers. Emulation runs the init routine once and repeatedly calls the play routine at a fixed rate (typically 50 Hz for PAL or 60 Hz for NTSC), while simulating SID register writes to produce waveforms.

Step:

1. Run the init routine with the specified start-song parameter.
2. Call the play routine at the correct frame rate.
3. Capture SID register outputs each frame for synthesis.

Notes:

• Some files rely on raster timing or system quirks; a precise emulator is necessary for accurate playback.
• Emulating the SID chip involves approximating its oscillators, filters, and envelope generators.

4. Decode tune data structures

Beyond emulation, SIDDecode can parse the tune’s internal data structures—pattern tables, note streams, effect commands, and instrument definitions—so you can analyze composition techniques or convert to modern trackers.

Step:

1. Identify pointers to pattern/sequence data inside the tune area.
2. Parse note/event encodings (e.g., note number, instrument index, volume/effect bytes).
3. Extract instruments (ADSR settings, waveform selection) from their data blocks.

Result:

• A readable representation of patterns and instruments useful for analysis or conversion.

5. Convert SID output to modern formats

SIDDecode typically offers options to export either audio (WAV/MP3) or converted tracker data (MIDI, MOD, XM). Exporting audio uses the SID register captures from emulation, processed through a SID synthesis model; exporting MIDI/tracker data requires mapping SID note/effect commands to target formats.

Steps to export audio:

1. Choose sample rate and rendering duration (per song).
2. Render each emulated frame into PCM samples, applying SID waveform and filter synthesis.
3. Save as WAV or encode to MP3.

Steps to export MIDI/tracker:

1. Map SID note values and durations to MIDI note-on/note-off events or tracker rows.
2. Convert instrument parameters to approximations (e.g., translate ADSR to envelope settings).
3. Write MIDI or tracker file and test in a player.

6. Troubleshooting common issues

• Incorrect playback speed: Verify PAL vs. NTSC and frame rate settings.
• Garbage/no sound: Check load address and whether the driver initialized correctly.
• Missing instruments or effects: Some SID files use custom playroutines; you may need to reverse-engineer player logic.
• Filter differences: Hardware SID filters vary by chip revision; try different filter models if audio sounds off.

7. Practical example (quick command-line workflow)

1. Inspect header:
   • siddecode inspect mytune.sid
2. Emulate and render WAV:
   • siddecode render –song 1 –duration 180 –rate 44100 mytune.sid mytune.wav
3. Export MIDI (if supported):
   • siddecode export-midi mytune.sid mytune.mid

(Replace commands with your SIDDecode implementation’s syntax.)

8. Tips for chiptune enthusiasts

• Use a precise SID emulator when fidelity matters.
• Compare outputs using different SID models (6581 vs 8580) to hear filter differences.
• When converting to trackers, preserve quirks by exporting pattern data rather than only audio.
• Study instrument ADSR and waveform choices to learn authentic C64 techniques.

Summary

SIDDecode works by parsing the SID header, loading the embedded player and tune data into a virtual C64 memory map, optionally emulating the 6502 and SID chip to capture register activity, decoding internal music structures, and exporting either rendered audio or converted tracker/MIDI data. Following the steps above will let you inspect, play, analyze, and convert SID tunes with accuracy and control.