Keyboard locked to Live using Native Instruments Komplete
Keyboard locked to Live using Native Instruments Komplete
Whenever i use an Instrument of the NI Komplete Bundle, all the Inputs of the Computer Keyboard still work in Live, not in Massive / FM8 / Kontakt etc. This is quite fine when playing the Sounds of Komplete, but when designing Sounds it's a mess. I can't name Sounds, can't name Buttons (ie the macro controls) etc...
Is that my Fault, NIs Fault or Abletons fault? I want someone guilty! Hang them high!
And, maybe even more important, is there a workaraound?
Is that my Fault, NIs Fault or Abletons fault? I want someone guilty! Hang them high!
And, maybe even more important, is there a workaraound?
Re: Keyboard locked to Live using Native Instruments Komplete
ableton's fault. this was brought up way back during the beta, and i'm surprised it still exists. i just found that the same issue exists with omnisphere.
Re: Keyboard locked to Live using Native Instruments Komplete
Ok, so one of us should do a bug report. Are you familiar with reporting a bug to ableton? As you know of troubles during beta testing i think so. Otherwise i would report it, but when you know of the procedure, i would be glad if you could.
Re: Keyboard locked to Live using Native Instruments Komplete
It's a known issue that first came about with Live 7. It affects any version of Live released since 7.0.2 or so (this includes 6.x updates released after L7 came out), and the fix is well known- put a text file named options.txt in Live's preferences folder and have this as the text in it:
-_EnsureKeyMessagesForPlugins
ew
-_EnsureKeyMessagesForPlugins
ew
Re: Keyboard locked to Live using Native Instruments Komplete
thanks ewistrand, that does the trick.
glad to see ableton is so on top of it. [/sarcasm]
glad to see ableton is so on top of it. [/sarcasm]
Re: Keyboard locked to Live using Native Instruments Komplete
scratch that...issue persists.
Re: Keyboard locked to Live using Native Instruments Komplete
yep same problem -_EnsureKeyMessagesForPlugins does NOT solve the problem.