Kontakt 6.7.0 is here, adding native M1 support

[zvenx]

I produce/record/compose music on two computers, a mac and a pc.. That said I am a mac-head. Have been since 1988.
Every other computer I use and own have been/are macs.

However if by 2022 someone doesn't realise that for compatibility to be able to open older projects, pc's stand a better chance of doing that than macs.. well...(and this is not just for music)

As much as I love macs, I am pretty confident that 10 years from now, my older projects will still open and work on whatever PC I use then, but several changes from apple either software or hardware will not allow me to open these older projects on whatever mac I am using then.

That's not a SB thing, not an NI thing but an Apple thing.

rsp

[Funkybot's Evil Twin]

I produce/record/compose music on two computers, a mac and a pc.. That said I am a mac-head. Have been since 1988.
Every other computer I use and own have been/are macs.

However if by 2022 someone doesn't realise that for compatibility to be able to open older projects, pc's stand a better chance of doing that than macs.. well...(and this is not just for music)

As much as I love macs, I am pretty confident that 10 years from now, my older projects will still open and work on whatever PC I use then, but several changes from apple either software or hardware will not allow me to open these older projects on whatever mac I am using then.

That's not a SB thing, not an NI thing but an Apple thing.

rsp

You're right about Apple breaking compatibility on the one hand, but Steinberg forcing the depreciation of VST2 in favor of VST3 and Native Instruments therefore dropping VST2 support is the topic. And that is very much Steinberg and NI thing. If Steiny wasn't using heavy-handed tactics to push VST3, then NI would have likely included an Apple Silicon VST2 build of Kontakt (sounds like ED is saying one existed at some point) and there would be no project recall issues for Kontakt VST2 projects for years to come.

U-he will continue supporting VST2 for as long as they can but NI opted to jump ship at this point, and while I don't know it for a fact, I think we can all surmise that Steinberg's recent announcements certainly would've played a big part.

And before you get upset about me laying the blame partially on Steinberg's door (after all, I believe they started this)...I didn't dislike them at all up until just recently. I've got Cubase and just wanted it to drop the dongle and improve remote control features. There's a lot to like in it. My anti-Steinberg stance is new and because this VST2 thing is going to inconvenience me and a lot of other people for no good reason.

[jamcat]

I produce/record/compose music on two computers, a mac and a pc.. That said I am a mac-head. Have been since 1988.
Every other computer I use and own have been/are macs.

However if by 2022 someone doesn't realise that for compatibility to be able to open older projects, pc's stand a better chance of doing that than macs.. well...(and this is not just for music)

As much as I love macs, I am pretty confident that 10 years from now, my older projects will still open and work on whatever PC I use then, but several changes from apple either software or hardware will not allow me to open these older projects on whatever mac I am using then.

That's not a SB thing, not an NI thing but an Apple thing.

rsp

I totally disagree there. It's all about the software you're using.

All of my projects from 10+ years ago have been updated several times along the way in order for them to still be working and relevant. And not just updated, but also rebuilt in Studio One when I moved from Cubase. And all of this was exclusively on Windows at the time.

Every time there is a major version update of a plugin, you have to manually swap the old version for the new version, unless you are going to keep old versions installed indefinitely. For example, Kontakt 6 does not load in place of Kontakt 5 or Kontakt 4 or Kontakt 2...

10 years ago, a lot of people were still using 32-bit DAWs. Many 32-bit plugins never made it to 64-bit so they either had to be replaced, or reloaded through bit-bridges when people made the leap to 64-bit.

And lots of plugins have stopped working because of changes to Windows 10. Plugins have needed updates for larger or resizable GUIs along the way. So whether your songs still fully load or are usable has everything to do with whether or not the developers have kept up to date. A lot from 10 years ago are no longer around.

The reality is your projects are NOT going to still be completely working on any current OS after 10 years without regular maintenance.

But the files will still load. Whether you're on Mac or Windows, the .cpr or .song or whatever DAW you are using will still open. Even if you created it 10 years ago on Windows, the current Mac version of that DAW will still open the song.

[teilo]

Wow. So they just gave up on VST2.

NI sucks.

I have years worth of instrumentals, half finished ideas, track starters, etc that I will have to spend significant time rebuilding now when I get a client that picks them to work on. Previously I would just open and go. I had hoped things would be seamless again on my M1 Pro after NI updated. I'm pissed.

Why would anyone have loyalty to a company this blind to it's users needs?

You have to understand that every single VST developer is going to be in the same boat soon. And it's not their fault. Steinberg is entirely to blame for this. Some developers are, understandably, opting to rip off the bandaid now vs. later. And as one of the largest plugin developers in the world, you can bet that NI will be in Steinberg's sights before anyone else.

That's why U-He is investing their time and effort in CLAP. Hopefully it catches on in hosts, but even if it doesn't, it will allow them to continue development against a fixed target and wrap it to whatever the Formats de jour are.

[teilo]

Steinberg's optics on this VST2 move are terrible. It's going to hurt them. But, frankly, I'm glad they are playing hardball. It may well drive CLAP adoption so that we can finally have a superior plugin standard that is not in the hands of a single company.

[EvilDragon]

I am very much in agreement regarding CLAP. I really really hope it succeds!

[zvenx]

[....

And before you get upset about me laying the blame partially on Steinberg's door (after all, I believe they started this)...I didn't dislike them at all up until just recently. I've got Cubase and just wanted it to drop the dongle and improve remote control features. There's a lot to like in it. My anti-Steinberg stance is new and because this VST2 thing is going to inconvenience me and a lot of other people for no good reason.

Or on this one.. blame whatever DAW doesn't allow the seemless vst2 to vst3 migration... ED and I mentioned DAWS that do.. some don't.. is that really SB's fault?
rsp

[zvenx]

...
I totally disagree there. It's all about the software you're using.

...

Well if you can tell me how to open my older projects on mac that use SB's Hypersonic 2, NI's B4 II and a slew of others, I would be happy to hear...
32bit plugins stopped being able to run awhile ago, for some time 32lives allowed you to get around that, no more since I believe Catalina.

They all still open well on PC running Windows 10...


rsp

[EvilDragon]

Or on this one.. blame whatever DAW doesn't allow the seemless vst2 to vst3 migration... ED and I mentioned DAWS that do.. some don't.. is that really SB's fault?
rsp

Nope it's not. But their strongarm tactics are not helpful either. They could've left VST2 alone and open sourced it if they didn't want to support it at all anymore - it was certainly an option. If VST3 were THAT GOOD on its own merits, devs would flock to it rather than being forced to adapt, but it didn't quite work out like that so strongarming it is...

[Funkybot's Evil Twin]

That’s my thinking.

[EvilDragon]

Well if you can tell me how to open my older projects on mac that use SB's Hypersonic 2, NI's B4 II and a slew of others, I would be happy to hear...

If something happens to your Windows machine that you'd have to reauthorize (i.e. motherboard craps out and you gotta replace it), you won't be able to reauthorize B4-II or Pro-53 etc. anymore. Just FYI.

[zvenx]

Interesting, I thought i could do B4 thru NA, knew I couldn't do Pro-53, but I never was a fan of that one and never used it.

Rsp

[jamcat]

Well if you can tell me how to open my older projects on mac that use SB's Hypersonic 2, NI's B4 II and a slew of others, I would be happy to hear...

If something happens to your Windows machine that you'd have to reauthorize (i.e. motherboard craps out and you gotta replace it), you won't be able to reauthorize B4-II or Pro-53 etc. anymore. Just FYI.

Exactly. You can load those old projects either on an old Windows Machine or an old Mac. But they're not going to load on a new machine of either. That was my point.

Realistically, you should have bounced those tracks down when the plugins were abandoned, or swapped them out to keep your project relevant. You can still still do that now, and the replacement plugins will certainly sound better than B4 and Hypersonic. It wouldn't be a loss.

Personally, I'm not going to keep Cubase 5 and AmpliTube 2 around just to load an old song. But I have working songs in Studio One 5 with AmpliTube 5 that started out that way.

[zvenx]

Would you like me to give you a list of plugins not NI authorisation challenged that still work on my pc not my mac? In the industry I work in, if my clients want an older project they want it to sound the same not better, not different. The same.

But indeed my current pc can run all my older projects from probably about 2004, but my mac can't.

Nuendo 4 still works flawlessly on my pc which also runs the next Nuendo.

My mac can't run Cubase before 10 without graphic issues.

Rsp

[fisherKing]

i don't want to be running projects from 2022 in 2032, i want to have moved forward, along with the tech. hard (for me) to understand the point of reopening 10-year old material, when there's new music to be made...