Why is Native Access such a trash product?
Comments
-
Native Instruments ? Did I get it right this time ? If so what did I win ?
3 -
A very good point for the conversation indeed. Of course, no vendor asks for that, neither NI obviously.
But, if you are a power user, or you want to do things your way, or you just want to know "how it works", then those (among other things) are a "must know".
If you are not, then simply sit and wait for a "future update" or for an "official announcement".
There is nothing "right or wrong" in both cases. It is just a matter of choice, or, if i may say, your personal point of view in life. Personally, I am creator and explorer and i also like to configure things my way (and i don't like to wait, too) so i always choose option 1. …and i like to share my founds with other like-minded people. 🙏
2 -
That's very helpful, thanks!
As am I. I'm just making guesses based on what I know, or maybe more likely, what I THINK I know.
That's not our job. We're here because we like the instruments, we like the people from NI (at least the ones who make a real effort here), and we feel a sense of responsibility to the users.
We don't work for Native Instruments, and as Poorfellow says above, we're just reporting the findings.
1 -
Wow, what a great response. I shall amend my stance then.
I'm ALSO here because I have a technical interest in all things PC (and maybe one day Mac too, hehe). But not so much that I would want to apply for a job!
But yeah, learning a bit about the registry here, and how an installer works there, and what the heck is supposed to happen when you uninstall something; that's kind of cool. It's better than sitting in a home somewhere and drooling all over myself while waiting for my pureed dinner. 😏
1 -
Thanks a lot for this! I took a quick look around and this seems like a reasonably easy workaround and is much appreciated!
A quick question about editing the XML files: I'm assuming I would need to edit both the <Name> and <RegKey> 'fields' (arguments? lol) correct?0 -
I don't know the answer. And since it's Saturday and I need to get outside and touch grass, somebody else will probably be able to tell us before I'd ever get around to testing it for myself.
1 -
No messing around took place. This folder structure has been in place for a few years now and is backed up to an external drive.
The game-breaking trigger here was my hitting "Update" when I was offered to update Native Access.As for the full paths, I thought I'd provided that both in writing, as well as in the form of a screenshot my friend:
F:\Native Instruments\
Individual examples included about half of the available expansions for Maschine (which I frankly never use), almost any (but not all) directory that had the word "Library" added, etc. Hope that helps.
0 -
Snow melted today for us here in Ontario, Canada, so I just might go and touch grass myself lol
0 -
Yes, that is correct
1 -
"I thought I'd provided that"
No, you only ever mentioned F:\Native Instruments\
The full path (to e.g. Solar Breeze) would be F:\Native Instruments\Solar Breeze\
I've just noticed, looking at my paths in Native Access, the old paths (without the added Library) have a \ at the end, and the new ones (Library) don't have a backslash at the end…
1
Categories
- All Categories
- 19 Welcome
- 1.5K Hangout
- 61 NI News
- 783 Tech Talks
- 4K Native Access
- 16.5K Komplete
- 2K Komplete General
- 4.3K Komplete Kontrol
- 5.7K Kontakt
- 1.6K Reaktor
- 378 Battery 4
- 841 Guitar Rig & FX
- 425 Massive X & Synths
- 1.3K Other Software & Hardware
- 5.8K Maschine
- 7.3K Traktor
- 7.3K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators