just a quick question: I noticed that the Reason3 demo supports the KMK, do you know if all features of the protocol are supported, or if anything is missing?
Is any other demo software available in the net which supports the Korg protocol, so that I can double-check the implementation?
I am not aware of any other software at this stage, but i’ll do some research and report back.
I’ve not spent much time with Reason and the microKontrol so I haven’t really familiarized myself with how the two work together. I arrive in London on Sunday so once I settle in i’ll have a chance to play round a bit more, mind you, i’ve got a 27 hour flight ahead of me so i’m sure i’ll find some time in transit.
Im flying thru Brunei rather than Singapore…with no stop overs, so i’ll have some time ; ) buy the way i’ll bring that P&G fader we talked about a while ago, You never know I may drop it off in person.
Hi tatapoum,
thanks for your offer. The SyEx Implementation for Korg native mode can also be found Here:
I still don´t get it and so I got a little question spinning in my head:
How do you want to realize following features:
changing backlight of the LCDs (just different LEDs?)
Drumpads (velocity?!?)
The rest is more or less clear, but I´m cracking my head with this VERY interesting project (as I´m thinking about getting a new main keyboard for controlling).
I’m back on the KMK tip, I’m really hoping that this app can become a reality. Let me explain my stand point.
After some time using this protocol with Logic 7.1 I have come to the conclusion that it is best suited to plug-in control not control of the host app itself. What I propose is some thing like the Mackie C4 (In function alone, not protocol). Thankfully I have just have had the fortune of buying a large number of 20 x 2 CLCD’s for next to nothing (Please don’t hit me with sale requests yet, once I know how many I will need I will post in the Flea Market). What I would like to implement is 1 encoder per 10 LCD charcters (The protocol uses 8 charcters pre encoder) so the 1st and 10th charcter are unused. MIOS will support upto 8 LCD’s per core, so effectivily 2 emulated MicroKontrol’s can be run per core (therefore 16 parameters) . Because the KMK only uses 1 line LCD’s the second line of a 2 line LCD could be used to display the encoders current value (The MicroKontrol displays the encoder value when you move the encoder, then reverts to the encoder name after a user set amonut of time).
That is about all there is to the basic concept., encoders and CLCD’s controlled using the KMK protolcol.
@TK, If you are interested in devloping this project I will provide all LCD’s required to you free of charge (8 for the basic one core project, and an other 16 as a gesture of good will) I am more than happy to work on hardware development and testing…I still don’t know enough about software development to undertake a project like this when example applications using the C wrapper are next to non-existant.
when I think about all the plans I already have for this (and the following) year, I fear that I won’t find the time for just another project.
But I fully aggree, that the KMK protocol is better compared to LC. My own problem is, that I haven’t any benefit from it for myself (yet).
However, writing the driver based on MIOS C shouldn’t be so difficult, maybe somebody else is interested? The C based MIDIbox MM driver already provides all the basics (e.g. SysEx parsing)
Thanks for you reply. I understand you don’t really need such an app yourself as you are using logic 5, I just thought I’d ask. Maybe I’ll just have to brush up on my C code. Is using 8 LCD’s per core going to be diffucult to code in C?
Anyone else interested in my offer? you’ll need to have a bit of a track record of getting some serious MIOS coding done.