Kawai K4/K4r controller done!

[kaneel]

Very good question, I have a friend who is interested into downloading this panel!

[markuc]

No answer ? So why do you write this thread ? ” title=”Confused” />

[Anonymous]

Did anyone start a Kawai K1 panel? I haven’t finished my other panels, but I might start this one anyway!

[dimi_dimi]

hey all,

first, big greeting to all members of this community. i think it is an amazing work. i am looking to to this forum for some time (since last major ctrlr revision) and i am very excited to see some new panels.
i will also be interested in Kawai K1M panel, let me know if you have some prototype panel. I am not focused on programming, but at least I would like to test it.

[Binman_UK]

[quote:1l488icv]Did anyone start a Kawai K1 panel? I haven’t finished my other panels, but I might start this one anyway![/quote:1l488icv]

If you could do a panel for the K1 (I’ve got the K1M) it would be MUCH appreciated ” title=”Smile” />.
It’d really improve the usability of the synth.

Cheers.

[ivysun]

whats next? hmmm debating between The Ensoniq SQ2 or the Korg M3r….
both would truly benifit from a good controller surface.

good post

Rc Hobby[/url:3ow5w4j8]|Rc Helicopters Reviews[/url:3ow5w4j8]

[romsom]

A few weeks ago I found a document on creating "panels" with SoundDiver nad tthe examples they used were the K1 and the LXP5 (which I am going to do a panel for in good time ” title=”Razz” /> ). There were some interesting notes about how these devices behave that might be of interest when creating a panel, e.g. that the K1 has no patch cache and you directly modify (i.e. overwrite!) the patches in your K1’s memory.
If anyone is interested I can dig through my internet cache and look for that pdf.
BTW I, too, would really appreciate a K1 panel but I don’t think I will have the time to do one soon, so if anyone still wants to try it out, go ahead! ” title=”Wink” />

EDIT: Sorry for the Spam! ” title=”Wink” />

[ware505]

Is this panel available anywhere?

[atom]

this panel is like a ghost, it’s there but it’s not there ” title=”Smile” />

[layzer]

yup, sorry on this one and a couple others. they need some LUA to function acceptably. as i learn new tricks in LUA
i will get these up ASAP

[betaaffair]

Haha, my bad luck.
I just downloaded Ctrlr and deleted MQ because I saw this thread…
Really must read to the end next time.

Hey Layzer how’s your new tricks?

I imagine the original unacceptable one worked just as well as MQ anyway.

Have  a fine after noon all.

[STK]

Hello Layzer,

why don’t you upload your unfinished panels and have people help with finishing them? Any work done is much appreciated. Look at how many hits this thread has…

[shooking]

I have created two panels, albeit in Beta form, for K1r and K4.

Please find them both currently hanging off my Miniaktools website.

https://sourceforge.net/projects/miniaktools/files/beta1/

Imaginatively entitled MyK1Panel.panel and MyK4Panel.panel

So far I expose all the parameters and one can send values to the synths.
I have not written systex decoders (yet) to load up state to the panel.
Looking at some existing panels for inspiration. I also wrote a C# panel so maybe I do the decode there first then work out this LUA language.

The Tools->Send Snapshot at least updates the Kawai’s with your current values.

I am colour / artistically challenged – but the key point is the sysex and ranges are mostly correct should you want to take this and collaborate on improving things.

Please share credit, that’s all I ask. Oh and let me know of bugs which I will try to fix.

I there is an official place to store these by all means let me know.

Hope you find them useful — my K1r is being used again after years of sulking in corner of studio. It is being triggered by the K4 via ctrlr 🙂

And the K4 — much more fun to sculpt with panel than using the presets.
I will probably update wave names on K4 soon (at the moment I just use inc/dec).

Regards
Steve H

[wikter]

WEll, I’ve been testing the panel.
There’s a very confusing sort of values.
In some cases your K4 editor show values that doesn’t reflect the ones shown in any K4 editor. Sometimes, modulators that have bipolar values (-50, 0, +50) show values from 0 to 100 in your editor.
That’s really annoying, there’s a way to create a list of shown values that have different values when they’re sent by sysex. The formulas are usually simple.
Also, the labels of the groups mess with other value labels.
The important values such as Cutoff, Level, PAN, Velocity>Level… have the same size as other unused values…

