Contributing instruments

The catalogue grows by demand. If you own a library that isn't in the knowledge base yet — or a patch within an existing library that's missing — you can submit it.

What we need

For a whole library, the most useful starting point is:

• Library name and vendor.
• Patch list — names exactly as they appear in your sampler.
• Per patch: articulation names, dynamic layers, mic positions, and (if you know it) the MIDI control rule the library expects — e.g. "UACC on CC 32", "keyswitches at C-1 up", "program changes".
• Vendor's documentation link if there is one.

For a single missing patch in an existing library, just the patch name + articulation list is enough — we'll match it to the rest.

How to submit

For now, contributions are handled via the contact form on dawforge.com. Reach out with the items above and we'll get back to you with a short turnaround. A self-serve submission flow is on the roadmap.

What happens after

• We curate the patch list against the canonical tag families (length, technique, style, pattern, dynamic). See Tags and families.
• We pick the default MIDI output rule from the vendor's documentation, or by sniffing the library directly if needed.
• The library appears in the next catalogue snapshot — typically within a week.

Vendor coverage

DawForge is not affiliated with, endorsed by, or sponsored by any referenced product vendor. Names and product descriptions are used descriptively to make the catalogue searchable. If you are a vendor and want your library curated proactively, the contact form is the right place — we curate without asking, but we're always glad to hear from the people who built the library.

Next

→ Expression maps — concepts