Kontakt 6.7.0 is here, adding native M1 support

[machinesworking]

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 going to be very disappointed ten years from now.

32 bit is going away, and likely everything going forward ten years will be SOC and Arm like Apple are doing right now.Who knows what Microsofts emulator will be like? Apple has a lot more experience with them.

But then again you won't be that disappointed. I can open up just fine a song I did on an E6400 Ultra in DP2 on OS 9, in DP11 on an M1 Air, that's two chip versions back. I kept all the samples from the E6400 so they're loaded into Kontakt now.

Truth is nothing is bullet proof in the software world unless you do some things to prevent loss in case say NI discontinue the B4 and you can't instal it on your new computer. having a printed audio version and the MIDI track etc. to replicate it as well as you can is the way to go.

[jancivil]

"projects from the mid-90s" - JFC

[bmanic]

i have mixes of old projects, if i need a reference. and if i open an old project and no longer have some synth plugins, i find new sounds, and endeavor to make things better. and life goes on...

Sure, that strategy works fine if you are the sole owner of the copyright, composition, production etc.

.. but that's not how it works with major record labels or television networks (for instance if you are the composer for some local TV series that gets renewed 10 years later and they want to make a surround mix).

As I tried to allude to earlier, I understand your case as it seems a "singular" type of deal. You is just you.. so it's easy to deal with it. But that is not always the case as you can well imagine.

i've worked with major record companies, famous artists (and less famous ones); done some film work (no tv scoring tho). anyway, i get it. but please... keep repeating the same thing as often as possible.

EDIT: ok, am gonna take a break from stupid posting. plenty of others here to keep that going (which makes THIS my last stupid post).

at least for a while...

... so why then claim otherwise?

You know you could have lead with the above info right away.

[bmanic]

Truth is nothing is bullet proof in the software world unless you do some things to prevent loss in case say NI discontinue the B4 and you can't instal it on your new computer. having a printed audio version and the MIDI track etc. to replicate it as well as you can is the way to go.

.. or just keep the old computer around that has B4 installed on it and the one that has the track you worked on. That's what we've been doing at the studio. I suspect this is the norm (.. as is printing everything to audio and midi of course).

[zvenx]

(I still have working Power Tower Pro with OS 9 on it that I can open my Opcode Studio Vision Projects if I really need to, sometimes I have actually had to to export midi into Cubendo etc.)
rsp

[fisherKing]

am thinking that bmanic & i could give it a rest, and let the thread get back on track....

[machinesworking]

Truth is nothing is bullet proof in the software world unless you do some things to prevent loss in case say NI discontinue the B4 and you can't instal it on your new computer. having a printed audio version and the MIDI track etc. to replicate it as well as you can is the way to go.

.. or just keep the old computer around that has B4 installed on it and the one that has the track you worked on. That's what we've been doing at the studio. I suspect this is the norm (.. as is printing everything to audio and midi of course).

Yeah that was my point, because B4 or Alchemy etc. cannot be recovered if anything happens to the drive they reside on, it's best to have printed audio, and of of course the MIDI etc. Windows is better in terms of lasting longer but only by a small margin in the bigger picture, nothing is permanent in the software world, as we're seeing with M1, 32 bit support going away, NI discontinuing authorization for super old plug ins, Camel being bought, freeware lagging in support etc.

[zvenx]

Alchemy's copy protection is a key file, unless one didn't back it up, that one should be fine on windows for years to come.

Rsp

[Atlatnesiti]

Love it.
Hopefully first of all NI to migrate to m1

[Atlatnesiti]

Alchemy's copy protection is a key file, unless one didn't back it up, that one should be fine on windows for years to come.
That’s right…
Alchemy is now Apple own
Hopefully Apple will aquire more music app developers
At least then we will have some updates happening

[dusted william]

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?

[EvilDragon]

That sounds like VST3 version wasn't properly updated. Click the KONTAKT logo in top left, which version does it say?

[Super Piano Hater 64]

Hopefully Apple will aquire more music app developers
At least then we will have some updates happening

Apple has gobbled up a lot of companies, but very few have been in the music production business. Camel Audio was a special case. Apple wanted to use their spectral resynthesis tech as the basis of new features in Logic. When they do want new plugins, they typically develop them in-house, like they did with Retro Synth and all those EQs and reverbs. 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.

[machinesworking]

Hopefully Apple will aquire more music app developers
At least then we will have some updates happening

Apple has gobbled up a lot of companies, but very few have been in the music production business. Camel Audio was a special case. Apple wanted to use their spectral resynthesis tech as the basis of new features in Logic. When they do want new plugins, they typically develop them in-house, like they did with Retro Synth and all those EQs and reverbs. 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.

Hmm? you must not know about Redmatica then? They gobbled them up as well, and their tech went into Autosampler in Logic. In fact every possible audio related tech Apple owns has been used in Logic, the AI was surprising to me, but it's there. I think at this point they really don't need anymore outside sources, barring something like buying Melodyne or Sononym etc.

[beely]

Apple has gobbled up a lot of companies, but very few have been in the music production business. Camel Audio was a special case. Apple wanted to use their spectral resynthesis tech as the basis of new features in Logic. When they do want new plugins, they typically develop them in-house, like they did with Retro Synth and all those EQs and reverbs.

They also bought Redmatica for the same reason - to use the tech, and the developer skills in their audio tools (primarily Logic). Many bits of AutoSampler and Keymap Pro made their way into Logic, GB and MainStage as a result.

They will make strategic acquisitions when they can gain something out of it. In Camel, and Redmatica's case, they got to use the IP, and got to keep the developers, so it worked out well for them. So it's not that Camel was a special case as such - it really follows Apple's standard MO in regards to purchasing other companies for the IP and the talent.

Edit: I see machinesworking was essentially typing the same thing as me at the same time!