Page 3 of 3

Re: Korg MicroKontrol - New Python Control Surface Script

Posted: Sat Feb 19, 2011 8:27 pm
by Captain Johnson
Non of LED screens work, buttons don't light up properly! What Am i doing wrong?

Just KMK by wac on the far two screens!! :cry:

Re: Korg MicroKontrol - New Python Control Surface Script

Posted: Sat Feb 19, 2011 8:45 pm
by Captain Johnson
Now the LEDs lights are working but the dials and faders aren't!!!! Sooooo close to exploding!!!! HA!

Re: Korg MicroKontrol - New Python Control Surface Script

Posted: Sun Feb 20, 2011 1:56 pm
by lx71
That is because I am a moron.
I never tested the sliders and encoders. All I needed was the buttons at the time.
I figured if it works for pads/buttons, then the rest will work as well.
But of course it doesn't. There are extensive threads about this issue, that I had read a year ago or so.
I can't believe I forgot about it and actually thought that this was the way to do it.

Not testing before sharing, that's just bad form.
So very sorry for all this.

If you still want the pads to behave like buttons (make them velocity insensitive),
Restore things to the way they were...
Open the wacKMK_A script in a text editor and replace the line
vel = ((midi_bytes[6] >> 6) & 0x01) * midi_bytes[7]
with
vel = ((midi_bytes[6] >> 6) & 0x01) * 127

That way 'vel' does not get passed on from velocity, but is sent out as 127, or 0.
Small consolation.

Re: Korg MicroKontrol - New Python Control Surface Script

Posted: Mon Feb 21, 2011 8:14 pm
by Captain Johnson
.........could you post up the wakmk A changed file name thing I have no script editor and fear such things!!! ......................thanks in advance!

Re: Korg MicroKontrol - New Python Control Surface Script

Posted: Sun Mar 20, 2011 11:59 am
by triss
hey guys.

I've tried both willyc's scripts for Live 8 and 7 and neither of them will make my microKontrol switch to native mode. :?

I've also experimented with the max patch too and that won't switch me to native mode either.

I'm on XP, using a thinkPad laptop.

I'm connected via my USB port and have followed the instructions to the letter.

I've tried doing this from a USB port with the Korg MIDI drivers installed and another where the device is just recognised as a generic USB Device.

Does anyone know why this could be?

I was so excited by this functionality that I nearly burst but now all I feel is sad. :cry:

Re: Korg MicroKontrol - New Python Control Surface Script

Posted: Wed Sep 21, 2011 9:02 am
by Nube2021
Hey guys,

since two days I'am trying to understand why the script of willyc does need two control surfaces to be set in Live's Midi Preferences. I know that Live isn't able to handle sysex messages, but why does the APC40 script work with just one control surface?

I would be very thankful if somebody could explain me this issue or at least send me some useful links where it is explained.


Cheers,
Nube2021

Re: Korg MicroKontrol - New Python Control Surface Script

Posted: Wed Sep 21, 2011 9:41 am
by lx71
I think the APC uses sysex only for 'handshake' purposes.
Also, if it is just sysex buttons, these can be handled through a single script, because you can catch the button events in your script and then, sort of, send them on to Live.

The problem comes with knobs. These need to be connected within Live, rather than in the script, so to speak. Knob events are not caught/handled by the script. Live is told what to do when a knob event occurs. The reason of course being that knob events are very fast.
So there is the reason for the 2nd script. The first one converts sysex to straightforward midi data. The 2nd script tells Live what to do with this straightforward midi data.

I missed this bit of knowledge when I thought I had figured it out. I'm still trying to come up with a solution, but so far, I've got nothing.
I think Hanz, who's done tremendous work in explaining the Framework classes, at one point made some suggestions, but I can't find these anymore.

I hope I've made it clear enough.

Re: Korg MicroKontrol - New Python Control Surface Script

Posted: Wed Sep 21, 2011 4:19 pm
by Captain Johnson
Whoops! posted in wrong hack section!!

Love this micro korg thing though!! just wish the buttons would be more responsive!!

Re: Korg MicroKontrol - New Python Control Surface Script

Posted: Tue Oct 18, 2011 9:58 pm
by willyc
Hi,

A couple of people have contacted me as the previous version of the KMK script no longer appears to work with Live 8.2.5

I have put an updated version of the script on my website at:

http://chippanfire.com/software/wac-kmk-control-script/

I no longer own the Korg Microkontrol, so am unable to say 100% that it works with Live 8.2.5 on windows AND Os X, but feedback from all users who have contacted me has so far suggests the amended version of the script does now work.

The updated scripts also include the fix that makes the pads more responsive.

Cheers
Will

Re: Korg MicroKontrol - New Python Control Surface Script

Posted: Tue Nov 15, 2011 12:00 am
by discoali
The updated python script works fine with the latest Ableton release. Thankyou SOOOOOOOOOO much for your time and effort in making it!

Re: Korg MicroKontrol - New Python Control Surface Script

Posted: Thu Dec 08, 2011 5:47 pm
by Captain Johnson
Does this updated script work with Live 8.2.7???

Re: Korg MicroKontrol - New Python Control Surface Script

Posted: Thu Dec 08, 2011 8:18 pm
by Captain Johnson
Works like a treat!!! :D

Re: Korg MicroKontrol - New Python Control Surface Script

Posted: Wed Aug 29, 2012 5:37 pm
by revoltcrew
Oh man! Got the kmkwac script working for my kontrol49 this morning...!!!
what a treat!
Thanks for all the efforts and info in this thread.

-sunfalls.org

Re: Korg MicroKontrol - New Python Control Surface Script

Posted: Thu Jan 10, 2013 5:24 pm
by Captain Johnson
The keys dont seem to be working with Live 8.3.4 on mac :cry: everything else is working though!

Any chance of an update? (Pretty please)

Re: Korg MicroKontrol - New Python Control Surface Script

Posted: Fri Mar 29, 2013 11:36 am
by dh2k
These scripts were amazing. Any chance someone is porting it to Ableton 9?
If no one is trying to make it hopefully I'll have time to start working on it... Time is precious these days. :/