1/7
Openkit
Distributing sounds without flattening them.
Fifty sounds
- One track
- One isolated sound
- Five export interactions
- Repeat up to fifty times
- Roughly 250 interactions before the kit can move
Seventeen kick tracks in Ableton before a kit can leave the session.
Access at the cost of specificity
- Splice solved access at enormous scale
- Scale created "the Splice sound"
- The sonic equivalent of AI slop
“I'm turned off by someone having the exact same loop.”
Topaz Jones
The ask
“Send me your drum kit.”
- People seek producers through DMs
- The producer's selection carries the value
- The file carries a trust transaction
The kit request, still living in a private message.
Built for how kits actually move
- Export utilitydurable home for kits
- Sound marketplaceproducer-first social network
- Download catalogplayable browser audition
- Attribution labelpersistent fork lineage
bacoDRUMS
What it is
The beatmaker GitHub
- A kit is tied to its maker
- A fork keeps its history
- A profile becomes visible proof of taste
Loosie
@heavybag555baco martinez
Confirmed on OpenkitStated by the maker
Drums
2Sample
1- Main chopsamplesource withheld
The kit keeps its maker
When a kit leaves a session as a folder or a Drive link, the producer disappears. Openkit keeps maker and lineage attached wherever the sounds go.
- A durable home for the kit
- Maker and lineage stay attached
- The value people sought in the DM survives the download
bacoDRUMS
Forks
- +4
