Repository navigation
Community
Open the studio · Browse scores · Join Discussions
Include a title, the code or public project link, BPM/CPS, browser/device requirements, sample dependencies and the license you chose. Explain one thing the score does that someone else can learn from. Use Fork / Remix to preserve provenance instead of editing another person’s project.
Include the sound, creator, source, license, sample rate, channel count and a short example pattern. State whether the sound was recorded, synthesized or edited from a licensed source. Only share material you have the right to redistribute.
Describe the musical workflow, what is awkward today, and one concrete example. A minimal score or short screen recording often explains more than a long feature list. Put reproducible defects in Issues; use Ideas for proposals and tradeoffs.
No hidden network tricks in scores, no unlicensed sample packs, no private credential links. Shared code is executable: keep it understandable and make hardware/external dependencies explicit. Help newcomers start with a small pattern they can hear and change.
XXC / THUGS(red) · Studio · Source · Discussions