MVXSynths
R3 / MOX6 / Electribe2 / Electribe R MkII / Electribe MX / K4R / BCR2000 / XStation61 / XStation25 / Virus Rack / Chameleon / Proteus 2500 / RM1X / KN2600

[wikter]

Well… analyzing more indepht I’ve seen that you’ve used MS/LS messages when almost all of the K4 messages are just lower than 127.
I’ve been correcting some… And it shows clearer.

MVXSynths
R3 / MOX6 / Electribe2 / Electribe R MkII / Electribe MX / K4R / BCR2000 / XStation61 / XStation25 / Virus Rack / Chameleon / Proteus 2500 / RM1X / KN2600

[wikter]

Ready!!! It works fine!

EDIT: Updated!

• This reply was modified 9 years, 5 months ago by wikter.
• This reply was modified 9 years, 5 months ago by wikter.

Attachments:

You must be logged in to view attached files.

MVXSynths
R3 / MOX6 / Electribe2 / Electribe R MkII / Electribe MX / K4R / BCR2000 / XStation61 / XStation25 / Virus Rack / Chameleon / Proteus 2500 / RM1X / KN2600

[shooking]

There’s no problem with MS/LS … this is simply ctrl’s way to represent the number.
If as you say most of the values are 0 … 127 then the MS will never be used.
But infact many of the values (OSC 2, 3, 4) are > 127 so you do need MS/LS.

You are right that I did not modify the values to centre them (ie I left sysex 0 … 100 as is, rather than -50 … 50). The reason for this is simple. I did all this in C++ program and it was tiresome to modify the sysex decode in LUA. Subsequently I found one can use the +bias and -bias method (like I did on the drop-down menus). Still from my perspective the panel was allowing me to control the params so I was happy to do the math in my head.

You are right that for completeness it should be modified.

Thanks for trying the panel.

regards
Steve H

[shooking]

Nice … I see you have made the UI much more compact/logical. Excellent work – like I said I am no artist!

I will test this out at the weekend. Pleasure collaborating with you.

regards
Steve H

[wikter]

Well, the hard work was almost fully done by you, I give a look to the manual and I remembered how terribly it was written. I made a programmer for Synthmaker some years ago, but I used SoundDiver to get the values. The Sysex Spec in the manual is really a mess.
In fact, to match the correct values I had to use my own synthmaker plugin.
Maybe your mistake in the values was that you count the “element number” as part of the data.
Any sysex chain has parameters for:
– manufacturer Id
– device ID
– sub ID’s…
And these Sub Id’s are structured in sections and elements.
In the K4 messages, the last third byte is related to each of the four voice elements, but again in a strange way:
00 – Common + element 1
02 – Element 2
04 – Element 3
06 – Element 6
In fact, the waveform parameter, with almost 256 values may guide to wrong interpretation of these values as there’s no room for higher than 127 in the only byte left to values…
(Some manufacturers use 2 bytes for values)
F0 40 00 00 00 04 00 20 F7
F0 – start
40 – manufacturer
00 – device
(…)
00 – ELEMENT
20 – Value
F7 – END
(that sample message is taken from sysexdb.com and is not an edit message but a recall routine)

I’ll offer this panel here when I finish adding labels for patch.
http://www.mvxsynths.tk

MVXSynths
R3 / MOX6 / Electribe2 / Electribe R MkII / Electribe MX / K4R / BCR2000 / XStation61 / XStation25 / Virus Rack / Chameleon / Proteus 2500 / RM1X / KN2600

[wikter]

Ok, I’ve revisitated the K4R panel and found some errors, problems, etc…
I’ve fixed some of them.

If anyone wants to generate a lua script to translate presets, feel free to modify anything an repost here, thanks.

Enjoy!

The file contains the old and the new version “K4R b”.
Remember to use the overrides to allow full VST automation.

• This reply was modified 8 years, 1 month ago by wikter.

Attachments:

You must be logged in to view attached files.

MVXSynths
R3 / MOX6 / Electribe2 / Electribe R MkII / Electribe MX / K4R / BCR2000 / XStation61 / XStation25 / Virus Rack / Chameleon / Proteus 2500 / RM1X / KN2600

[Author]

Posts