BEATCODEX
Mapping Submission Terms
Last updated: 1 June 2026
1. Introduction
These Mapping Submission Terms govern any drum map, mapping correction, MIDI note information, articulation information, compatibility note, file, comment, feedback, or related material submitted to BeatCodex.
By submitting mapping-related material to BeatCodex, you agree to these Mapping Submission Terms.
If you do not agree with these Mapping Submission Terms, do not submit mapping-related material.
2. Current Project Status
BeatCodex is currently an independent, pre-commercial software project.
No products, subscriptions, paid downloads, paid services, paid support, voluntary support payments, donations, or crowdfunding contributions are currently sold or collected through this website.
BeatCodex is in a pre-launch phase. Mapping coverage, compatibility information, export formats, plugin features, and public map availability may be incomplete, experimental, or subject to change.
3. What Counts as a Mapping Submission
A mapping submission includes any material you provide to BeatCodex related to drum mapping, compatibility, or MIDI workflow, including:
- drum-library mapping data;
- MIDI note names;
- MIDI note numbers;
- kit-piece information;
- articulation information;
- DAW drum-map files;
- mapping corrections;
- compatibility notes;
- library or kit requests;
- screenshots or notes explaining a mapping issue;
- exported text, CSV, XML, or other mapping-related files;
- comments, feedback, or suggestions about BeatCodex maps, taxonomy, or conversion behavior.
4. Permission You Grant to BeatCodex
By submitting mapping-related material, you grant BeatCodex a worldwide, non-exclusive, royalty-free, transferable, sublicensable, perpetual, and irrevocable permission to use, store, review, edit, adapt, normalize, translate, merge, publish, distribute, reproduce, display, make available, and otherwise use your submission.
This permission allows BeatCodex to use your submission for purposes including:
- improving BeatCodex maps;
- correcting mapping errors;
- expanding library compatibility;
- normalizing mappings into the BeatCodex taxonomy;
- generating public-safe map information;
- creating DAW export files;
- improving plugin behavior;
- improving documentation;
- improving website content;
- creating free or paid BeatCodex products, features, maps, packs, services, or commercial offerings in the future.
This permission does not transfer ownership of any third-party product, library, trademark, software, sample, manual, or content that you do not own.
5. No Payment or Compensation
Unless BeatCodex agrees otherwise in a separate written agreement, mapping submissions are voluntary and unpaid.
By submitting mapping-related material, you understand and agree that BeatCodex has no obligation to:
- pay you;
- share revenue with you;
- provide royalties;
- provide a free future license;
- provide a discount;
- provide beta access;
- provide support priority;
- credit you publicly;
- publish your submission;
- keep your submission available;
- use your submission at all.
BeatCodex may choose to credit contributors in some cases, but no credit is guaranteed unless agreed separately in writing.
6. Editing, Normalization, and Combination
BeatCodex may edit, simplify, correct, reorganize, rename, normalize, combine, split, translate, or otherwise adapt mapping submissions.
BeatCodex may merge submitted information with:
- existing BeatCodex maps;
- BeatCodex canonical taxonomy;
- other user submissions;
- manually curated mapping data;
- compatibility research;
- internal validation data;
- future map formats or product features.
You understand that submitted material may be transformed into a different structure, naming convention, taxonomy, or format.
7. Public and Commercial Use
BeatCodex may use submitted mapping-related material in both free and future commercial contexts.
This may include:
- public map pages;
- public compatibility listings;
- free DAW export files;
- beta materials;
- plugin features;
- documentation;
- map packs;
- paid products;
- paid licenses;
- commercial services;
- support tools;
- internal development tools;
- future BeatCodex products or services.
Submitting material does not give you ownership, approval rights, veto rights, revenue share, or control over BeatCodex products, maps, taxonomy, or commercial decisions.
8. Your Responsibilities
You are responsible for what you submit.
By submitting mapping-related material, you confirm that, to the best of your knowledge:
- you have the right to submit the material;
- the submission does not knowingly infringe third-party rights;
- the submission does not contain confidential information that you are not allowed to share;
- the submission does not include third-party audio samples;
- the submission does not include virtual instruments, installers, plugin binaries, or proprietary software;
- the submission does not include copyrighted manuals copied in whole or substantial part;
- the submission does not include license keys, passwords, API keys, or private credentials;
- the submission does not include malicious code, malware, or harmful files;
- the submission is not intentionally false, misleading, abusive, or unlawful.
9. Third-Party Products and Compatibility
BeatCodex is an independent MIDI mapping and remapping project.
Third-party company, product, library, software, DAW, sampler, and trademark names may be referenced in mapping submissions only to identify compatibility, source mappings, target mappings, user-requested drum libraries, or relevant workflows.
BeatCodex is not affiliated with, endorsed by, sponsored by, approved by, or officially connected with Native Instruments, Toontrack, GetGood Drums, XLN Audio, Steven Slate Drums, BFD, UJAM, IK Multimedia, Ableton, Steinberg, PreSonus, Cockos, Image-Line, Apple, Avid, or any other referenced third-party rights holder.
All trademarks, product names, company names, and library names remain the property of their respective owners.
Users must own or lawfully access any third-party drum library, sampler, DAW, plugin, or software referenced in a mapping submission.
10. No Third-Party Audio or Proprietary Content
BeatCodex only needs mapping and compatibility information.
Do not submit:
- audio samples;
- sample-library files;
- virtual instruments;
- plugin installers;
- cracked software;
- license keys;
- passwords;
- private API keys;
- proprietary presets;
- copyrighted manuals copied in whole or substantial part;
- official product artwork;
- logos;
- confidential documents;
- private third-party material;
- anything you do not have the right to share.
BeatCodex may delete or ignore submissions that appear to contain unauthorized, confidential, infringing, unsafe, or unnecessary material.
11. Vendor-Specific Names
Some mapping submissions may include third-party product names, library names, kit names, or articulation names where necessary to identify compatibility.
BeatCodex may use such names only as compatibility references, source labels, target labels, or internal mapping context.
BeatCodex may choose to replace, reduce, hide, rename, normalize, or avoid public display of vendor-specific labels where appropriate.
BeatCodex may use its own canonical taxonomy as the public-facing naming layer.
12. Review and Publication
Submitting material does not guarantee that BeatCodex will review, use, publish, correct, respond to, or retain the submission.
BeatCodex may accept, reject, edit, merge, archive, remove, or ignore any submission at its discretion.
BeatCodex may remove or restrict submitted material if it is inaccurate, outdated, incomplete, legally sensitive, reported by a rights holder, technically unsuitable, or inconsistent with the project.
13. Takedown and Correction Requests
If you believe that a mapping submission, public map entry, compatibility label, product reference, or related material infringes your rights, misuses a trademark, contains inaccurate information, or should be removed for legal reasons, contact hello@beatcodex.com.
Please include enough information to identify the relevant page, content, product name, mapping entry, file, or submission, and explain the reason for the request.
BeatCodex will review good-faith reports and may correct, restrict, or remove content where appropriate.
14. Privacy
Personal data submitted through mapping forms, correction forms, file uploads, email messages, or related communication is handled according to the BeatCodex Privacy Policy.
BeatCodex does not sell personal data.
If you want your personal contact information removed from BeatCodex records, contact hello@beatcodex.com.
BeatCodex may retain non-personal, anonymized, normalized, or aggregated mapping information where appropriate for compatibility, documentation, product development, or legal record-keeping.
15. No Confidential Relationship
Submitting mapping-related material does not create a confidential, fiduciary, employment, partnership, agency, contractor, or joint-venture relationship between you and BeatCodex.
Do not submit confidential ideas, private business information, unreleased third-party content, or material you expect BeatCodex to keep secret unless there is a separate written agreement.
16. Changes to These Terms
BeatCodex may update these Mapping Submission Terms as the project evolves, especially if public maps, beta access, plugin downloads, user accounts, license systems, commercial services, contributor programs, or mapping workflows change.
The updated version will be published on this page with a new “Last updated” date.
17. Contact
For mapping-related questions: maps@beatcodex.com.
For legal, privacy, or takedown requests: hello@beatcodex.com.
For support questions: support@beatcodex.com.
