I wrote a program on the last week... It's convert the MS2000 syx files to R3 syx files...
Some notes:
- the MS2000 has 3 MODSEQ; the R3 just one; so the program always converting the first MS2K MODSEQ data;
- the Timbre2's EQ are not set yet;
- the DWGS names are not agreed yet.
- the patches in the source files are so redundant... I don't have enough time for clearing this redundancy...
Have downloaded and will give them a try as soon as I can! Whatever the results it's great to see you making such an effort to help us R3 folks out -thanks!
squidex wrote:
do you have any advice on software packages required to load/save syx files to the synth?
is a USB/MIDI interface required?
Hi!
The MIDIOX is a good choice to handle the sysx with the R3.
In case of R3 not necessarily a additional USB/MIDI interface. The R3's USB port is a MIDI interface
For example: in MIDIOX you can select the R3 MIDI Input and R3 MIDI output ports to send/receive system exclusive messages after you connect the R3 to the computer via an USB cable.
But if you enough patient, I'll exchange the sysx files on my website to r3l (R3 software editor format) files for the more comfortable handling.
Hi ,
I seem to be having a problem with loading the sysex file .
I am running MIDIOX , i have selected R3 1 MIDI IN and R3 1 MIDI OUT in the MIDI DEVICE menu .
I load a sysex file which appears on the screen as hex .
I then press SEND Sysex.
a box appears with FILE PROGRESS .
Then nothing seems to change, the R3 still has original patches and not the one i was trying to load.
On the R3 i have Sysex - Enabled .
Routing - MIDI+USB
Also i am using just a USB cable .
Help
Eat Static.
(First dabble into Sysex)
(EDIT: I've just used MIDIOX to send patches to my Mopho via USB (R3) and it worked fine .)
Korg R3 EMX1 KP3 miniKP KO1
Moog LP II CP251 MF-101
DSI EVOLVER MOPHO
ROLAND SP404SX JUNO-G
Thanks for your attempt to convert the programs to the R3. However, there are some major problems with the conversion.
For testing, I compared the MS2000 factory preset file from your "R3_MS2000 Factory.syx" sysex version to the one Korg has provided in the R3 library format named "MS2K_FactoryPreset.r3l".
I did this so that I could compare the exact same set of patches to see how they are different.
I noticed some obvious errors in the conversion.
For A1: Stab Saw the sysex was panned to the right so that nothing could be heard on the left channel. This was due to an incorrect virtual patch 2 with EG3 as the source, Pan as the Destination, and an intensity of 20. Because EG3 ADSR was set to 0 64 127 0, this causes the patch to be panned right all the time.
In the Korg version, there is no virtual patch 2.
It appears that the effects have been mapped incorrectly in the sysex. It has a stereo delay on IFX1, but the value is 0, dry, causing no delay.
In the Korg version, there's a chorus on IFX1 with 70:30 wet and a delay on IFX2 that's 88:12 wet, and the effect parameters are set differently, and think correct vs. the sysex. If I set the delay in the sysex version to 88:12, it still didn't have a delay sound until the other parameters were set to match the values used in the Korg version.
Because of the importance of the virtual patches and effects, most patches in the sysex files are not usable. I tried the several other sysex files just to see how many were affected, and unfortunately there were very few that made useful sounds at this point.
You might find it helpful to use the factory patches like I have, to verify that the conversions for at least the MK, MS2K, and MS2KB files end up sounding similar.
For anyone who tries to use MIDI-OX to send these sysex files to the R3, you'll need to modify the sysex default configuration values as follows:
Buffer Sizes: 1024 bytes
Num: 64
Milliseconds between buffers: 60
Checked: Delay after F7: 1200 Milliseconds
Checked: Fill Display Window as Bytes Come In
Basically the sysex should send a 530 byte buffer for each program and then receive the following sysex as a response indicating success:
SYSX: F0 42 30 7D 23 F7
The F0 42 30 7D indicates a SYSEX for the R3, so the operative indication of success is the 23 F7, which is an acknowledgement of DATA LOAD COMPLETED. You may be able to reduce the Delay after F7 to something less than 1200 Milliseconds, but as soon as you get anything except 23 F7 as a response, then a patch will be missing or screwed up because there wasn't enough time given to perform the write operation. I calculated 1200 milliseconds based on how long the R3 editor takes to write all the patches when they are all different than currently loaded. The editor only write patches that are different, so that affects how long the whole write operation takes.
squidex wrote:
do you have any advice on software packages required to load/save syx files to the synth?
is a USB/MIDI interface required?
Hi!
The MIDIOX is a good choice to handle the sysx with the R3.
In case of R3 not necessarily a additional USB/MIDI interface. The R3's USB port is a MIDI interface
For example: in MIDIOX you can select the R3 MIDI Input and R3 MIDI output ports to send/receive system exclusive messages after you connect the R3 to the computer via an USB cable.
But if you enough patient, I'll exchange the sysx files on my website to r3l (R3 software editor format) files for the more comfortable handling.
xmlguy wrote:
For testing, I compared the MS2000 factory preset file from your "R3_MS2000 Factory.syx" sysex version to the one Korg has provided in the R3 library format named "MS2K_FactoryPreset.r3l".
I did this so that I could compare the exact same set of patches to see how they are different.
I noticed some obvious errors in the conversion.
Thank you very much xmlguy!
I'll check once more the matching mechanism in my converter. Anyway my starting point was the midi implementation documents by KORG. For example in the R3's documentation the Knob numbers are wrong So it's need some further testing and fine tuning I agree that!
But thank you once more your helpfully oppinions!
Cheers!
xmlguy wrote:
For testing, I compared the MS2000 factory preset file from your "R3_MS2000 Factory.syx" sysex version to the one Korg has provided in the R3 library format named "MS2K_FactoryPreset.r3l".
I did this so that I could compare the exact same set of patches to see how they are different.
I noticed some obvious errors in the conversion.
Thank you very much xmlguy!
I'll check once more the matching mechanism in my converter. Anyway my starting point was the midi implementation documents by KORG. For example in the R3's documentation the Knob numbers are wrong So it's need some further testing and fine tuning I agree that!
But thank you once more your helpfully oppinions!
Cheers!
I'm glad to help as much as I can on this project! I would like to see all these patches converted too, so you can depend on me to test them and report the results as you work on changes.
Sysex and proprietary file formats suck for trying to see what the data means. XML can be used in such a way that the data describes itself in a manner that's readable by humans and software. At some point in the next year or so, I hope to have some time to do some interesting conversions between the Korg sysex and proprietary formats to XML and back. Now everyone knows the source of my username.
Hi ,
This is a good example of why i like this forum so much .
This has become a very informative thread .
Thanks for all your input .
Thanks to xmlguy for some very clear and concise instructions .
This has made the whole Sysex subject easier to understand .
Eat Static .
A LITTLE WISER EVERYDAY
Korg R3 EMX1 KP3 miniKP KO1
Moog LP II CP251 MF-101
DSI EVOLVER MOPHO
ROLAND SP404SX JUNO-G
I checked the matching code by the midi implementation documents.
So, I'm afraid there is some "bugs" on the R3's MIDI Implementation document (not just with Knobs numbers) and it's the reason why Patch tables are wrong...
I'll take a lot of test on the weekend to discover the right parameter values in R3, and I'll refreshing the sysex files!
I just mad some minor changes... so, the new files still sysex files, but there is more onces udable patches like for now.
Unfortunatelly there is some mistake on the official r3 midi implementation document I discovered the right values, and change my software... The result is more better then I wait! )))
](./images/smilies/eusa_wall.gif "Brick wall"){kind=small}
So it's need some further testing and fine tuning I agree that!