Patches on the WAVESTATION are similar to HD-1 Programs on the Kronos. However, there are some differences. Most of them can be solved, except for the hard sync option on the WAVESTATION, which is not available in the HD-1. For the oscillators you can choose between wave or wave sequence. These are described elsewhere, so here we focus on some other issues:
The first difference is that the WAVESTATION has an individual pitch envelope for each oscillator, whilst the Kronos has one envelope for both oscillators. There is no workaround for this, but it gives rarely a problem for recreating the WAVESTATION sounds.
Furthermore, the setting for the pitch slope is not quite the same. For the Kronos, changes are made in 1/10, while the WAVESTION can be set with an accuracy of 1/100. The workaround is to use one of the AMS mixer as AMS for the pitch on the Kronos. Use in the AMS mixer type Offset, with Common Key Track 1 (for instance set to 99 and offset set to 50). Modify common key track 1 with bottom low and Low-center set to -75. Adjust the AMS and pitch settings until it is close over the whole range of the keyboard (See for example RAM1 26: Organ 2, the settings for Osc2).
Finally, some of the Kronos Multisamples have the wrong pitch. Below a table of the samples with a wrong pitch, and how they should be corrected (mind that this should be corrected as well if you recreate wave sequences using one of these samples):
The WAVESTATION has two envelopes: AMP and ENV1. ENV1 is most of the time used for the filter. So on the Kronos, use the ENV1 envelope to setup the filter envelope. The envelopes on the WAVESTATION and the Kronos are both ABDSR envelopes, with values ranging from 0-99. However, the lower values on the Kronos are much faster then on the WAVESTATION, so you can't just copy those values. I have determined by ear what the relationship is. Unfortunately it is not linear nor exponential relationship. In graph below you can see the relationship between settings on the WAVESTATION and on the Kronos.
One note about AttackVelMod: a positive setting reduces the attack time when the note is hit with a higher velocity. On the Kronos you will have to use a negative setting instead.
As you can see, I have tried to calculate a trend line. However, more practical is the table below.
I couldn't find any information about the filtertype used in the WAVESTATION. However, it is probably something like a 12 db low pass. So use the 12db lowpass and determine the correct setting by ear.
Furthermore, I get often better results when using a high pass filter in serial with the low pass filter.
The ENHANCER is not present on the KRONOS in the filter. There is an effect however. But I did not manage to get any results close to the WAVESTATION.
A major problem is that many of the Multisamples on the Kronos seem as if they are filtered with a low pass filter already (compared to the same ones on the WAVESTATION. There is no solution for this: what is missing can't be added. With some EQ-ing you can sometimes lift some of the higher frequencies up, but that is all there is. I do hope that KORG is going to correct this in the future.
The velocity settings are different. if the velocity on the WAVESTATION is set to 127, this roughly equals a setting of 70 on the Kronos. So I have used a conversion from 127 to a 70 scale to calculate the value for the Kronos.
The frequency of the LFO needs a lower setting than on the WAVESTATION. I do not know the relationship, but you can do it by ear. In the WAVESTATION you use the modulation wheel and/or the aftertouch to modify the amplitude of the LFO. This is not possible on the Kronos. However, you can do this where you apply the modulation. For instance, if the pitch is modulated by the LFO, then you can set this at the Pitch settings.
As long as two oscillators are used, everything is the same. However I would advice to use Equal Power. When you want to program a 4 vector synthesis Patch, you will need to create two Programs, one for oscillator A and C, and one for oscillator B and D. Now you cannot use the default vector volume, because it only responses to the X-axis. Since it should respond to both the X and the Y axis, I used the following workaround using the filter volume:
First HD-1 program (OSC A and OSC C from the WAVESTATION):
OSC1 corresponds with OSC A on the WAVESTATION,
OSC2 corresponds with OSC C on the WAVESTATION.
Disable Vector Volume.
Enable CC control:
set VJS X mode: XFade and VJS Y mode: Split.
OSC1 AMS Mix, AMS Mixer 1: Type A+B, AMS A: VJS +X: +74, AMS B: AMS Mixer 2: +74
OSC1 AMS Mix, AMS Mixer 2: Type A+B, AMS A: VJS +Y: +49, AMS B: VJS +Y: +49
OSC2 AMS Mix, AMS Mixer 1: Type A+B, AMS A: VJS -X: +74, AMS B: AMS Mixer 2: +74
OSC2 AMS Mix, AMS Mixer 2: Type A+B, AMS A: VJS +Y: +49, AMS B: VJS +Y: +49
Filter 1, Output level: 74, AMS: AMS Mixer 1, Intensity: -99 Filter 2, Output level: 74, AMS: AMS Mixer 1, Intensity: -99
Create the Vector Envelope.
The second HD-1 program. Copy the first HD-1 program, and then modify it:
OSC1 corresponds with OSC B on the WAVESTATION,
OSC2 corresponds with OSC D on the WAVESTATION.
Vector control: set VJS X mode: Split and VJS Y mode: Xfade.
OSC1 AMS Mix, AMS Mixer 1: Type A+B, AMS A: VJS -Y: +74, AMS B: AMS Mixer 2: +74
OSC1 AMS Mix, AMS Mixer 2: Type A+B, AMS A: VJS +X: +49, AMS B: VJS +X: +49
OSC2 AMS Mix, AMS Mixer 1: Type A+B, AMS A: VJS -Y: +74, AMS B: AMS Mixer 2: +74
OSC2 AMS Mix, AMS Mixer 2: Type A+B, AMS A: VJS +X: +49, AMS B: VJS +X: +49