[FIXED BY LOGIC 10.8.1] MIDI note doubling issue with Komplete Kontrol 3.0.3 and Logic Pro 10.8
Answers
-
Judging by LogicProHelp it looks like Logic 10.8 also introduced several other MIDI related bugs including MIDI sync and timeout issues:
so I would guess Apple are working on fixing these and we can expect an update sooner rather than later
3 -
I have this issue now and stumbled across this thread. Certainly part of this is Apple's fault but, in the end it's always Komplete Kontrol that seems to run into these bugs far more often.
I've already been through critical issues that have taken months to fix before with this software and here I am sad again to see the same response. It's like NI team doesn't understand that maybe with issues that completely prevent using the software, more urgency is required. Maybe it warrants dropping features currently in progress. Here it is again, "maybe it's on apple's side, maybe it's on our side, we don't know" for weeks on end. Meanwhile ofter software vendors seem to be working fine.
This just further cements my idea to move away from all things Komplete Kontrol. Won't be buying the new keyboards and will be using the software less over time. It's not their fault that these issues arise but there's no excuse for it taking months to get traction on issues that render the functionality useless.
1 -
While it's true that there are other bugs to be resolved by NI, this is not one of them and this is not a situation where a fix is going to be possible from NI alone, it really does require Apple being on board too as they changed how AU plugins work and probably released that prematurely before the changes were adequately tested or communicated to developers. And it is affecting other venders too (see the Logic Pro threads)
2 -
Yes that's fair and I know NI didn't cause the problem. It's just the response they have that I don't trust anymore. I get the impression they just shoot a few emails over to Apple and hope for the best, waiting for months for something to happen. Rather than establishing a stronger relationship with Apple, and prioritizing the dev time to release workarounds to hold things while Apple works on a fix.
0 -
For what it's worth I'm also having this problem with Arturia Pigments. So, that's unfortunate.
0 -
Interesting - that implies Pigments could potentially be used to send its fantastic sequencer and arp to other plugins (once this is working as intended)
0 -
Yeah, it'll be nice when this feature is working correctly. Unfortunately now I'm stuck in a tricky spot because a bunch of the plugins I use are kinda useless for now.
But yeah the fact this is happening to a bunch of things means the ball's definitely in Apple's court for fixing it.
1 -
I created a new Logic Pro 10.79 project and then a single track with Guitar Rig Pro. Didn’t even record anything. Audio buffer set very conservative at 256. AND YET… massive delay between pressing a key on the MK3 S61 and hearing a response. No delay at all in my Arturia KeyLab MK3 49 controller. 2023 Mac Mini M2 Pro macOS 13 (Ventura). So annoying.
0 -
I am bound by NDA and cannot comment on any communications between companies (e.g. NI and Apple, as an example raised in this thread). Speculation is also unhelpful and incorrect @balboa7 .
There's also nothing to add to the thread that hasn't already been said by myself or others.
As of Logic 10.8, there is a change in the AU format affecting MIDI generative plug-ins.
As noted, this affects all such plug-ins, not just Komplete Kontrol.
The timeline to resolution is uncertain, and not something within my team's control.
4 -
Yes, my type of speculation is not helpful for anyone getting around this issue that's true.
The point is for any other customers new to using NI hardware on MacOS and come across this as their first debilitating issue. I don't blame you or your team personally for this bug. But there is value in pointing out when there is a certain pattern in how companies respond to unexpected and even undeserved issues. Especially because Apple tends to make breaking changes like this often, those working in this ecosystem need to be aware that there are companies that prioritize the ecosystem and those that don't.
The point is simple-- don't get too invested in a company whose constant refrain is "there is no timeline, it's not within our team's control", compared to other companies who do everything they can to make sure their customers can at least use the product.
For those where this is their first issue, just be aware this won't be the first time Apple makes a breaking change and it won't be the first time NI, by all evidence across dozens of similar incidents, sits around and waits on Apple.
As someone who invested too much in NI hardware already, including several Komplete Kontrol keyboards and Komplete Audio, I can only wish I read a similar warning after my first issue with my first keyboard that made it nearly unusable for several months.
1 -
As noted, this affects all such plug-ins, not just Komplete Kontrol.
Actually it doesn't, which is good because it might offer some clues as to how to deal with this. I have tried with a number of plugins that have a MIDI out and the results are not consistent. For example even from NI Komplete Kontrol is affected, but Kontakt also has a MIDI out and yet is not. Arturia Pigments which has a MIDI out is affected but Vengeance Avenger 2 and UVI Falcon 3, both comparable synth/samplers with complex sequencing and MIDI out capabilities, are not.
2 -
I've also seen and experienced direct reports of the products you describe to work... in fact not working as a consequence of the changes introduced.
There has been a lot of work behind the scenes involving multiple companies to diagnose and report the emergence of these issues.
There is also further work needed to resolve the issues, and that work exists outside of the Native Instruments codebase.
I literally cannot comment in any more detail than this other than to again ask @balboa7 not to cast aspersions that anyone is sitting around and waiting, or that we're not doing everything we can. There is nothing we can do other than advise users to remain on, or roll back to Logic 10.7.9.
2 -
That’s also interesting because it suggests there are additional factors at work. Of course that also makes it harder to pin down.
0 -
Anybody have a trustworthy "non-NDA bound" source that has an inkling of what/when on this issue?
Maybe someone working on this talks in their sleep a little too loud?
Inquiring minds want to know!
0 -
I have a better workaround for the MIDI doubling. In the Logic inspector set the MIDI input just to Komplete Kontrol 1, set the MIDI in channel to 1 and change the MIDI out from 'ALL' to anything apart from ALL or 1
3
Categories
- All Categories
- 19 Welcome
- 1.4K Hangout
- 60 NI News
- 729 Tech Talks
- 3.8K Native Access
- 15.7K Komplete
- 1.9K Komplete General
- 4.1K Komplete Kontrol
- 5.5K Kontakt
- 1.5K Reaktor
- 363 Battery 4
- 810 Guitar Rig & FX
- 413 Massive X & Synths
- 1.2K Other Software & Hardware
- 5.4K Maschine
- 6.9K Traktor
- 6.9K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators