Kontakt 6.7.0 is here, adding native M1 support

[bmanic]

Hmm.. for some reason the latest Kontakt only added an AUi plugin on my Mac M1 system. Both VST2 and VST3 are missing.

Not a huge problem for me as I use Reaper which is happy with anything really.. but still, was wondering if somebody else ran into this oddity?

[EvilDragon]

VST3 should definitely be there, hmmm...

I just got word that VST2 for ARM is not happening after all, since it's unsupported from Steinberg's side and so on. Any old projects that depend on VST2 should be loaded in Rosetta 2 mode, and any new projects should be started with VST3 or AU.

[benzene]

So, at some point we'll need to migrate Kontakt instances in existing projects to vst3. Maybe not right away, but in good time before Rosetta is removed in a Mac OS update. Not too trivial a task.

There was another thread here "VST2 to VST3 migration strategy" and the word was no need to worry yet, but that was more generally (not considering Rosetta). It does seem one would need a strategy here to think how to approach this existing projects in the medium term (lifetime of Rosetta).

Edit - assuming we do need to do this, I wonder if it could be scripted - eg search and replace across project files for VST2 Kontakt instances and create new project file with a reference to the VST3 instance instead. No idea if feasible.

[zvenx]

I don't have an M1 so I can't say from first hand experience and I use Cubendo almost exclusively, and my vst3 Kontakt seemlessly replaced the vst2 versions in older projects. Does it cross platform too (mac to windows and vice versa).Surprised it doesn't do it for all DAWS.

rsp

[benzene]

Ah ok thanks, I'm on Live, I got plug-in not found for Kontakt on existing projects when opening in native ARM after the update. Works fine in new projects as VST3.

Quite possible I didn't have the right options enabled to scan for VST3 when I tried, so I'll check that. Hopefully it'll just "fall back" to VST3 if VST2 not found.

[zvenx]

Sadly I think another Live user said on the previous page that live doesn't automatically substitute vst3 for vst2 if they have the same plugin ID as Cubendo does.
rsp

[benzene]

Interesting - thanks for confirming. I might have a crack at a migration script then at some point. Likely, I'll quickly realise it's not feasible as soon as I actually take a closer look at project file format!

[zvenx]

It would indeed be 'very unfortunate' if Live and some other DAWS don't do the automatic conversion.. (I say this as a SB and NI 'sycophant' )
rsp

[benzene]

Indeed! I suspect there may be some unhappy users later on when Rosetta goes away if that's the case (seems so). The right solution to this is probably a feature request to those DAWs ...

[Funkybot's Evil Twin]

VST3 should definitely be there, hmmm...

I just got word that VST2 for ARM is not happening after all, since it's unsupported from Steinberg's side and so on. Any old projects that depend on VST2 should be loaded in Rosetta 2 mode, and any new projects should be started with VST3 or AU.

Does that mean Kontakt isn't able to automatically migrate from VST2 to VST3 if the former isn't present? Some plugins allow for this.

Thanks Steiny! Where's the CLAP version of Kontakt?

[benzene]

I suspect the plug-in itself is unaware of how it's opened. There's the VST2 and VST3 versions, independent of each other, and the host is responsible for opening one or the other.

(I hope I'm not talking nonsense though, not a plug-in dev and you did say some plugins can do this, so happy to stand corrected).

[zvenx]

VST3 should definitely be there, hmmm...

I just got word that VST2 for ARM is not happening after all, since it's unsupported from Steinberg's side and so on. Any old projects that depend on VST2 should be loaded in Rosetta 2 mode, and any new projects should be started with VST3 or AU.

Does that mean Kontakt isn't able to automatically migrate from VST2 to VST3 if the former isn't present? Some plugins allow for this.

Thanks Steiny! Where's the CLAP version of Kontakt?

...
Seems it is the DAW not the plugin.. in Cubendo once they have the same plugin ID, they do.
rsp

[zvenx]

I suspect the plug-in itself is unaware of how it's opened. There's the VST2 and VST3 versions, independent of each other, and the host is responsible for opening one or the other.

(I hope I'm not talking nonsense though, not a plug-in dev and you did say some plugins can do this, so happy to stand corrected).

I think this is what it is.
rsp

[nanostream]

So, at some point we'll need to migrate Kontakt instances in existing projects to vst3. Maybe not right away, but in good time before Rosetta is removed in a Mac OS update. Not too trivial a task.

Honest question, how long do you keep working on tracks? Rosetta is here to stay for a few years, that should be more than enough time to finish whatever you’re working on. I’m struggling to see what the problem is exactly?

I mean, you can clone your current setup to an external drive and boot into that if needed, you can just not update for one or two OS versions if push comes to shove, you can print your Kontakt tracks to audio (you should do that anyway). I really don’t get it.

[jamcat]

Some people like to maintain working source files. I know I do.