GENIUS-MIDI

GENIUS-MIDI · Build dossier

A pass over the project’s own repository: what is implemented, what is partial, what stayed on paper.

A Python research generator: the scripts emit multi-track MIDI files and a manifest; there is no web product or server, and it runs from the command line.

2 implemented · 2 partial · 1 on roadmap · 1 not implemented

Concept illustration: GENIUS-MIDI. Not a product screenshot

What the code says

  • Two generator versions: v1 at 3,794 lines and v2 at 4,402 Python lines

    Source gen_phi_primes_fib_midisv2.py

  • The v2 script defines 110 top-level functions

    Source gen_phi_primes_fib_midisv2.py

  • Theory names in the v2 code: Narmour 11, Lerdahl 2, Tymoczko 3, Euclidean 3, Bjorklund 1

    Source gen_phi_primes_fib_midisv2.py

  • The numeric core is present: the 1.618 and 0.618 constants, Fibonacci and prime-weighted accents

    Source gen_phi_primes_fib_midisv2.py

  • The only declared dependency is midiutil 1.2.1 or newer

    Source requirements.txt

  • The README is a v5.0 whitepaper: seed determinism, per-layer sub-seeding and a manifest audit of seed, bpm, bars, profile, scale and event counts

    Source README.md

Module state

  1. implemented

    The deterministic MIDI generator

    The v2 script, about 4,402 lines and 110 functions, builds tracks through midiutil from a seed and writes a manifest.

    Source gen_phi_primes_fib_midisv2.py

  2. implemented

    The numeric structures: phi, primes and Fibonacci

    The golden ratio, prime weighting and the Fibonacci sequence drive form, accents and density.

    Source gen_phi_primes_fib_midisv2.py

  3. partial

    The theory stack, only partly in code

    Narmour, Lerdahl, Tymoczko and Euclidean-rhythm names appear in the code, but the Huron ITPRA model is absent (zero mentions), so the stack is only partly realised.

    Source gen_phi_primes_fib_midisv2.py

  4. partial

    Seven tracks and a manifest

    The README promises seven aligned tracks and a manifest per variant, yet the only committed output in version control is a single sample .mid file.

    Source output/01_DRUMS_MAIN.mid

  5. on roadmap

    The v1 to v2 path and the research document

    Two parallel script versions and a research note sit side by side; the generator is not packaged as a library or tool.

    Source midi-gen-research.md

  6. not implemented

    Tests, CI and a web interface

    The generator has no test files or workflow and no interactive web page; it runs only as a script.

    Source .github

How this was checked

  • ITPRA is absent from the source

    A scan of v2 returns zero ITPRA hits against 11 Narmour mentions, so the whitepaper describes more than the code implements.

    Source gen_phi_primes_fib_midisv2.py

  • The code sizes were measured directly

    v1 at 3,794 and v2 at 4,402 lines were counted from the files, with 110 top-level functions in v2.

    Source gen_phi_primes_fib_midis.py

  • There is exactly one dependency

    requirements.txt lists only midiutil 1.2.1 or newer.

    Source requirements.txt

Limits of these claims

  • Not a web product: it runs from Python only and outputs MIDI files; there is no site of its own.
  • The README theory is broader than the code: the ITPRA model is claimed but missing from the source.
  • Only one sample .mid is committed; the full seven-track sets and manifests are not held in the repository.
  • No tests or CI: generation correctness is checked by ear, by hand.
  • Two parallel script versions (v1 and v2) without a shared module risk divergent behaviour.
  • Seed determinism is not musical usefulness: promised measures such as ITPRA are benchmarked by neither code nor listeners.

Why there is no live build

Why there is no live build

There is nothing to publish as a site: this is a Python command-line generator, not a web page; the repository holds neither a built page nor an address.

Back to the project overview ↗