Kontakt 6.7.0 is here, adding native M1 support

[Fleer]

Monterey

“ ARM, Monterey and Windows 11 compatibility, new bass amps, bug fixes.

FIXED Kontakt is now native ARM compatible
FIXED Kontakt is now macOS Monterey compatible
FIXED Kontakt is now Windows 11 compatible
CHANGED Minimum supported macOS version is now 10.14
CHANGED Minimum supported Windows version is now Windows 10
IMPROVED Show replace Multi dialog setting is now replaced by a new preference option
ADDED There are now two new amplifiers (Bass Invader and Bass Pro)
FIXED Kontakt VST3 could crash loading instruments with very long host automation names
FIXED Memory was not released correctly in VST3 under certain conditions
FIXED Replika in Ping-Pong mode would not initialise recalled parameters correctly since Kontakt 6.6.1
FIXED Replika in bus effects slots would not follow tempo changes
FIXED Plate Reverb would incorrectly recall in stereo when saved in mono
FIXED Lo-Fi Noise parameter would lose realtime control after modulating SR or Bits params
FIXED 3x2 Filter gain knob would not allow text input
FIXED Modulation in the Phasis effect was behaving incorrectly
FIXED Automation could not be dragged to UI elements beyond 512th instance
FIXED Step modulator can now have all of its 32 steps modulated
FIXED All Convolution factory presets have been updated to zero latency mode
FIXED Number of zones in Expert tab would get cut off when exceeding 9999
FIXED Quick Load view would obscure the virtual keyboard
FIXED Long sample paths would get cut off when hovering the sample name in the mapping and wave editors
FIXED Collection of minor cosmetic GUI fixes
FIXED Collection of various info pane fixes
FIXED Factory scripts using note duration set to Bar now work properly in Kontakt standalone
FIXED Crash when declaring KSP ui_file_selector under certain conditions
FIXED KSP Saving a string array would add an extra white space
FIXED KSP Loading a Windows-formatted (CR/LF) NKA file would result in superfluous empty lines
FIXED "Search for alternative file types" has been set to on by default in the search dialog
CHANGED Event Inputs and Outputs have been renamed to MIDI Inputs and Outputs in VST3 for consistency
IMPROVED KSP Snapshot mode 2 and 3 can now be set, allowing to only store persistent KSP variables
FIXED Factory KSP Script MultiCh Transpose did not retain persistent values
ADDED New Factory KSP scripts "Alternate Pan Modulation", "MIDI Latch 6x", and "Rotate Chords"
KNOWN ISSUE Creator Tools does not connect when Kontakt is running natively on ARM
Creator Tools stays on version 1.4.0, but see Known Issue above.”

[digitalboytn]

FIXED : Scalable GUI

[jameslovesaudio]

Am using Ableton 11.1 I have opened the new Kontakt build VST3 and it displays "Arm" as the processor, so it's running natively now.

Seems to open much faster than the Intel build which is positive, not noticed any major performance gains yet. Don't really run lots of Kontakt instances myself, would be interesting to hear from someone who relies heavily on Kontakt instruments to put it through it's paces.

[grdh20]

Just put the prior vst back if need be for older projects.

[Synth Master Jedi]

I guess it's good that they finally got on board with M1 support, but it would have been nice to have a resizable Gui for the tiny Kontakt UI in 2022.

I had hoped for it, but I wasn't betting on it and it's a good thing that I wasn't holding my breath for it, because I would be dead now.

[SLiC]

Apparently we would have had full resizable HD interfaces for all NI products, a new browser for Massive X and new Amps for GR if they hadn't had to spend all the development time updating for apple chips....

Edit- I take some snarking back- they have added 2 new amps as well

....also added two new bass amps from the GUITAR RIG 6 stable – the tube-powered Bass Pro and the all-new Bass Invader, created with Intelligent Circuit Modeling technology.

[soulata]

is kontakt 6 GUI resizable? i guess not cause then the 3rd party guis have to be too? it is just so small on a big monitor...

This.

[chk071]

Apparently we would have had full resizable HD interfaces for all NI products, a new browser for Massive X and new Amps for GR if they hadn't had to spend all the development time updating for apple chips....

Not sure about that. None of us know how they work internally, and how they distribute their work force.

Would love to blame the Apple folks for everything nice we Windows folks don't get ASAP though.

[CausticPuppy]

So after upgrading to 6.7.0 on my M1 Mac Mini, the "about" page within Kontakt still shows my processor as x64 when run inside Logic. I tried re-registering the plugin in Logic to no avail.

In standalone mode, Kontakt shows "arm64" as expected... but why is Logic is still forcing it to Intel mode? Logic itself is loading in universal mode and other plugins are working with native M1 support.

[nanostream]

So after upgrading to 6.7.0 on my M1 Mac Mini, the "about" page within Kontakt still shows my processor as x64 when run inside Logic. I tried re-registering the plugin in Logic to no avail.

In standalone mode, Kontakt shows "arm64" as expected... but why is Logic is still forcing it to Intel mode? Logic itself is loading in universal mode and other plugins are working with native M1 support.

Have you tried rebooting your Mac already? For some reason that’s sometimes necessary for AU plugins to show up correctly.

[CausticPuppy]

So after upgrading to 6.7.0 on my M1 Mac Mini, the "about" page within Kontakt still shows my processor as x64 when run inside Logic. I tried re-registering the plugin in Logic to no avail.

In standalone mode, Kontakt shows "arm64" as expected... but why is Logic is still forcing it to Intel mode? Logic itself is loading in universal mode and other plugins are working with native M1 support.

Have you tried rebooting your Mac already? For some reason that’s sometimes necessary for AU plugins to show up correctly.

Yep I just got done rebooting and it finally worked, then came back to the thread to update it.

[davidrlevin]

It says they added Bass Invader and Bass Pro, but they've been there since version 6 was released. I'm confused.

[benzene]

I read that as they added those two amps to Kontakt, despite them being previously bundled in Guitar Rig 6.

Ah yes - confirmed - "Additionally, this release expands the sonic capabilities of the platform with the addition of 2 new bass amplifiers from Guitar Rig (Bass Pro & Bass Invader) " (source https://community.native-instruments.co ... 7-0-update)

[benzene]

Giving the update a go now. Unchecked Rosetta, then just had to enable VST3 plugin directory in Live (yes I've only just caught onto this ), then there was Kontakt in all its glory.

Then I noticed none of my NI effects are there (like VC 2A compressor which I use a lot). Thought, oh yeah - duh. Then recalled people saying AU plugs should work natively. Never enabled that before (no idea why, thought it was a Logic thing). A lot more showed up under the AU folder, but Kontakt was much slower to load from there.

I'm not normally adopting things as they get released - realising how much I don't know what I don't know

Not complaining really as Rosetta is fine for what I do.

[beely]

So after upgrading to 6.7.0 on my M1 Mac Mini, the "about" page within Kontakt still shows my processor as x64 when run inside Logic. I tried re-registering the plugin in Logic to no avail.

In standalone mode, Kontakt shows "arm64" as expected... but why is Logic is still forcing it to Intel mode? Logic itself is loading in universal mode and other plugins are working with native M1 support.

There was a note I saw regarding the Liquidsonics M1 plugin versions, that when you install, you should *reboot* immediately, *then* try to load the plugins in Logic. If you don't do this, Logic can still see the older, Intel version of the plugin binary in the cache, and it only picks up the Intel binary and uses that, without recognising there is an M1 binary in there now too it can use.

So what you were seeing was probably related to that, I'd guess...