Hey everyone,
Hoping you can advise, I've always used the Korg sound library for moving presets (prg files) around but I just bought a set of syx files.
So I know to use a program like Midi Ox http://www.midiox.com/
I have the Korg Instructions http://www.korg.co.uk/downloads/m1/supp ... MIDIOX.pdf
and how to check Midi Filter Exclusive is enabled (using the manual Page 60)
http://www.korg.com/uploads/Support/mic ... 600000.pdf
What I don't know is whether once the syx is sent to the Microkorg, do you then have to use the Microkorg's settings to save the preset to a number (eg. B34) ?
I mean it seems I have to do each one one by one, can I pick and choose where they will go?
Also will they then be exportable to the KORG library as prg files? so i don't have to mix and match my methods?
Microkorg - syx patches midiOX - assigning to a preset?
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Backup all your existing programs before using any sysex, since it could overwrite anything and everything. A sysex can overwrite a single program, all of the programs in the library, or even everything including the global settings. What it actually does depends on the contents, which you won't know unless you know how to read them. Unfortunately, most people who buy sysex files do so because they don't know how to program the synth, much less how to decode sysex files, which is harder.
Hopefully you didn't spend too much money. Most sysex files are garbage patches collected and sold by people who don't know how to program synths either, who don't know a good patch from a hole in the ground, and are basically ripping off anyone who sends them money for things that can usually be downloaded for free. Most of the sysex files won't even work. Once you backup any custom sounds you have, you can see how bad the sysex really are for yourself without any drawbacks besides the time you may be wasting.
If you want the best synth sounds, it's best to learn how to program them for yourself. If you want the best guitar licks, it's best to learn how to play and make them yourself. If you want the best drum beats, it's best to learn how to play them for yourself. There's this whole musician's craft aspect of making music that can't be so easily downloaded or purchased.
Hopefully you didn't spend too much money. Most sysex files are garbage patches collected and sold by people who don't know how to program synths either, who don't know a good patch from a hole in the ground, and are basically ripping off anyone who sends them money for things that can usually be downloaded for free. Most of the sysex files won't even work. Once you backup any custom sounds you have, you can see how bad the sysex really are for yourself without any drawbacks besides the time you may be wasting.
If you want the best synth sounds, it's best to learn how to program them for yourself. If you want the best guitar licks, it's best to learn how to play and make them yourself. If you want the best drum beats, it's best to learn how to play them for yourself. There's this whole musician's craft aspect of making music that can't be so easily downloaded or purchased.
Glad you got a good source. Some sysex will do the memory write as part of the file, while some will only load the patch into the current buffer, which you have to manually save yourself. It appears you got one of the latter ones.
You can use the new patches as motivation to learn how they are designed to produce any sounds that you like. It's not hard to learn the basic flow and elements of a patch. Take a patch that you like then manually go through all the parameters while writing them down as notes. Then create an iniit patch and start recreating it step-by=step to hear how it changes along the way. This is a great way to learn because you know that you like the end result, while you are starting from scratch with an init patch to build up the sound. It's like watching the evolution of something from a crude lifeform to a higher one. If you do that for every new patch you like then you'll learn how they are made that way.
You can use the new patches as motivation to learn how they are designed to produce any sounds that you like. It's not hard to learn the basic flow and elements of a patch. Take a patch that you like then manually go through all the parameters while writing them down as notes. Then create an iniit patch and start recreating it step-by=step to hear how it changes along the way. This is a great way to learn because you know that you like the end result, while you are starting from scratch with an init patch to build up the sound. It's like watching the evolution of something from a crude lifeform to a higher one. If you do that for every new patch you like then you'll learn how they are made that way.
I don't really get into tweaking my microkorg. i'll play around with existing patches and modify them to how i want them to sound, but i dont start from scratch. i really don't like the interface.
I've done a lot of patches with my Korg Poly 61 and Moog little phatty. Once I get my PolySiz repaired I'll be able to work on that more and I'm hoping to get the Moog Sub37.
I find the Microkorg/MS2000 engine has a lot of potential with really expert hands, but i'm not up to that level most of what I get sounds wishy washy or poorly designed.
I've done a lot of patches with my Korg Poly 61 and Moog little phatty. Once I get my PolySiz repaired I'll be able to work on that more and I'm hoping to get the Moog Sub37.
I find the Microkorg/MS2000 engine has a lot of potential with really expert hands, but i'm not up to that level most of what I get sounds wishy washy or poorly designed.