Notifications
Clear all
Developers & MIDI 2.0 Specifications
3
Posts
3
Users
1
Reactions
296
Views
Topic starter
I'm working on a simple guitar pedal midi controller, using only Midi 1.0. The prototype is working well. I'm now developing a configuration utility based on Web Midi, which is looking promising but not yet complete. I plan to release the project as open-source, both hardware and software.
To send configuration data to/from the pedal, I'll be using using SysEx messages. The problem is that these require a manufacturer ID which I don't have. While the registration fee is reasonable enough for a commercial developer, it's far too much for a project that will net me nothing.
Is there a less expensive option for open source developers?
Short of that, is there a recommended practice for avoiding collisions?
(If not, I have some thoughts.)
-Matt
This topic was modified 6 months ago by Matt Keveney
Posted : 03/02/2025 4:30 pm
Really cool project—props for going open-source! Getting a SysEx manufacturer ID can be tough for non-commercial work. You could try the development ID (7D) from the MIDI Association—it’s limited but often enough for open projects.
This post was modified 3 weeks ago by The MIDI Association
Posted : 26/06/2025 6:17 am
jon smith reacted
For the SysEx issue, you're right, getting a manufacturer ID can be a bit much for indie or open-source developers. A common workaround is to use the non-commercial ID provided by the MIDI Association (formerly 0x7D). It’s specifically reserved for educational or experimental purposes and might be a good fit if you're not shipping commercial units. Just make sure to document it clearly to avoid confusion or potential conflicts down the line. Good luck with the project!
Posted : 08/07/2025 1:02 am
