Ableton Forum

There is a long standing issue with Komplete Kontrol not working properly in Ableton Live, where a plugin loaded into Komplete Kontrol has no GUI. It just shows a black square.
This happens in a lot of plugins, so I made a list of plugins I own in which this occurs:

• Algonaut: Atlas
• Cherry Audio: All plugins
• D16: Drumazon 2
• D16: Phoscyon 2
• Devicemeister: Stepic
• Evabeat: Melody Sauce 2
• Gforce: OB-E
• Gforce: OB-X
• Gforce: Oddity 3
• Hexachords: Orb plugins
• Klevgrand: Slammer
• Korg: most plugins
• Kushview: Element
• Loopmasters: LoopCloud
• Moog: Mariana
• Plugin Boutique: Big Kick
• Plugin Boutique: Scaler 2
• PluginGuru: Unify
• reFX: Nexus
• reFX: Vanguard
• Robotic Bean: Portatron
• Sonic Academy: Kick 2
• Spitfire Audio: BBC Symphonic Orchestra
• Spitfire Audio: Labs
• TAL: All Plugins
• Toneworks: Catalyst
• UJAM: All plugins
• UVI: Falcon
• UVI: Workstation
• Waldorf: Streichfett

I hope Ableton and NI can work together to finally fix this annoying bug one day.

PS: I also posted this in the Ableton 12 beta forum and on the NI forum (both official and Komplete Kontrol beta forums)

Did you open a support case with NI?

cids wrote: ↑

Mon Feb 05, 2024 7:54 am

Did you open a support case with NI?

NI are already aware of the issue but they don't seem to care much about it.

…yep…ni traditionally doesnˋt care about anything…like…they‘re always the last when it comes to compatibily updates…so sad…

This is crazy.. I thought this was just my install or something that could somewhat easily be fixed.. It seems more like an Ableton issue if the issue doesn't exist in Bitwig or other DAWs though. The past few times I've talked to NI support they've been quite short, didn't answer my questions, and they apologized for responding so late saying they're short staffed.

…when ni is involved you can bet the solution to a problem is on their side…

Wow,I'm shocked
This is a big issue for everyone,using Komplete Kontrol, including me.
Native Instruments really need to get on this,problem and speak with Ableton tech team get it sorted asap.

Well, this is a showstopper. I was seriously considering an S61 Mk3. But not now.

Yearofthegoat wrote: ↑

Wed Feb 07, 2024 5:22 pm

Well, this is a showstopper. I was seriously considering an S61 Mk3. But not now.

I wouldn't recommend their MK3 keyboards. Not because of the quality of the keyboards (which surely is great), but because the new KK v3 software is a complete nightmare.
Many people who own the older keyboards have reverted back to v2.9.6 because it works so much better. But the new keyboards only work with the v3 software, so basically you would have an amazing keyboard that gets ruined by the buggy software that comes with it.

It's very frustrating. I use several different DAWs (software) so I need a non-tied MIDI keyboard that will work across Ableton, Cubase, FL Studio and Reaper. Currently using a Yamaha NP-V80, which is okay but no aftertouch nor mod wheel.

The wait goes on (unless I bite the bullet and get Korg's Keystage 61).

Also make sure to report to Support.

Yearofthegoat wrote: ↑

Sat Feb 24, 2024 2:29 pm

It's very frustrating. I use several different DAWs (software) so I need a non-tied MIDI keyboard that will work across Ableton, Cubase, FL Studio and Reaper. Currently using a Yamaha NP-V80, which is okay but no aftertouch nor mod wheel.

The wait goes on (unless I bite the bullet and get Korg's Keystage 61).

For what its worth I have a Korg Keystage 61 and it is extremely well integrated with Live and Live's inbuilt instruments and effects and is very easy to map to 3rd party plugins.

I also use it with Logic Pro, and although it doesn't auto-map its built in plugins like Live, it's still easy to map and all transport controls etc work fine (after installing Korg's script for Logic), and the aftertouch works fine.

It also has a lot of adjustability for keyboard velocity, aftertouch and pedal setup.

Pretty happy with it so far and hoping more plugin makers will adapt to Midi 2's potential.

NI finally fixed this bug in the latest Komplete Kontrol 3.2.1.

Reefius wrote: ↑

Wed Apr 10, 2024 4:54 pm

NI finally fixed this bug in the latest Komplete Kontrol 3.2.1.

thx for the heads up

Fixed in 3.2.1...

Was a QT issue.