Skip to content
RetrogamingDeep Dive July 12, 2026 1 min readViews unavailable

Retro Sound Chips: PSG, FM, Wavetable, and Sample Playback Architectures

Why classic systems sound different: channels, oscillators, envelopes, filters, sample memory, bus timing, and the limits composers turned into instruments.

“Chiptune” covers several unrelated sound architectures. A programmable sound generator may expose square waves, noise, and simple envelopes. FM chips synthesize complex spectra by modulating operators. Wavetable hardware reads short programmable waveforms. Later consoles mix PCM or ADPCM samples from memory. Each design gives composers different constraints and artifacts.

Registers are the instrument interface

Game code writes pitch, volume, envelope, routing, and timer registers. Drivers multiplex musical voices onto limited hardware channels. Fast arpeggios can imply chords; noise becomes percussion; carefully timed volume writes create articulation the chip did not natively provide.

The analog path matters

The digital register model is only part of the sound. Clock rate, resampling, filters, DAC behavior, mixing levels, and analog output stages affect the captured waveform. Two hardware revisions may therefore sound measurably different even when software writes identical values.

Emulation tradeoffs

An emulator can use efficient high-level synthesis or reproduce internal counters and nonlinear behavior more closely. Incorrect clock conversion causes pitch drift; poor resampling aliases high frequencies; ignoring write timing smears effects. Validation uses hardware captures, diagnostic programs, and documented schematics where available.

Preservation should keep original program/audio data and record hardware revision and capture chain. A streamed soundtrack preserves one performance; emulation preserves the interactive instrument that creates it.

Sources: MAME audio system documentation, SID documentation at the C64 Wiki