The patch you want is already installed.
Colophon reads every sample library on your machine and puts the whole collection in one catalog — searchable by name, by vendor, or by the words you’d actually use. Rate it, tag it, note the sample delay. From the app, or from inside the assistant you already write with.
One email when there’s something to install. Nothing else.
- Celli LegatoBerlin Strings · Orchestral Tools −58 ms
- Violins I LongSpitfire Chamber Strings −62 ms
- Legato ViolinsAlbion ONE · Spitfire Audio −44 ms
- Violas SustainSynchron Strings · VSL −39 ms
- Felt PianoNoire · Native Instruments −12 ms
You own more than you can remember.
A working library grows one purchase at a time. Kontakt keeps its own browser, SINE keeps another, the Audio Units sit somewhere else entirely. None of them knows anything about the others.
So you reach for the same forty patches. Not because they are the best you own — because they are the ones you can find. The rest is paid for and effectively invisible, and the gap widens with every library you add.
And the knowledge that would fix it lives nowhere durable. Which shorts need how much sample delay, which patch you tried last time and rejected, which articulation actually worked — that is in your head, or buried in one template you are afraid to touch.
One browser per vendor
- Kontakt’s browser, SINE’s, the vendor’s own app
- Nothing searches across them
- Ratings and tags stay in one vendor’s silo
- Offsets live in your head
One catalog
- Every installed library in a single index
- Search all of them at once
- Rate, tag and annotate any patch
- Offsets stored per patch and per articulation
Three things it does today.
-
It reads what you own
Colophon walks the sample libraries installed on your machine — Kontakt, SINE, Audio Units, and manifest-described sources — and catalogues every patch it finds, with the articulations it can identify. It tells you which ones it could not classify rather than pretending it knows.
-
You find things by describing them
Search across every vendor at once, by name or by meaning. “Celli legato”, “felt piano”, “something breathy and slow” — with filters by library, vendor and rating for when you already know exactly what you want.
-
You mark what works
Ratings, tags, notes, collections and saved searches. Sample-delay offsets kept per patch and per articulation. Colophon remembers what you worked out, so the next session starts from it instead of from memory.
All of it is MCP-enabled: the same sixteen operations are tools as well as app screens, so the search, the tags and the offsets are available from inside the assistant you already write with. That is the point of the app being a catalog rather than a destination.
What it does not do yet.
Colophon catalogues and remembers. It does not build your session.
The next milestone is session assembly: taking the patches and offsets you have already curated and producing tracks that play correctly — loaded, routed, delay-compensated. It is designed and specified in detail. It is not built.
Two questions have to be answered before it can be, and neither will be settled by more thinking: which DAW, and whether to write a project file or drive a running session. Both get answered by sitting behind a composer while they work.
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:
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.