I purchased this today and it works fine with the Spitfire Library but unify can't find or play any files in Kontakt.I have Komplete 12 Collectors edition which includes all of the Symphony Series (note not called Symphony Essentials) I can access all my files in Machine/Kontakt 6 and Komplete Control but none of the Unified will play.
Any Ideas? I have all the plug ins in the Unity list.
Exactly the same issue for me. As a relative novice I would really appreciate being pointed to the latest advice regarding this issue. Skimming the Kontakt / Unify posts it appears there are several known issues but this problem relates directly to a product sold by Pluginguru and I would be grateful for any available technical support on the matter.
A lot of the Unify patches in the K6 SE version of this library are referencing to a Volumes/ROCKET-PRO that does not exist on my system.
Probably an external disk of the maker of that library. Not sure if this can be fixed without rebuilding.
A lot of the Unify patches in the K6 SE version of this library are referencing to a Volumes/ROCKET-PRO that does not exist on my system.
Probably an external disk of the maker of that library. Not sure if this can be fixed without rebuilding.
Well, maybe it is not that bad. I did some further checking and most of the patches work OK. I just deleted some that did not work for the above mentioned reason.
This problem arises because Kontakt does not know where to look, to find the samples. As @fotoxbr_nl has noted, when the Kontakt plug-in's state is saved (either in a Unify patch or in a DAW project; the mechanism is identical), it includes the absolute path to each referenced sample, which works fine for patches/projects saved and later recalled on the same computer, but will almost always fail when recalling the state on a different computer.
In Kontakt 6.5, Native Instruments added a new setting called Non-Player content base path into their Options dialog (click the gear icon in Kontakt, choose Loading from the list at left of the pop-up window), which allows you to choose where Kontakt should look for sample libraries. You must either save each library inside the selected folder, or create a symbolic link there, pointing to the actual location. Once you do this, Kontakt should be able to load these patches automatically.
This problem doesn't exist for Kontakt sample libraries which are compatible with the free Kontakt Player, because Kontakt uses an internal database to keep track of where these are stored. Many third-party sound libraries don't work this way (the vendor will specify "requires full version of Kontakt"), because NI charges a hefty fee for this. This is why the new setting is called "non-player" content base path.
We realize this is a significant problem, but it's due to the design of Kontakt itself, and hence outside our control. NI very kindly added the "non-player content base path" setting to Kontakt 6.5 because we reported this issue to them.