Skip to content

soundings

What the instrument answered, not what the manual says.

Every address of one sound module is read, written to, reset and listened to, one at a time, and only what came back is written down. Nothing is copied from a specification, and a question that was never put is left as a gap rather than filled in.

How to read the archive

Addresses
45,611
Regions
854
Heard
149
Units
1

45,611 addresses answered a read. 41,200 of them held a value at power-on. 671 were listened to, and 149 of those changed the sound.

Address map

Every address the unit answered a read at: what it held at power-on, what values it took, whether its neighbours are separate addresses, and what each reset put back.

Tones / Effects

The bank and program combinations the unit actually moved to, and the insertion effect types it stored — with what each effect's parameters were heard to do.

Observations

What the unit did that no address explains: a read of 256 bytes that stops it answering, a reply that runs on for 29 seconds. Each says how it was found and what it does not establish.

Emulator

A model of the control surface driven by the measurements alone. It answers what was recorded, and says so when a question was never put.

Units

Every finding here belongs to one unit, measured on one path, on the day it was taken. It is not a statement about a model, a firmware revision, or anyone else's unit. Where a run never reached something, the page says so rather than filling the gap in.

Measurements are CC0 1.0 · Not affiliated with, or endorsed by, any instrument manufacturer. Product names identify the equipment measured.