Eurorack Interface Specification (EIS)

EIS is a free, open specification for Eurorack hardware. It says what modules, enclosures, bus boards, power supplies, and cables owe each other so that products from different makers fit, power up, and patch together. A rule is a shall only where two products would otherwise fail to work together; everything else is written "EIS recommends". Every requirement has an identifier, a product type, and a machine-readable model behind it.

Get it: lzxindustries.net/eis has the PDF, a design reference for each product type, and the machine-readable models to download, and every clause as a web page with a URL for each requirement. In this repository, start at Scope or, to design a product, at the designer's guide.

Claim it: a product states its product type and any feature in one line, EIS draft, module (VID-REF-IN), and can keep what it publishes in a claim file that eis claim eis-claim.yaml validates.

Change it: open an issue or a pull request at git.lzxindustries.net/lzx/eurorack-specification. CONTRIBUTING.md says what belongs in EIS and how a change is made. A proposal for a new shall names the two products that would stop working together without it.

Document map

Machine-readable models

data/ holds the register and every normative number: requirements.json, the mechanical models, signals.json, video_timings.json, video_75.json, and dc_12.json. A product's claim file follows data/claim.schema.json; the examples are in data/examples/.

The market survey behind Annex F and the catalog rail sections behind Annexes A to D are in the separate eis-reference repository. They are informative and do not size anything EIS requires; a copy of the survey is kept in data/survey/ so that Annex F builds here alone. Third-party documents are not stored here; data/sources.json records each one the specification cites.

Tooling

pip install -e ".[build,test]" installs one command, eis:

Every subcommand is a script under tools/. Figure cards in figures/ follow one house style, tools/card.py. CI builds the PDFs and the site on every push, and a tag v* publishes them at lzxindustries.net/eis (CONTRIBUTING.md).