Kontakt 6.7.0 is here, adding native M1 support

[Super Piano Hater 64]

I chose my phrasing carefully. Of the hundred-something companies Apple has acquired, I'm aware of only three that were making music production software before their acquisition: Emagic, Camel Audio, and Redmatica. (I did have to look up what exactly Redmatica's products were. I literally only knew about it because it's on this very short list.)

It's possible that Apple has pursued the acquisition of other plugin developers. For example, I've heard rumors that U-he was approached by one or more big companies in the past, and anyone can imagine that Apple was among these. However, in the seven years since they bought Camel, they don't seem to have gone through with any other such acquisitions.

I think the three of us are in agreement on the reasons why they typically acquire companies: Either for special-purpose tech, or for the domain experts who developed it. Even when they acquire tech with the intent of adding features to Logic, they don't seem likely to get it from plugin developers. That's what makes Camel Audio a special case.

[machinesworking]

I chose my phrasing carefully. Of the hundred-something companies Apple has acquired, I'm aware of only three that were making music production software before their acquisition: Emagic, Camel Audio, and Redmatica. (I did have to look up what exactly Redmatica's products were. I literally only knew about it because it's on this very short list.)

It's possible that Apple has pursued the acquisition of other plugin developers. For example, I've heard rumors that U-he was approached by one or more big companies in the past, and anyone can imagine that Apple was among these. However, in the seven years since they bought Camel, they don't seem to have gone through with any other such acquisitions.

I think the three of us are in agreement on the reasons why they typically acquire companies: Either for special-purpose tech, or for the domain experts who developed it. Even when they acquire tech with the intent of adding features to Logic, they don't seem likely to get it from plugin developers. That's what makes Camel Audio a special case.

I think one thing you're and we're collectively missing here, is the absolute most common way for a company to acquire the tech or means to that tech, is to hire the developer that made that tech, not necessarily the company and the patents etc. It's what Apple initially did with the window and mouse tech that Xerox were essentially letting go to waste, and it continues to this day. Plus and I'm certain of this, there are of course audio developers outside of some need from the Logic team that end up being used by the Logic team. The AI in Logic is a prime example, other DAWs would have had a hard time justifying spending that much on the developers that code that sort of thing, but since Apple can use that in more than one aspect of their business handing AI tech to the Logic team is not a big deal.

But in the bigger picture I think the only disagreement I and probably beely have with you is with this subjective statement:

Their decision to keep Alchemy around (and resurrect the other Camel plugins) was kind of a lucky break (or maybe a condition of the acquisition deal). Don't assume future acquisitions will work the same way... though I don't think we'll see any for a while regardless.

I can't predict the future, but the way they rolled in Redmatica and Camel suggests they want the tech, and the current functioning software that uses that tech. I see no indication they just harvest the body and toss it.

[EvilDragon]

Just a heads up:

Anyone coming into this thread attempting to post about Kontakt crashing on load either as standalone or plugin, it would be really awesome if you could send me the database file before you try and delete it in order to fix the situation (just ZIP it up and put it on Dropbox/OneDrive/whatever, if it's too large to attach to your post)! The file is found at:

Windows:
C:\Users\<your username>\AppData\Local\Native Instruments\Kontakt\Db\kontaktdb2_56

Mac:
/Users/<your home folder>/Library/Application Support/Native Instruments/Kontakt/Db/kontaktdb2_56


Thank you!

[zzz00m]

Haven't updated yet. Still waiting for 6.7.1.

[EvilDragon]

It will happen sooner if somebody sends one such corrupt database file as requested above.

[Atlatnesiti]

I just got my M1 macbook pro and just installed Kontatk. I loaded up a third party library, but it wont' show up in the VST3 version, but does show up in the Audio Unit plugin.

Has anyone run into this?

Same thing was happening in previous live versions as well.
For some bizarre reason, if live or any other host is seeing certain plug-ins in native AU format, it will not load or recognise vst3…
Logic - no pun intended behind this is unclear, but I’m thinking that once Live recognises the same plug-ins in AU and VST3 on Mac, it decides to ditch vst3 in favour of AU
Btw; If you can see and can use AU, is there any reason for wanting to use vst3 as well?
Little bit puzzling

[chroma]

Yes - especially for kontakt which has quite a few sequencers, ableton can take midi out from vst, but not au…

[jancivil]

right, AU does not provide for that. I suppose AU3, still in beta, will.

It's working perfectly here in standalone and plugged into Cubase Pro 11.0.41.
it's not exposing the other three MIDI ports in Cubase, which it can now as VST3 but they couldn't be arsed to I guess. That would be a reason for somebody. I have up to 48 ports in VE Pro, which is a good excuse not to bother with it in Kontakt directly.
None of this matters at this juncture for me. I guess I should at least run it and report, I didn't get to it during beta tho, kind of a fast turnaround afaict.

[jancivil]

I ran a quite new (SonicCouture Geosonics II) and a rather old (Tonehammer) 3rd-party libs.

[EvilDragon]

You can always post your findings on Centercode even if it's not an active beta cycle.