 |
 |
||||||||||
|
|
|
Hi. I am trying to use a Korg Midi Kontrol with DNA (version 2). When trying to assign the transport buttons on the Kontroller (Play, stop etc), the buttons only work for as long as they are pressed. So if you release say the Play button on the Kontroller, the film clip stops. When you use the Korg Kontrol Editor, and ensure that the button behaviour is set to 'toggle' and not 'momentary', it doesn't make any difference. Has anyone else had experience of this, and could help in any way? Thanks!
It has to be sending a not off it should be set to momentary then it will "toggle" play when you press it.
Hi. Thanks for your reply. If I set it to momentary, it will only play so long as I'm pressing 'play'. As soon as I release the button, the film stops. Setting it to 'toggle' makes no difference, the same thing happens. It didn't happen with version 1.5. At the moment, I'm only using a trial version (of version 2), would that make a difference?
Hm...what is the MIDI message the transport commands are sending? MMC or control change? I'm assuming control change. (hmm....need to make it so DNA responds to MMC, come to think of it!). When the play button is controlled by a cc message, it will stop when the cc value is 0 and play when the cc value is greater than 0. I've confirmed this behavior. Are you sure the toggle doesn't make a difference? Can you confirm the values sent in the MIDI Spy in Preferences/MIDI?
Hi Peter and thanks for your reply. I have set it to cc, and to toggle. In Midi spy the value is 127 when the play button is pressed, and zero as soon as I release it. Can't work out where I'm going wrong!
Is there a way to make the button behave such that when you press the play button it will send "127" then the next time it will send "0"? That would produce the desired effect.
If not, well, wait till early next week for v 2.01 which will respond to MMC. Are you on mac or PC? I can mail you a pvu to test out if you like
Hi and thanks again. I suppose I thought that the 127 and then 0 would be what would happen when it was set to toggle, but it just isn't happening. It would be great if you could email a pvu to test. I'm using a PC.
drop me an email at pete at liv...etc. and I'll send the link
Thanks for the 2.1 version. I have tried every conceivable permutation of settings using the Korg Nano, both CC and MMC, and no matter how you configure it, as soon as you release the play button (set on toggle or momentary) the play sequence stops. Perhaps the Korg Nano is faulty. Is there anything else you would recommend instead (that won't break the bank)..
if you could download midiox from http://www.midiox.com/ and record some data, then I could possibly make some adjustments.
I'm not sure if you can simply save events to a text file - at worst you could save the screenshot. I will, however, need a way to identify the data as unique events. That is, clear the data display in midi ox, press and release the "Play" button, then save that file and name it "play-cc" or "play-mmc" as appropriate. this way I'll know exactly what data to expect from each button press, and maybe make adjustments as necessary.
Hi. I downloaded midiox, but couldn't understand how to use it. In the meantime I discovered that the Nano Kontrol Editor wasn't recognising the Kontrol hardware, hence the problems. I've now sorted this out, and I've got everything working as it should do, except for the A and B buttons on the crossfade. I can't get them to respond to the Korg at all, even though everything else is fine. I guess I'll have to start saving for the ohm64. Thanks for all your help.
Good to hear. What doesn't work with the A/B - do you mean MIDI learn for those buttons, or do they not function as you would expect.
You must log in to post.
