Some NI Libraries now updated to require Kontakt 7.6?

[mi-os]

I'll make sure this reaches the right people.

Please also remind them we're waiting for the important Battery bug fix (BT4-2680 - the sample relocation bug).

Another urgent question would be when we will be able to automatically replace old Battery (say B2 and B3) instances in old DAW projects with the latest B4 VST3 using tools provided by the VST3 SDK. Just being able to load and map the correct samples would be a step in the right direction since old Battery versions can't be activated anymore. It would be very welcome even if the replacement isn't going to sound exactly the same in some cases. Transfer of parameters like envelopes, tuning, volume, panning and so on should be feasible.

[EvilDragon]

This is not a thread about Battery.

(But the right people already know about the issue and are looking into it.)

[felis]

Just checked NA and I've got several programs that have updates.
I've got Kontakt 6.8 though and am afraid that if I update, I won't be able to use them.
There are no notifications or warnings about them though.

[zvenx]

But the Read Me say?
rsp

[sacer]

Yes I am not forced, but I have updated before reading this thread and now I can’t roll back.

What you still can do is contact support and ask for earlier version installers. Then you can roll back.

Would be better if NI gets anytime the long loading times fixed. The support isn’t able to adress these issues. So the delevoper should compare, what is Kontakt 7 scanning, what Kontakt 6 doesn’t scan to to optimise this issue. They already know that the Korg gadget NKS files take the loading time up to 4 minutes. I don’t know if the Kontakt 7 engine Scans also plugins, but I would have no problems to use Kontakt 7 instead of Kontakt 6 if this issue would get fixed.
Also for battery 4 it won’t take them this long time, to check if the new linked library path from NA2 contains the samples, before asking for the sample folder.
Also after the last update from guitar rig 6 the loading time has significantly increased.
I know that we are a minority with this issue, but it makes no fun to open battery 4, maschine2, Komplete Kontrol or Kontakt 7, if you have to wait minutes. I was able to compensate battery and Maschine with algonaut and compensate Kontakt 7 with version 6. but I really would like to use maschine2 again and would also prefer Kontakt 7 instead of Kontakt 6.
Maybe you could also adress my kore2 issue.
Old versions of massive, fm8, absynth and guitar rig don’t get activated with Native Access2 but with Native access 1 they get activated. I don’t want to roll back with Komplete 14 CE to native access1, it would be easier if NI could add these activations from NA1 to NA2. I had used an extra folder for these plugin versions and since my last cpu update, most Kore2 sounds are now not able to edit, because these plugins can’t be activated. The support had no understanding for my issue, because it’s no actual product

[noiseboyuk]

My guess is that the long load times (at least on first launch) are connected to the new browser's database.

[bmanic]

So you're just confirming that what he says is a fact and that the user needs a workaround after the update. You know not everyone using Kontakt is reading this thread or this forum right? Or should people rely on random forum people to be able to load instruments?

No, people should just read release notes and not mindlessly click Update.

This is just dumb. NI should have this feature built into their application. It isn't difficult to make a string that checks if you own Kontakt 7 or not and then not allow the update.

Or at the very least the NI Access should have the option of rolling back to previous update(s).. this would be a good feature to have in general.

[glokraw]

Native Access should be optional, as it's mainly for those wanting an automated install of Komplete,
or large portions of it. Every individual item should have it's own installer, and then be able to be registered online, or off.

NA has always failed to work as advertised/hoped-for, for enough customers, that long threads
of ridicule keep propagating. Providing individual installers and simple registration would certainly
be welcome for some paying customers. The box is damaging the goods inside it

[Echoes in the Attic]

Native Access should be optional, as it's mainly for those wanting an automated install of Komplete,
or large portions of it. Every individual item should have it's own installer, and then be able to be registered online, or off.

NA has always failed to work as advertised/hoped-for, for enough customers, that long threads
of ridicule keep propagating. Providing individual installers and simple registration would certainly
be welcome for some paying customers. The box is damaging the goods inside it

But but but... there's a light and dark mode now!

[sacer]

My guess is that the long load times (at least on first launch) are connected to the new browser's database.

Yeah a second instance of the same plugin opens fast, but why does the new browsers database also is needed in battery4, Komplete Kontrol and maschine2, they have exactly the same loading times than Kontakt 7.
Also if you open up all 4 plugins you have to wait for every plugin a long long time to open.

[funky lime]

My guess is that the long load times (at least on first launch) are connected to the new browser's database.

Yeah a second instance of the same plugin opens fast, but why does the new browsers database also is needed in battery4, Komplete Kontrol and maschine2, they have exactly the same loading times than Kontakt 7.
Also if you open up all 4 plugins you have to wait for every plugin a long long time to open.

iirc i solved the K7 extreme loading times (like 10+ seconds for the first instance) by manually deleting a bunch of extraneous XMLs for stuff i no longer had installed. I wanna say they were in a weird folder specific to Native Access ... i wanna say %CommonProgramFiles%\Native Instruments\Service Center

very unofficial, and backup before you mess with stuff ... this is not a method support suggested (a lengthy exchange with support basically amounted in them basically basically admitting "kontakt 7 is just that slow, sorry"). not sure if NI unreg tool is needed in conjunction, but probably couldn't hurt.

[funky lime]

(besides buying K7, which was the ulterior motive all along i suppose)

No, that is not the ulterior motive. The motive is updating products to work with the new keyboards. This comes with certain requirements.

Ah, so the ulterior motive was to sell new hardware. Thanks for the correction

[sacer]

My guess is that the long load times (at least on first launch) are connected to the new browser's database.

Yeah a second instance of the same plugin opens fast, but why does the new browsers database also is needed in battery4, Komplete Kontrol and maschine2, they have exactly the same loading times than Kontakt 7.
Also if you open up all 4 plugins you have to wait for every plugin a long long time to open.

iirc i solved the K7 extreme loading times (like 10+ seconds for the first instance) by manually deleting a bunch of extraneous XMLs for stuff i no longer had installed. I wanna say they were in a weird folder specific to Native Access ... i wanna say %CommonProgramFiles%\Native Instruments\Service Center

very unofficial, and backup before you mess with stuff ... this is not a method support suggested (a lengthy exchange with support basically amounted in them basically basically admitting "kontakt 7 is just that slow, sorry"). not sure if NI unreg tool is needed in conjunction, but probably couldn't hurt.

I am aware of deleting xml, I have reduced my loading times from 4 minutes to only one minute, but I have lost a lot of NKS libraries therefore.
And also one minute is still a long time, if Kontakt 6 needs 5 only seconds

[zvenx]

After seeing you also have loading issues in modwave, I am even more curious about your computer.
What anti virus do you use on it and have you excluded the folders, all folders that you include samples on from it?
rsp

[Funkybot's Evil Twin]

So you're just confirming that what he says is a fact and that the user needs a workaround after the update. You know not everyone using Kontakt is reading this thread or this forum right? Or should people rely on random forum people to be able to load instruments?

No, people should just read release notes and not mindlessly click Update.

This is just dumb. NI should have this feature built into their application. It isn't difficult to make a string that checks if you own Kontakt 7 or not and then not allow the update.

Or at the very least the NI Access should have the option of rolling back to previous update(s).. this would be a good feature to have in general.

Or if I'm understanding the issue...just installing in as an entirely new version, keeping old versions completely unchanged. Then having "Komplete Kontrol" or whatever do a check: if new libraries are installed, ignore old (to avoid duplicates). This way the two can live side-by-side with no risk to any users.