Colophon

Adding one instrument shouldn’t cost twenty minutes.

Colophon reads the sample libraries you already own and assembles the session from them — patches loaded, tracks routed, sample delay already applied.

One email when there’s something to install. Nothing else.

Strings · legato 31 matches
  1. Celli LegatoBerlin Strings · Orchestral Tools −58 ms
  2. Violins I LongSpitfire Chamber Strings −62 ms
  3. Legato ViolinsAlbion ONE · Spitfire Audio −44 ms
  4. Violas SustainSynchron Strings · VSL −39 ms
  5. Felt PianoNoire · Native Instruments −12 ms
Every patch carries the offset you tuned for it. That number is what makes the track play on the beat.

A template is expensive to build and more expensive to change.

A working template takes days. Every track loaded by hand, every short nudged earlier to cover its sample delay, every output routed. People sell eight-hour courses that teach nothing but this.

Then it ossifies. Not because it stops working — because changing it costs nearly what building it did. So it stops changing. The library you bought in spring never gets wired in. The template drifts away from what you actually own, and the gap widens quietly, until one day the fastest way to use a new library is to not use it.

The usual fix is to buy a template. That solves the first day and not the second: a bought template is built against the vendor’s library set, so it gets adapted by hand after purchase rather than used as shipped.

A template you buy

  • Built against the seller’s libraries
  • Adapted by hand after purchase
  • Static from the day it ships
  • Offsets are somebody else’s

A session Colophon builds

  • Resolved against what’s installed here
  • Built on request, in seconds
  • Rebuilt when your library changes
  • Offsets are the ones you tuned

Three steps, and the third one makes sound.

  1. It reads what you own

    Colophon walks the sample libraries installed on your machine — Spitfire, Orchestral Tools, Native Instruments, VSL — and catalogues every patch it finds, with the articulations it can identify.

  2. You name the patches

    In plain words: three celli legato, a felt piano, the Albion pad. Colophon also speaks MCP, so you can ask for them from inside the assistant you already write with.

  3. It builds the tracks

    Each patch on its own track, routed, with your sample delay applied. If a name is ambiguous or a patch isn’t installed, it stops and tells you which — a half-built session is worse than an error.

No one is using this yet.

Colophon is not released. There is no download, and no one uses it but the person building it.

It runs every day against one real library. That library is the only one it has been proven against, and these are its numbers, not a user count:

15,518Patches 91Libraries 29Vendors

If that sounds like a reason to wait, it is. Leave an address and you’ll hear once, when there’s a signed build worth installing.