Software emulation of hardware instruments adds representational layers that distance the user from the original circuitry

Propellerhead ReBirth (1997) modelled the TB-303’s circuitry algorithmically at around $200 versus $1000+ for a used hardware unit. Nate Harrison notes an irony: ReBirth also emulated the 303’s physical control surface — a representation of a three-dimensional interface on a two-dimensional screen, controlled by third-party hardware (mouse, MIDI controller), to emulate a machine that was itself built to emulate a bass guitar, itself modelled on the contrabass. Each layer of emulation adds interface mediation between performer and sound. This matters for understanding the difference between playing an original 303 and a software emulator: the former has direct physical control-to-circuit coupling; the latter has at least one software translation layer. The distinction recurs in hardware-vs-software debates generally — the question is not only whether emulations sound the same but whether the interface affords the same exploratory manipulation.

Examples

ReBirth showed a virtual 303 panel on screen. A modern analogue: a hardware 303 clone versus a software BassLine plugin — different affordances despite similar sound.

Assessment

Harrison describes multiple representational layers in software emulation of the TB-303. List three layers he identifies. What is the practical consequence of these layers for performance and exploration?