Can a prompt replace Soundtrap?

Set up a local music production workflow around an open-source digital audio workstation, and solve the collaboration half with version control rather than pretending to solve it live.

Install Ardour for audio-led work or LMMS for pattern-led production. Do not build a workstation.

The project that is worth writing is the session-sharing layer. Put each project in a git repository with git-lfs for audio, and write a small tool that: prepares a session for sharing by consolidating every referenced sample into the project folder (the classic failure is a session that opens with missing files on someone else's machine); records the plugin list with versions into a manifest; and refuses to commit if any plugin is not in a shared, agreed list.

Add a bounce-on-commit hook that renders a stereo mixdown to an `exports/` folder named after the commit. That gives every collaborator a listenable version of every revision without opening the project, which is most of what real-time collaboration is actually used for.

For loops, build a tagged local sample library over material you have licensed or recorded: a folder scanner that reads BPM and key from filenames or detects them, writes them into a SQLite index, and offers search by tempo range and key. Store the licence for each pack in the index, so "can I release this?" has an answer.

Do not implement live collaborative editing. Conflict-free concurrent editing of a timeline with audio is a research-grade problem and a half-working version loses takes.