Ideally I'd like to tell Native Access, "Ok, register this specified new library in K6, but do nothing else. I'll put up with Native Access only to let me use new libraries which I'd be using K6 for, but that's it. per se, but because I question NI's technical competence have read just too many shameful tales of woe re Native Access) that I'd really hate to find, for example, that I have to re-download / re-authorise any instruments which already work well in K5. If I buy K6 and buy libraries which require NA, will NA mess with my K5 stuff (including already installed libraries) in any way? I'm so mistrustful of NA (not because I object to online licensing etc. Not even interested in the K6 version of the Kontakt Factory Library. I'd only use K6 for the new libraries I choose. I figured I'd just wait for K6, as I'm told K5 and K6 can coexist on the same PC just fine. The problem of course is that there are new libraries out there I'd like which require K5.5.2+. I've not updated Kontakt since 5.5.1 as I've read that, between subsequent 5.5.2+ versions of Kontakt and Native Access (NA), there always seem to be some bug or PITA that I really wish to avoid. (By the way, I'm ok with loading libraries via the file menu tab having things show up in the library tab means nothing to me.) This includes all 8Dio libraries, some Spitfire libraries, some Orchestral Tools libraries, some Keep. I love my Kontakt libraries, and my K5.5.1 (full) setup works just fine. Kontakt automatically adds libraries that are registered in your Native Access App, but any library that doesnt require a native access serial number is not present unless you add it yourself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |