Music production infrastructure for the crews building what comes next
One shared mind
for the whole crew.
Every record adds to what you can make next. Gamut keeps your collective's stems and versions ready to build with, and each artist's lyrics, references and vocabulary in a private songwriting archive. The sound and the thinking behind your work keep growing with you.
Drop a stem on the right. The analysis you are about to watch is the same code used for browser uploads. It runs on your machine. Nothing is uploaded and you do not need an account.
00The short version
A memory that grows with your practice.
A sound should outlive the session that made it. So should a reference, a hard-won lyric or the reason a line belongs. Gamut keeps the collective's sound library ready to reuse and gives each artist a private archive for the writing behind their records.
The lexicon brings your words, images and recurring phrases into view, with their sources and your own judgments alongside them. Shared craft knowledge covers form, rhyme, cadence and hooks. You decide what fits your work. The record of those decisions stays with you.
Connect an agent to the archives and projects you choose. It can recover cited context, keep your corrections tied to a song or style, and organize audio for the next session. Your private archive stays separate from the collective's audio; selected excerpts reach a project only after you review and publish them.
Running today: audio analysis, the collective catalogue and versions, private artist archives, the lexicon, shared craft knowledge and downloadable writing briefs. Connected agents can check lines against recorded rules, save references and scoped feedback, and resume audio imports. You choose their resources and can revoke access. In development: the arrangement map. Designed: the DAW bridge. See what comes next.
- Your collective, your spaceBring the people you already send files to. A collective is the unit here, not a user account, and its vault is private until the collective itself publishes something.
- Your writing, your own archiveEach artist keeps a separate private songwriting archive and lexicon. Joining a collective does not give its members access to either.
- Your next session starts aheadConnect the tools you work with to the memory you have built. Source citations, retained corrections and import receipts help the next agent continue from the work you already trust.
01The moment a file lands
Drop a sound into the browser. Get more than a filename.
Most tools treat a stem as a blob with a filename. This one listens to it. Tempo comes from autocorrelating a spectral-flux onset envelope, key from chroma against Krumhansl-Schmuckler profiles, loudness from a real BS.1770 meter with 4× oversampled true peak.
Browser uploads run analysis in a worker on your machine. The original is stored untouched; measured properties and the listening preview sit alongside it. Direct agent imports preserve the original and supplied metadata; analysis remains a separate step.
And when a filename says 130bpm outright, that wins over detection. On an isolated stem a detector is routinely an octave out, and the person who exported it already knew the answer.
- 01SHA-256content hash
- 02Decodeany format the browser reads
- 03Onsetsspectral flux over an FFT
- 04Tempoautocorrelation of the onset envelope
- 05Keychroma, Krumhansl-Schmuckler
- 06LoudnessBS.1770 integrated + 4× true peak
- 07Peaksthe waveform you scrub
- 08Preview160 kbps stereo, encoded here
02Catalogued, not just stored
instrumentDrumsPercussionBassKeysPadsVocals
characterdarkwarmtightwashed
structureloopone-shotfillriser
Sounds do not get buried in the song they came from.
Every stem lands in one pool the whole collective can search, so a percussion take cut from something two years ago is one filter away from tonight. The song it was made for is just another facet.
Sounds are tagged against a controlled vocabulary of 621 terms, covering instrument, genre, descriptor, structure, vocal, region, gear and effects, rather than whatever anyone typed that day. Guesses read off a filename are marked as guesses, and anyone can reject one.
Then filter the whole pool by tempo range, key, instrument, character or who uploaded it, and pull the original down byte for byte.
It also runs the other way. Drop a reference track on a project and the same analysis gives you its tempo, key and loudness to work against, so a new idea starts from something concrete instead of a blank page.
03Versions, takes and stacks
Hear every version, not one at a time.
A song is rarely one bounce. It is a 130 version and a 132 version, an early take and the one that survived, five or six stems each and half of them shared. Gamut keeps every take inside the same song, so the early one is still there when the last one turns out to be worse.
A take is a stack. Press play and every stem in it starts together on one clock, with per-stem gain, mute and solo, and the bar grid is the take’s own tempo rather than a guess. Switch takes and you keep your place, so you A/B the same bar.
Below is that interface with an example song in it. The takes and the waveforms are drawn, not loaded from anyone’s vault. Everything you can do to it is real: change take, solo a stem, drag across the stack.
Take 03 · the 130 oneThe version everyone knows. Vocal in, pad out.
break, choppeddrums
shakerperc · from another session
subbass
rhodes loopkeys
lead vocalvox
riserfx
04How a track evolves
- 01Member Aopens with a sketch6 stems
- 02Member Banswers round 19 stems
- 03Member Aanswers round 211 stems
- 03bMember Cbranches off round 24 stems
and any of it can be carried into a different song later, edge intact
Every exchange is kept, and any of it can branch.
Someone sends a sketch. You build a bundle out of it and send that back. They answer with a bounce built from yours. Six weeks later a percussion loop from the second exchange turns out to be the best thing anyone made that year, and it goes into a different song entirely.
Each exchange is a round, and a round can answer any earlier round rather than only the last one, so a project branches and both branches stay real. Underneath, every "this came from that" is a claim a person made, never something inferred. That is what makes credit survive the trip.
That is the difference between a folder of bounces and a palette that compounds.
05Out to your DAW
Next: take the session into your DAW.
Nobody finishes a record in a web app. The point of stacking a take here, with its tempo and its levels, is that the arrangement is already a document, so it can be handed to the place you actually work.
That is why the mixer state lives in the shared core rather than inside the website: the web player and the bridge read the same shape. Ableton Live, FL Studio and Logic all count time in bars and load audio off disk, so the same document describes a session in any of them. Nobody should have to switch DAW to work with their own collective.
Where this stands: the mixer and the shared document are built and in daily use. The bridge that opens them as a session is designed and not yet written. This page will keep saying so until it is.
- 01A take in Gamutsix stems, one tempo, gain and mute per lane
- 02A manifestthe mixer state, written down: positions, levels, tempo, originals
- 03A session in your DAWtracks laid out, files local, nothing re-uploaded
06Open by design
vault
- The vaultEverything the collective has, with its metadata and its declared relationships.built
- An agent that reads it“Find me a dark 130 percussion loop we already own.” Reference, never training.designed
- Your own orchestrationBring your stack. The vault is a surface it can query and write back to.designed
- The tools you useAbleton Live, FL Studio, Logic. Whatever the person on the other end opens.designed
A lasting memory for the tools you work with.
A useful assistant should not need your creative history retold every time. Gamut keeps the work you choose to save available for the next session, through the tools you already use.
Choose the archives, vaults and projects an agent can work with. It can recover cited writing context, check a proposed line, retain your feedback and resume an audio import. Selected writing excerpts can become a project reference after you review the exact text. Your private sources stay in your archive.
Where this stands: these operations work through an authorized connection, with saved sources, versions and receipts. Saving feedback does not automatically approve a rule or rebuild your lexicon. Sound similarity search, autonomous production workflows and DAW handoff remain planned.
07Being built
Where this goes next.
The sound library and songwriting memory are running. These are the next connections and tools we want to put around them, with their current stage marked below.
- in progressThe arrangement mapLay individual samples out in bars and export the plan straight into a session.
- designedCreative direction tied to soundKeep a project's shared direction with the samples that demonstrate it, so the next collaborator can hear what you mean.
- designedAgents across the production processBuild longer workflows on connected writing memory and audio imports, with recoverable jobs that carry work between collaborators and their tools.
- designedRegions inside a stemFind the four different patterns baked into one percussion bounce, and save any of them as its own sound.
- designedSearch by earAn embedding per sound, so "more like this one" stops meaning "tagged the same".
- designedListening togetherTwo people, nine time zones apart, hearing the same bounce at the same instant.
08Who is building it
The first collective on it.
Gamut is built by the people using it: five producers across three countries who were losing work in shared folders. Founders is the first collective on the platform and the reason it exists, not the platform itself. Yours would sit beside it, private and separate. Everything below is what these artists release under their own names, and nothing on this page comes out of anyone's vault.
GHOSTMOCHI
Long Beach · experimental / electronicTwo Suns Down.
newFirst release with the collective
Zenstep
Long Beach · ambient / future garageAmbient bass from the Zenstep Lab. Let's dream together.
2026Velvet Rain2025Into The Forest2023Estuary, Modular Grid Records
One shared mind for the whole crew.
gamut n. from gamma ut, the lowest note of the medieval scale, and by extension the whole range of it.
09Bring your people
Labels, crews, duos.
Bring the people you already send files to. Build a sound library you can all draw from, keep each artist's writing in its own private archive, and give the next record more to start from.
Access is by request while we get it right with the first few groups. Tell us who you work with and we will come back to you.
- Your vault is private unless your collective publishes it.
- Originals come back byte for byte.
- Relationships are declared by people, never guessed.
- Your artist archive and lexicon are private to their owner.