Kawai Synthesizers

Alan,

I'm not an expert with the K1-series sysex implementation, but I'm
going to try to help you brainstorm on this problem as best I can. :)
[pulls out K1 sysex implementation chart, which is in the wave list
book (available in the files section for you kids following along at
home)]. 

>   I recently got a Kawai K1M and am currently trying to write an 
> editor program for it.  I use a Music Quest MPU401 interface and Turbo 
> C language with Windows 98.

Awesome! Perhaps some of us can help beta test it when you have a
first release. :)


>   I can send a One_Single_Internal_Voice message with the 86 
> S_parameters from the PC to the K1M, but the K1M will not update any 
> of the old parameter values to a new sound unless I press the 
> Single/I-iE-e button on the actual K1 twice.  
>
>   I've checked the checksum and I believe that it is correct.

Okay. When you send this message, does the K1m's LCD display read
"WRITE COMPLETE" or does it display "WRITE ERROR"? 

>   The MIDI message that I'm sending to the K1 is (hex):
> 
>    F0 40  00  20  00 03 00 00 .. 86 S_params  ... checksum .. F7
> 
> for Int A-1 voice as I just want to get something very elementary
> working first before expanding to more versatile editor program.

So, this is the "ONE SINGLE DATA DUMP" message described in section
5-4 of the K1 Sysex implementation chart, right? It's been a while
since I used a computer editor with my K1m (or the K1rII I replaced it
with, for that matter). I seem to recall needed to change patches or
even re-hit the patch or bank number for a recently dumped patch to
take effect. If you issue a program change message that changes to the
program number you just dumped up, do the changes then take effect
with no manual interaction with the k1m's controls? 

One theory is that the K1m uses a sort of "active patch" buffer, so
that when you patch change, the parameters are loaded into an "active"
area of K1m RAM, as opposed to being read from the patch bank. When
you upload a new patch, you overwrite that slot in the patch bank but
not the "active buffer".


>   Might anyone have any suggestions for making a K1 editor work?

Well, I'm wondering if that "PARAMETER SEND" commands in section 5-3
of the Sysex Implementation chart  might allow you to bypass this
problem, at least for "real time" changes when editing. One advantage
is that these messages have a fixed length of... I think it's ten
bytes, instead of the... 107 total bytes sent for a single data dump.
If somebody were sliding a slider in your editor, the extra bytes
might cause a MIDI clog. I suspect the PARAMETER SEND messages don't
overwrite any slots in bank memory, but instead modify only the active
patch. The SINGLE DATA DUMP messages would be sent as a sort of last
step when the user is satisfied with her patch while editing.


Hope this is helpful. :) It's kind of a a case of the blind leading
the blind, I fear.

Regards,
Ben