Synth Explorer - Librarian for Prophet 5/10 - Share presets with OB-6 & P-6

Synth Explorer - A modern editor/librarian for OB-6, Prophet-6 & P5/10

Hey everyone, I’ve spent the last year building Synth Explorer, a browser-based editor/librarian for the OB-6, Prophet-6 and Prophet-5/10 Rev4.

This project started from my desire to build a more modern editor for my favorite synths, my OB-6, Prophet-6 and Prophet-10, so it works as a traditional editor librarian, but it also can convert patches between the OB-6, Prophet-6, and Prophet-5/10 Rev4.

I’ve been a UI-focused web developer for the last 15 years, but I’d always kept that work separate from music because I didn’t want to burn myself out creatively. This project was my first time building software for my music hardware, and I spent a lot of time refining the workflow and making the UX feel as immediate and intuitive as the hardware itself.

Any sound imported into the shared library is converted into supported formats for all synths. So you can import sounds from your synths directly, or from a sysex file with multiple presets for any of the supported hardware. Any presets that are imported into the library are automatically converted to be used across all synths.

Obviously the supported synths have different architectures, so it isn’t trying to make them sound literally identical. The goal is to translate the musical intent of the patch as closely as possible given the parameters available on the destination synth.

Everything runs directly through Web MIDI in Chrome, so there’s nothing to install. You can try it for free at:

https://synth-explorer.com

I’m especially curious how something like this fits into other people’s studio workflows. If you own one or more of these synths, I’d be interested to hear how you currently manage presets, move sounds between projects or machines, and where a tool like this would be useful.




Does this support "Import Edit Buffer from Synth" - in other words, when you load a preset and makes changes you want to save that version without overwriting the P10 preset.

That is software with a unique approach.
I believe it is necessary to release a version that can run locally on a PC.

I imagine that processing for elements like effects would likely be mutually exclusive. However, if there were a way to add to or subtract from other destinations, it might open up alternative use cases.

If the software included a feature allowing users to freely configure the destination mappings for conversions between models, it could evolve from a simple translator into a tool that lets users enjoy intentionally modifying the data.

Is it possible to simply load a SYX file, convert it, and transfer it without having the original hardware? I’m simply curious, as it would be interesting to utilize tone data for models I don't actually own.

I believe there is future potential for software that incorporates a system allowing for the flexible configuration of destinations.

Is it possible to adjust the level of conversion used to transform the sound into the same target sound?

Is there anywhere I can find sample audio of the results—converted to similar sounds—that might serve as a reference?
If it produces a similar sound, I think the software is like magic.


« Last Edit: August 15, 2026, 06:54:18 AM by Jpro600k »

Does this support "Import Edit Buffer from Synth" - in other words, when you load a preset and makes changes you want to save that version without overwriting the P10 preset.

Sorry for the late reply, I forgot to turn on notifications for this thread.

Yes, this is something that I took a lot of care to implement. If you make edits to a preset, either in the app UI, or using the hardware knobs, you will see the knobs change color to indicate they have deviated from the saved preset values.

If you right click the knob you can randomize it or reset it at any time to the saved values from that preset.

Any edited hardware program will then give options to save the original hardware program to the library, or save the edited version to library.

For library programs you can save the edits to the current program, or use them to save a new library program.

« Last Edit: August 23, 2026, 09:18:29 AM by ryanpluseverything »

That is software with a unique approach.
I believe it is necessary to release a version that can run locally on a PC.

I imagine that processing for elements like effects would likely be mutually exclusive. However, if there were a way to add to or subtract from other destinations, it might open up alternative use cases.

If the software included a feature allowing users to freely configure the destination mappings for conversions between models, it could evolve from a simple translator into a tool that lets users enjoy intentionally modifying the data.

Is it possible to simply load a SYX file, convert it, and transfer it without having the original hardware? I’m simply curious, as it would be interesting to utilize tone data for models I don't actually own.

I believe there is future potential for software that incorporates a system allowing for the flexible configuration of destinations.

Is it possible to adjust the level of conversion used to transform the sound into the same target sound?

Is there anywhere I can find sample audio of the results—converted to similar sounds—that might serve as a reference?
If it produces a similar sound, I think the software is like magic.

Thank you, this is exactly the kind of perspective I hoped the project would invite. I’ve considered making a local desktop version, but Synth Explorer is very lightweight and works well as a web app without requiring any download or installation. You can try it for free in Chrome, or in Firefox using the Jazz-MIDI extension.

On the SysEx question, yes, you can import a compatible .syx file without owning or connecting the original source synth. Synth Explorer will create converted versions for all supported models directly from that file. You’d just need the target synth connected to audition the result or send it to the hardware.

Right now, Synth Explorer handles the parameter mappings automatically, since the main goal has been to make conversion simple and immediate. Letting users customize those mappings would take it in a more sound-design-oriented direction. I hadn’t considered that approach, but it’s an interesting idea and something I’ll think more about.

There are some audio examples of the conversions in the video on the homepage at synth-explorer.com. That video is taken directly from me using the app. You can also try Synth Explorer for free in Chrome and experiment with the conversions yourself. Because the app works directly with the hardware rather than emulating the synths in software, you’ll need one of the supported synths connected to actually hear the converted sounds.

And yes, “magic” is pretty much the goal. If a converted patch preserves enough of the original sound and character that it immediately feels inspiring on a different synth, that’s what I want the tool to do.

This looks promising.  Looking forward to testing it out this coming week.

Re: Synth Explorer - Librarian for Prophet 5/10 - Share presets with OB-6 & P-6
« Reply #6 on: September 20, 2026, 10:42:47 PM »
This looks promising.  Looking forward to testing it out this coming week.

Thank you, would love to hear your thoughts and happy to answer any questions

Re: Synth Explorer - Librarian for Prophet 5/10 - Share presets with OB-6 & P-6
« Reply #7 on: September 24, 2026, 12:08:43 PM »
Love this editor and UI.  Unfortunately on Mac OSX 12.7.6 there are some bugs like the patch number in the editor does not match what is on the prophet.  I look forward to testing with a newer mac next week and will report back.

Re: Synth Explorer - Librarian for Prophet 5/10 - Share presets with OB-6 & P-6
« Reply #8 on: September 24, 2026, 04:37:51 PM »
Love this editor and UI.  Unfortunately on Mac OSX 12.7.6 there are some bugs like the patch number in the editor does not match what is on the prophet.  I look forward to testing with a newer mac next week and will report back.

Thanks for the kind words, and thanks for flagging this. The patch number mismatch on macOS 12.7.6 is really helpful to know.

I’d love to hear whether you see the same behavior when you test on the newer Mac next week. If it persists, I’d be happy to look into it with you.