Finally, after waiting several weeks, Kawai reported back to me that they have no issues with me developing a Kawai K1 emulation. This is great news for me personally as I was still concerned that Kawai could respond in a way that would bring me in trouble. But they did not! 👍 They even sent high quality Kawai logos that I’m allowed to integrate into the plugin, I’m impressed, big thanks to Kawai!
Furthermore, there are now Linux & Mac versions of the VST. For Linux, there are .deb and .rpm packages in both 32 bits and 64 bits. The Mac version requires a 64 bit OS, minimum version is OS X 10.9 Mavericks.
For Mac, an AU version will definitely come. LV2 for Linux, too! Stay tuned.
Special thanks to all donators and to all testers at the KvR forum, a lot of people helped making the plugin available for Linux & Mac by testing on their machines.
You may have read about my Kawai K1m in the development blog. Unfortunately, it is slightly broken and I thought, as there are so many people around still loving these old machines, that some of you could give a hint to repair it.
The issue is that the envelope attacks behave incorrectly. Short attack values are fine, but larger values cause the machine to end in complete silence.
With attack values larger than 36, the attack never finishes, decay is never reached and the sound is audible forever, no matter what the decay/sustain/release values are.
If the attack is even longer, starting with value of 50, the volume starts to decrease. The attack gets stuck so early that the voice keeps being very quiet. With a value of 69, the sound is not audible anymore at all. Below is a picture that shows attack values up to 69, where the voice becomes completely silent.
Anyone knows what is wrong? What I already tried:
I added fresh solder to most ICs, including the CPU, the WaveROM (you might know) and the RAM chips
I measured the connections between the three tone generators and between tone generators and CPU & Wave ROM, they’re all fine
I upgraded the K1m firmware, I ordered a new chip with version 1.5, previously it had 1.3, no change
I contacted Kawai and asked for help, unfortunately they have no idea
I turned it off and on again 😎
My current assumption is that one of the Tone Generator chips is faulty and needs replacement. If there is anyone with another idea, that would be absolutely fantastic! 👍
As you might know, I was always interested to have the presets of the Kawai Phm Pop Synth Module. The PHm uses the same synthesis engine as the K1, the only exception is that the 200 presets cannot be edited. Not even via SysEX, as the PHm neither sends nor recognizes SysEX at all.
The PHm has some presets that never appeared on ROM cards for the K1. Due to a thread on KVR, I asked myself if there is a chance to extract the PHm presets from the device.
I have the device so I opened it and looked for chips that are ROMs. I have not been able to find any chip, so I wondered where the presets are stored. I guessed that they might be part of the Firmware EPROM.
I searched in the net and found the data sheet. This not only gave me the pin layout, but it also revealed something interesting: The EPROM of the PHm is 64kb, while the K1 EPROM is only 32k. This raised chances that it contains the presets.
Dumping the ROM was pretty straightforward, as I did this already for the Wave ROM. The only thing I needed to change is to change the wiring and the code a bit, as the firmware only has 16 address lines.
I dumped the rom and converted it to binary and started to look for the presets. Searching for presets by name didn’t lead to any result so instead, I searched for usual patterns that I already know because of the K1 Single format.
Given that 200 presets need about 20k of space, I quickly found them and began to compare the content against some presets that I know exist on the K1, too (on ROM cards).
Below is a picture. the upper part is the PHm firmware, the lower part is the SysEX of the K1 preset „ID-4 Hold a key“ from ROM card J1-02.
After some analysis, the differences are very minor. Compared to a K1 Single preset, the differences are:
No sysex header (F0h, …, 8 bytes)
No name (10 bytes)
Compared to the K1, they slightly adjusted the presets volumes (byte 11)
Byte at position 22 is missing in a PHm preset => A bit surprising to me, but apparently Source Mute is not supported by the PHm module
No sysex terminator (F7h, one byte)
After I figured out the format, I wrote a small conversion tool that converts all 200 PHm presets to K1 presets. Feel free to download them here! The Zip contains each preset individually and one .syx that contains all 200. The K1v can load it directly.
A small request: If anyone has got a Kawai PH50 firmware, can someone send me a dump? I’d love to extract the Ph50 presets, too!
Note: The PH50 presets are not identical to the PHm, although frequently stated on some websites. Just look at pictures of the device, the preset list is printed on it and it is different from the PHm list.
Just in case you didn’t see it yet, I am so excited about what Jürgen Moßgraber aka MOSS did. He created a whole song with the K1v. Except for some FX, there are only K1v instances in his music track. When listening to it, it instantly reminds me of the 80s. Thank you very much Jürgen for doing this! 👍😊
Nils‘ K1v has been updated to version 1.04, which brings the following improvements & fixes:
[Accuracy] LFO behaviour didn’t completely match hardware behaviour, especially for higher speed values
[IMP] Window size is remembered when the plugin editor is closed and reopened
[FIX] In Solo mode, audio clicks were audible when playing a note while another one was still playing
[FIX] Audio processing could lead to clicks/pops in some hosts. I personally didn’t experience this so feedback & if possible a recording of the issue would help. Thanks 😊
If you want to support me, feel free to donate:
Please visit the product page to download: Nils‘ K1v
Privacy & Cookies Policy
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.