The microKORG Sound Editor is free software from KORG for transferring patches (presets) back and forth between your computer and your microKORG via MIDI (music instrument digital interface), as well as for editing those patches. Unfortunately, the software is oldschool, clunky, and not at all intuitive.
A few people who have bought my original patches for the MicroKORG have run into trouble loading them into their synths. From my experience, here are a few of the common problems people run into. Hopefully this information will be helpful to others as well.
In order the make sure your MicroKORG is configured to talk to your computer you need to make sure you have the following settings enabled on your MicroKORG.
If you’re still receiving connection errors after following the previous steps, try this. However, after you’re done syncing with the MicroKORG Sound Editor you’ll want to remember to set the MIDI Clock back to either Internal (“
INT“) or Auto (“
AUT“) so that the internal arpeggiator will work without an external timing source.
Typically this is not necessary, but occasionally people have reported that this solves issues where patches don’t transfer properly or revert to init patches.
Don’t forget to set Local back to “On.” Setting Local to “Off” disables the keyboard keys, so you will not hear any sound when pressing on them. After connecting and transferring patches, you will want to remember to turn local back to “On” in order to play your microKORG.
KORG still has the old v1.0 of the software online, but make sure to grab the latest version (2.0), which adds compatibility with the new MicroKORG-S:
Try restarting your computer.
Try checking the MicroKORG Sound Editor preferences and making sure the correct MIDI interface is selected. Then try closing the software and opening it again. Sometimes I’ve had to do this a couple times before it works.
Try a factory reset on your MicroKORG. If you have any custom patches on your synth, be sure to back them up first or else they will be lost.
The Windows and Mac OSX versions of the MicroKORG Sound Editor behave differently and the formats they save are not compatible with one another.
Here’s a great video walkthrough.
The Windows MicroKORG Sound Editor saves patches in a .PRG file format. These should be placed in your
My Documents\KORG\My Library\microKORG folder. This folder should appear on your computer after the first time you run the MicroKORG Sound Editor. The files should show up within the MicroKORG Sound Editor, and all you need to do is double-click on one to load it up, and then use the “Write” function on either the open window or on the MicroKORG itself to save the patch to the desired memory slot.
If you are having trouble getting the MicroKORG Sound Editor to work, or have patches in a .MID format, try using a software called MIDI OX to send the patches.
MIDI OX: http://www.midiox.com/
This installs two programs. For simplicity sake just use the program called “MIDI Bar”
The Mac OSX version of the MicroKORG Sound Editor saves entire banks in its own file format that doesn’t have any extension. Here’s a good overview video: https://youtu.be/4VL08wpLcvw
Another option for transfering individual patches from your computer to your MicroKORG on a Mac is via SysEx, via 3rd-party software. I recommend the free SysEx Librarian. If the patches have a .PRG extension, you’ll need to rename them to .MID. If they’re already .MID then you’re good to go.
SysEx Librarian: https://www.snoize.com/SysExLibrarian/
Check the website for the manufacturer of your MIDI device and see if there are newer drivers available. Nonetheless, some people have complained that some cheap MIDI interfaces don’t work. Feel free to leave a comment to let people know which interfaces have worked or not for you, and I’ll add it to this list.
It’s been reported that doing a factory reset on your microKORG will solve this problem:
1. Shift + 7 key
2. Turn knob 1 to “Prg”
3. Press 7
In other cases, a Factory Reset on the MicroKORG resolved this issue.
If all else fails, you can use a patch decoder to convert the .PRG files into a human-readable format, and then input them manually.