It was slow but steady by the progress bar, but this time ONLY ONE PATCH TRANSFERRED. I changed my SYSEX settings as below and resent a file. I can see in the progress bar the first 7 patches are a little slow and then there is a pause and then WHAMMO – it zips to the end (this is when all the patches are being skipped). Now I begin to think this is a problem with the send speed/buffer sizes in use for transmitting sysex to the K1. Once again, the first 7 patches were sent. I cut about 15 patches out of the file I was experimenting with and resent it. This is a trick of editors that create random patches- they just scramble it up. Thing about sysex files is you can just edit them with HXD or MIDI-OX or even notepad if you know the pattern you are seeking. What I could see is the patches in my synth were the first 7 in the sysex file. You can read plain text (synth patch names, for example) from a sysex file since they are stored as ASCII character values.
I made the change in the sysex file and it worked- almost. My synth was set to receive on channel 1, not 5. Why didn’t 8BITK4.syx work? I could immediately see why this file failed to transmit- it was sending on MIDI channel 5 (04 means the 5th channel since MIDI channels start at 1 vice 0). 10 in hex equals 16, which means patch B1. Byte 8 (10) is the patch number (zero-based). Byte 7 (00) is for sending to internal memory.
The sysex below will do just that.įunction Number 20 (byte 4) is for sending a single or multi patch to internal or external memory. The sub-commands allow you to target individual patches to be stored wherever you like. But wait- on my prophet 12, every PATCH ends with F7. First 10 bytes are the patch name, by the way. These are the byte values for the different synthesizer headings. The sub-command bytes have more functions- see below for complete spec link.sub command 2: patch number (range is 0-63 for single and 64-127 multi).sub command 1: 00- internal patch 02- external (memory card) patch.00 is Group number (appears to be always zero).22 is the function number (these are for functions like send me a patch, bank, or effect.I looked at the file SYSEX header (these values are hexadecimal) using MIDI-OX: I had wrote in another blog that 8BITK4.syx would not transfer. My self and others have reported problems transferring SYSEX files to a K4 so I decided to take a look. If you want to hear a K1 in action, check out my Cyberpunk album at. My first synth was a K1, so I know these well. just going through the preset factory patches and throwing switches.I have a Kawai K4R. Here's an mp3 i made when i first got it. so you can turn some on some off and combine them in different ways for different effect. The bends vary between straight up glitchy stuff to waveform shifting/shuffling etc and lot's of modulation/envelope/filter etc it works like a matrix patch bay. so, it can be disconnected and everything still works just fine. The switches are in a passive controller box that is attached to the rack unit via a ribbon cable. however, the unit functions as normal all the time and can be edited, controlled by midi/sysex etc. they're a few rows of switches and one knob so their position can't be saved with the internal memory of the programmed patch. Wintchil wrote:What does the circuit bends do to the sound? Are they saved with the patch?