Help complete the Penemue Audio map

We are trying to answer practical questions: What exists? Who made it? Who is actively maintaining or porting it? Can you use it on standalone MPC? Is there a practical, legal path to build on the work? Where is more research worthwhile?

Everyone is invited to improve the map. Nothing is published without a Penemue editorial review. Corrections from the original developers, manufacturers and rights holders are particularly welcome. You do not have to open source your own work to be acknowledged here.

Ways to help

A useful submission states who/what, what should change, how you know, and (when relevant) what hardware and firmware was tested. A developer's own source or public project page is better than hearsay. "I made it" is a welcome starting point; we will work together to connect the work to a public attribution.

Suggestion → review → publish

  1. Use Suggest on an entry or Suggest an update in the navigation.
  2. Once the owner sets the GitHub repository, submitting opens a new issue. You must finish the submission in GitHub. You may alternatively propose a data edit in a pull request.
  3. A reviewer checks the supporting links, names, license and technical claims. If a detail cannot be established, the reviewer marks it unverified, asks for more evidence or leaves the suggestion pending.
  4. Only an approved, merged change to the protected main branch can update the public website. Creating an issue, even a highly detailed one, does not change the published catalog.
  5. Reviewed changes should reference the originating issue and source links. Maintainers can add additional credited contributors over time without erasing the project's listed author.

Things not to share

No ROMs or other proprietary firmware, factory samples, cracked software, leaked material, private data, or binaries without redistribution rights. Do not submit unverified authorship as fact. Distinguish inspired-by, modeled recreation, reverse-engineered code, firmware emulation, and official manufacturer software.

Constructive criticism is welcome. This is not a ranking of people's worth or an anti-manufacturer campaign. The fact that a feature can be built again does not erase the skill, investment and maintenance behind a trusted commercial tool.

What does priority mean?

The catalog's High / Medium / Normal open-source opportunity labels are early editorial triage, not crowdsourced demand, engineering estimates, licensing clearance, or promises. The value of a new project depends on feasibility, source availability, ongoing work, licensing, support burden, hardware constraints, and what musicians actually need. A "gap" can be best addressed through purchasing a legitimate product, contacting its developer, improving an existing project or designing a distinct instrument.