No sound from Komplete Kontrol - bug or normal?

DunedinDragon

I'm not sure there's anything they can look into. If you have a mk3 keyboard it should just work. My Analog Dream does. You need to look at your installation and configuration. Something's wrong there.

PoorFellow

https://community.native-instruments.com/discussion/comment/137409#Comment_137409

@Jeremy_NI , I have no idea if this is a known issue (this is another issue than originally started thread) , but if it is not then maybe you should look into it !? If issue known already then my apologies for the bother !

McClaneonfire

Thank all of you - I sent a ticket to support. Let's see what they say.

BIF

I have seen this happen, but it's not repetitive in my environment. It's not reproducible and it happens only very rarely. Usually it's because my drivers and MIDI+Audio devices aren't correctly configured. To fix it, I open everything individually, direct it to my output (UAD), and also make sure that the MIDI input is correctly set up. Starting with the innermost tool first, so Kontakt. Then close it and proceed with Komplete Kontrol (or a DAW if I'm having an issue in that area). Then close everything.

Anytime something "regresses" back to an unplayable state, I'll do the same steps above, then close everything and reboot. I can easily go two months between reboots, but sometimes this stuff needs a love tap with the reboot hammer.

Jeremy_NI

There's no similar bug being reported. @McClaneonfire What happens when you open Kontakt in standalone? Do you get sound there?

Vocalpoint

https://community.native-instruments.com/discussion/comment/141569#Comment_141569

I am still blown away about why the OP would want to actually open Kontakt (the actual app UI) within KK in the first place.

When I open any "Kontakt" instruments like Analog Dreams or Session Guitarist or Noire in KK - they all appear in their own "custom" UIs - with no "Kontakt-esk" UI elements appearing whatsover.

Is the OP trying to use Kontakt to access a third party instrument that is NOT NKS or one that loads via the Files area? If so - using Kontakt as a typical standalone VST (and not via KK at all) is a much better option.

VP

McClaneonfire

https://community.native-instruments.com/discussion/comment/141569#Comment_141569

As I wrote before using Kontakt 7 standalone everything works just fine. And yes Sebastian from support answerded my ticket and said:

• too many user requests are coming in these days, so I'll have to wait
• and -> the behaviour is reproducable

It's Kontakt inside Komplete Kontrol standalone.

McClaneonfire

https://community.native-instruments.com/discussion/comment/141577#Comment_141577

Please read what I wrote in this thread: KK is great for having an overview of every instrument. And this is all about Kontakt 7 inside KK standalone. And it is every first time using Kontakt in KK.

For DAW usage I just use the Kontakt plugin, right. That's better, I know...

McClaneonfire

BUT KK has it's benefits with the Komplete Kontrol Keyboards:

for example Play Assist for ARP usage and more ;)

Vocalpoint

@McClaneonfire

"And this is all about Kontakt 7 inside KK standalone. And it is every first time using Kontakt in KK.

Understood - but why?

You do not need to run Kontakt standalone "inside" KK.

Unless - I guess you are trying to use Kontakt (Inside of KK) to playback a third party library that is not NKS compatible or not one that displays a "one tile click" on the main Library view.

But then you would already know to just use Kontakt itself.

The whole point of using KK (at all) to to enable S-Series hardware control of a compatible instrument while avoiding to ever have to show ANY part of the Kontakt UI (or any other app "UI") and just present the primary instrument to the user.

VP

McClaneonfire

Well I just encountered that no sound is produced when clicking the Kontakt Keyboard via mouse.

If this is not meant to be used that way inside KK, why we have the option?

It's no big problem but when you don't have a hardware keyboard or don't want to power it up -> the mouse indeed is useful :)

Trying sounds in KK, loading an instrument, clicking a sound via mouse, next sound / instrument, and so on. Sometimes that's my workflow.

Vocalpoint

@McClaneonfire

"If this is not meant to be used that way inside KK, why we have the option?"

Well - as I mentioned - there are "edge" cases where one "could" need to load Kontakt INTO KK - a good one might be if a user has Kontakt 7 installed AND Kontakt 6 and wants to use a K6 specific instrument within KK.

But like I said - not common and definitely an "edge" case.

That said - just because an "option" is there - does not make it necessary or efficient.

Now - If you do not have a S-Series board - KK is of little value.

I have never attempted to use it like this (as a pseudo auditioner?) - so I am really out to lunch on this issue - except to say - you will always be battling audio routing if you try to open Kontakt "inside" of the Komplete Kontrol UI.

KK is designed for a specific purpose that becomes much clearer if you have the hardware to go with it.

VP

McClaneonfire

You're right, I'm just like well we have the option, so this should work.

Everyone has a different approach on what's efficient.

Also I'm not sure what do you mean by "load Kontakt into KK":

I double click a sound in KK which opens Kontakt, then change the view so I see the software keyboard and here the problem begins. Did you mean another way by "loading Kontakt into KK"?

Vocalpoint

"I double click a sound in KK which opens Kontakt, then change the view so I see the software keyboard and here the problem begins. Did you mean another way by "loading Kontakt into KK"

What exact sound (s) are you double clicking on in KK - which then opens in Kontakt?

Let's get that sorted first. Please be specific.

VP

McClaneonfire

Any preset, no matter what preset I open the first time. After closing Kontakt, then open a preset again, everything is fine.