NI issues

[TIBrent]

Does anyone else have consistent issue's with their Native Instruments plugins? I have the iZotope subscription every month mainly for Ozone, but the other stuff is pretty nice too. But it seems like every couple of weeks I go to launch Studio One 7 and it crashes on launch due to iZotope specific issues. Each time, I have to "reinstall" the plugin from within Native Access. And it's not just limited to that. It will be a few weeks or so between times when I launch a Kontakt library: Thomas Pridgen drums, Kurt Ballou Room Sounds, etc & when I go to insert them inside Kontakt I'll get an error saying it can't locate any of the sounds/samples of any of the instrument. Again, I have to start re-installing the specific instrument. Is this exclusive to me or does anyone else around these parts have any experience with this. Thanks in advanced.
-Brent

[Dirk Diggler]

Sounds like an issue with Izotope Ozone, are they owned by NI now?

[jules99]

Good morning from 2023, Mr. Diggler.

As for the issue, this might as well be an issue of the version of Studio One or the operating system you have installed, at least with regards to Ozone. I've had 11 running in Ableton 12 for years without a single crash or so, in macOS.

As for the Kontakt issue, that is tragically true, how forgetful this thing is when it comes to the location of the instruments' samples. I've had this happen recently, 150+ libraries needed to be relocated manually, as Access did not, even after numerous deletions and re-installings, notice the folder, everything was in.

I've also had it happen that macOS randomly decided to change the name of the external hard drive (say from "volume" to volume 1") which messed everything up big time, including Kontakt.

Have you tried contacting the support, both of NI/izotope and of Presonus?

[db3]

Today I found a load of NI expansions missing in Maschine. When I looked in Native Access most of my NI plugs had to be 'repaired' by re-pointing them to the path they already had saved. Couldn't see any reason for it.

[jancivil]

I use iZotope Neutron 3 and 4 all the time, and Ozone Imager 2 in every project for a while. No issues at all. No subscription.
I don't experience that issue in Kontakt. I'm not using K8, I have one thing requiring 7 I saved as that before it acquired some attributes i really dislike.

[Daru925]

I dont know if its specific to ni, but i tend get kontakt errors or neverending loading libraries when i connect my external ssd before launching the daw.
The whole setup is a bit unstable at times.
Hope you can sort your issue.

[zerocrossing]

There's one Kontakt factory library... I can't remember which one at the moment, but when it's loaded I just get a constant stream of script errors from it. It's been like that for a long time. I'm amazed it never gets fixed.

[mi-os]

Today I found a load of NI expansions missing in Maschine. When I looked in Native Access most of my NI plugs had to be 'repaired' by re-pointing them to the path they already had saved. Couldn't see any reason for it.

Is this on Mac? There seems to be any issue with NA at the moment. They're already working on a fix.

[TIBrent]

I have a Mac and I’m running the latest OS. I’ve experienced this issue with both Presonus Studio One 7 and Logic Pro. Frustrating, sometimes I just want to get going on a project and then it’s like “oh yeah, time again to reinstall”. Ugh.
-Brent

[db3]

Today I found a load of NI expansions missing in Maschine. When I looked in Native Access most of my NI plugs had to be 'repaired' by re-pointing them to the path they already had saved. Couldn't see any reason for it.

Is this on Mac? There seems to be any issue with NA at the moment. They're already working on a fix.

Yep (Sequoia)

[Scoops]

I was consistently struggling with NA until I killed NA processes at startup.
I was consistently struggling with poor customer support, but since I killed NA, everything is fine.
I consistently struggle with the download of any library. I'm on a 1G fiber, and it still takes days to download my complete set
I consistently struggle with the NI Forum, which is IMHO is a hostile experience.

[Bombadil]

There's an update for Native Access on NI's page. It seems to have fixed the disconnected library issue (though you'll still have to link them again). It happened to me about 3 weeks ago, then happened again last night, when I was too buzzed to attempt to fix it. Native Access doesn't seem to be able to update itself from within the app. Have to get the latest v. from the website downloads page.

[jancivil]

NA was rather a nightmare for a long time here in that there is a dependency that was known to be a botch ("Aria 2c"). It would not complete any installation; it would finish the download in any case but delete the disk image, so it was either grab it at the split second between the thing appearing and its disappearance, or not. At that time Steinberg Download Ass. had the same issue and so did VSL Vienna Assistant. Their support acknowledged the issue and was aware of Steinberg's. But these left the disk image alone. MacBook Air M1, Sonoma OS.

back in Feb. I acquired an M2 Mini with Sequoia on it. NA worked perfectly. I don't have Cubase on it, it's strictly for VE Pro by LAN, but Vienna Ass. also quit failing. So now I have a fair few duplicates of Kontakt libraries on two external SSDs and finally sorted all of that. Some of it it knows from strictly via the networked drive.

I don't have anything made for the platform all that recently.

[AcrossTheSky]

Ni is trying to force upgrades ... if you accidently update a library to one that only kontakt 7+ supports > the whole thing falls apart - ( paths, lib naming ) you end up looking for isos to reinstall affected libs ... Ridiculous....
If onyone still has kontakt 6 > upgrade should not show ..

[Ah_Dziz]

There's one Kontakt factory library... I can't remember which one at the moment, but when it's loaded I just get a constant stream of script errors from it. It's been like that for a long time. I'm amazed it never gets fixed.

I have a crazy amount of Kontakt libraries and at least 10 percent of them display regular errors. The errors don't actually effect anything I'm doing they just pop up on the bottom of the GUI. A smaller number have real scripting problems that can lock up Kontakt or kill an instrument so that it must be reloaded. I always report the latter. The former, I just let them slide. Some of the best libraries around, scripted by Kontakt Ninjas like Greg from OTS , have the odd error pop up on the GUI. As a platform I still think Kontakt is the best for high performance and massive voice counts, but I wish they didn't give it such massive updates all the time. I'd be happy if they'd kept K5 or K6 and only fixed bugs. Honestly K4 was fine too. The constant updates and upgrades are not only expensive but I'm always worried they'll just break something that was working fine. So I never update libraries in a way that breaks backwards compatibility.

Edit: oops, I didn't notice "factory" in your post. There's plenty in all the factory libraries going back to K2 that have the odd script error. I'd imagine they're too busy trying to churn out new content to worry about fixing old content. Especially with so much of that content being made by 3rd parties.