Kawai K1 as VSTi - Nils' K1v is here

[czsynth]

Hi Nils,
contains K1V all presets from PHm module (PH50)?
Thanks for this great VSTi!

[Nils Schneider]

Unfortunately not, I even contacted Kawai to get the presets, but they don't have them anymore Would have loved to get them

[planetearth]

Unfortunately not, I even contacted Kawai to get the presets, but they don't have them anymore Would have loved to get them

I'm not familiar with the PHm, but from what I've just read about it, it seems to use many (if not all) of the same samples -- which would make sense, if it's an offshoot of the K1. If it shares sample data, maybe a call out to a Kawai user group might find someone who still has one and could dump the SYSEX data.

I would imagine some of the people who are looking for Nils' very own K1v (and there are a lot now!) might know someone who still has a PHm, in the same way that some of us who own old hardware that no longer works (or works reliably) look for plug-in versions.

Steve

[czsynth]

Unfortunately not, I even contacted Kawai to get the presets, but they don't have them anymore Would have loved to get them

I'm not familiar with the PHm, but from what I've just read about it, it seems to use many (if not all) of the same samples -- which would make sense, if it's an offshoot of the K1. If it shares sample data, maybe a call out to a Kawai user group might find someone who still has one and could dump the SYSEX data.

I would imagine some of the people who are looking for Nils' very own K1v (and there are a lot now!) might know someone who still has a PHm, in the same way that some of us who own old hardware that no longer works (or works reliably) look for plug-in versions.

Steve

Hi Steve,
I downloaded user manual of PHm (PH50) and it is only preset (ROM) MIDI modul without the possibility of bulk dump (sysex) .

[planetearth]

Unfortunately not, I even contacted Kawai to get the presets, but they don't have them anymore Would have loved to get them

I'm not familiar with the PHm, but from what I've just read about it, it seems to use many (if not all) of the same samples -- which would make sense, if it's an offshoot of the K1. If it shares sample data, maybe a call out to a Kawai user group might find someone who still has one and could dump the SYSEX data.

I would imagine some of the people who are looking for Nils' very own K1v (and there are a lot now!) might know someone who still has a PHm, in the same way that some of us who own old hardware that no longer works (or works reliably) look for plug-in versions.

Steve

Hi Steve,
I downloaded user manual of PHm (PH50) and it is only preset (ROM) MIDI modul without the possibility of bulk dump (sysex) .

Ugh, I should have assumed that. Since it's just a stand-alone, closed ROMpler/sound module, there would be no reason to import or export SYSEX or patches in general. Unfortunately, one site mentioned "MIDI-SYSEX" for "external storage"(http://www.synthark.org/Kawai/PHm.html), and the few sites that had anything about it didn't mention "SYSEX" for it...or any other synth.

Steve

[Nils Schneider]

I have a PHm, its sitting next to me. I tried to send various SysEX messages to it, but no reaction, SysEX seems to be blocked for this device. It doesn't even respond to the generic "Machine ID request".

The WaveROM is identical, so yes, the K1 could use the sounds. It's just a matter of how we could extract them. There are some of the PHm sounds available on cards (For example "Hold a Key", "Water Drama", ...) but unfortunately not all of them. I really missed "Flimmer" so I recreated it for my K1v. But creating all of them would be much manual tweaking work.

[czsynth]

Unfortunately not, I even contacted Kawai to get the presets, but they don't have them anymore Would have loved to get them

I'm not familiar with the PHm, but from what I've just read about it, it seems to use many (if not all) of the same samples -- which would make sense, if it's an offshoot of the K1. If it shares sample data, maybe a call out to a Kawai user group might find someone who still has one and could dump the SYSEX data.

I would imagine some of the people who are looking for Nils' very own K1v (and there are a lot now!) might know someone who still has a PHm, in the same way that some of us who own old hardware that no longer works (or works reliably) look for plug-in versions.

Steve

Hi Steve,
I downloaded user manual of PHm (PH50) and it is only preset (ROM) MIDI modul without the possibility of bulk dump (sysex) .

Ugh, I should have assumed that. Since it's just a stand-alone, closed ROMpler/sound module, there would be no reason to import or export SYSEX or patches in general. Unfortunately, one site mentioned "MIDI-SYSEX" for "external storage"(http://www.synthark.org/Kawai/PHm.html), and the few sites that had anything about it didn't mention "SYSEX" for it...or any other synth.

Steve

Hi, maybe 50 user combinations can be stored via sysex. But in the manual is not any word about this

[fese]

I'm going to store the window size as part of the project data chunk, this allows to remember it per instance and it is portable.

This still doesn't sort out the problem with default GUI size when you first instantiate it in an empty project. Which is why you should have an .ini file somewhere. You can make it so that .ini file is first searched for next to the DLL, but by default it should be created in either ProgramData (for all users) or AppData\Roaming (current user). Then if the user moves the ini file next to the DLL plugin would read from it and write, if possible.

This still makes it portable. It's how it was done for Surge synth, and how u-he synths also operate with their .data folders.

I don’t think an INI file is necessary, if it is stored in the project data, you can easily set it up and save that size as your default preset...

[EvilDragon]

It doesn't solve the case of regular instantiation of the plugin. Also many people don't even know about default preset functionality in their DAWs. Doing both is the right thing to do.

[Tj Shredder]

I have a PHm, its sitting next to me. I tried to send various SysEX messages to it, but no reaction, SysEX seems to be blocked for this device. It doesn't even respond to the generic "Machine ID request".

The WaveROM is identical, so yes, the K1 could use the sounds. It's just a matter of how we could extract them. There are some of the PHm sounds available on cards (For example "Hold a Key", "Water Drama", ...) but unfortunately not all of them. I really missed "Flimmer" so I recreated it for my K1v. But creating all of them would be much manual tweaking work.

The only way to get to those, read out the ROM and try to figure out how the presets are stored. Electronic archeology...
Kawai should pay you for that job though... Maybe they can tell you who made the sounds?

[El°HYM]

Anyone else having problems with the #Joystick? - clicking on it doesnt work as expected, but makes the cursor/dot jump up an inch or two & then its ready to adjust (which works fine) but you cannot really move it around, as it is supposed to work, or works on other applications.

[Nils Schneider]

Saw it in a video but have not been able to reproduce the issue here. In what DAW and does it change if you resize the editor window?

[Nils Schneider]

The only way to get to those, read out the ROM and try to figure out how the presets are stored. Electronic archeology...
Kawai should pay you for that job though... Maybe they can tell you who made the sounds?

Analyzing the data should be straight forward, the question is, which one is the chip holding the presets?

[Aloysius]

The chip on your shoulder?
















































































































It was a joke. Don't hit me.

[El°HYM]

Saw it in a video but have not been able to reproduce the issue here. In what DAW and does it change if you resize the editor window?

First in Renoise (as usual) & Now in Ableton. No resize, yet (in Ableton) expanding the size did the trick; also resizing it smaller again, keeps the expected behavior with the joystick. Will check later, if its the same in Renoise.

*edit*

In Renoise the same happens after resizing, it works normal again. So seems like a mini - bug, when initializing the #plug for the first time & keeping its original size/window.

Should be easy to fix. An excellent little instrument you created here! So, much love & many thanks for this. I always thought that Kawai was a bit unrepresented in the plugin universe... Glad this has changed now!