Sonuscore Ha pi Concert Harp is now Unified
Sonuscore have a great offer which finishes on the 28th March. (Magic Spring Bundle - Sonuscore)
The bundle includes Ha-pi Concert Harp which has an excellent sound. I have unified the instrument and patches plus adding a selection of my own new unify patches.
Hope you enjoy!
Do you know if these phrases libraries allow 'drag n drop' MIDI onto your DAW?
I must be installing this incorrectly. I create a gurulink file to the folder that has the Kontakt content for this library, and load the .guru file, but the links do not work. The old method is not working either, as I have updated Kontakt.
Hi, Daren. I could not see any 'drag n drop' MIDI in the VST. However, definitely worth the 9.90 Euros on its own.
Hi, Martin. Sorry to see you are having an problem with the file. I am sure Shane will get back on the Kontakt issue but, in the meantime, I just wanted to suggest that you or anyone else facing the same snag could convert the guru file back to a zip file by changing the extension and then install the folder manually. There are only 21 patches so a quick Batch Update would be quite quick.
@mac16174 is correct.
The problem with "unified" Kontakt libraries is that Unify only saves the state-data provided by the Kontakt plug-in, which includes absolute paths to all the required files. Because these are almost always different for each user, we either need a way to update them or a way to make them work without needing to be updated.
Prior to Kontakt v6.5, we used the first approach. Kontakt 6.4 and earlier would pop up a "Content Missing" dialog when loading a "unified" Kontakt patch (technically: when Unify attempted to restore previously-saved Kontakt state-data into a newly-created Kontakt instance), so you could locate the required folder manually and tell it to use the same folder location for all subsequent attempts. Having done this, it was only necessary to load and re-save each "unified" Kontakt patch, and we added a "batch process" function to Unify for that purpose. All this was done in conversation with the Kontakt development team at Native Instruments, who were kind enough to advise us.
Right after we went to all this trouble, Native Instruments surprised everyone by updating Kontakt to v6.5, which included changes to the way it presented its "Content Missing" dialog, which completely broke the first approach. In fairness, these changes were forced on NI by Apple; they had no choice but to make them to support mixed-mode (Intel/ARM) operation on the new "Apple silicon" Macs.
So, we next pursued the second approach. Through experiment, we determined that if a "unified" library is created with the underlying Kontakt library at a specific path, the folder at that path could later be replaced by a symbolic link to the Kontakt library folder somewhere else, and the "unified" library would still work as before. Because true symbolic links (which are distinct from "aliases" and "shortcuts") are difficult to make on both Windows and MacOS, we created a new utility app called Guru Link to do it, which we now distribute with "unified" Kontakt libraries.
This symbolic-link approach has one HUGE drawback, which is that (as @mac16174 has correctly pointed out) when the "unified" patches are being created, the Kontakt content folder MUST be located at a path which is guaranteed to exist and be valid on every end-user computer. After some experiments, we chose C:\Users\Public\Documents\PlugInGuru Links on Windows and /Users/Shared/PlugInGuru Links on the Mac. (Our Guru Link app creates the PlugInGuru Links folder; the location where it creates it is the part of the path that is valid for all computers.)
This drawback has two important consequences, which are themselves major drawbacks:
- The paths for Windows and Mac are not the same, so we have to create separate .guru files for Mac and Windows.
- The use of symbolic links cannot rescue a "unified" library which was created with the Kontakt content folder anywhere else than this specific location.
Further to #2: IF Kontakt 6.4.2 or earlier is available (we have it here), AND IF it can open content from the Kontakt library in question (which is not always the case), then we can use Unify's batch-process mechanism to rework the "unified" patches with the Kontakt folder moved to the "magic" folder (once for Mac and once again for Windows). I believe this is how Stefano plans to rescue his unified Ethera libraries.
I don't like this situation at all, but we are stuck with it. Native Instruments has tried to be helpful, but there are limits to what they are prepared to do to support a tiny company using Kontakt in such a specialized way. They have discussed a possible future addition to Kontakt, which might make this whole problem disappear, but we do not know when (or if) they will actually deliver it. One thing which might help nudge them along is if enough Unify users write to their support staff (POLITELY) and explain why this is important.
Shane, thanks for such a detailed explanation of the Kontakt issue. It begs the question of whether it is going to be worthwhile unifying Kontakt libraries for now. I only have a Windows PC so a Mac guru file is not practicable. Should I stop sending links for converted Kontakt libraries to the forum until there is a solution?
For future Kontakt conversions, just move the Kontakt library content folder temporarily into C:\Users\Public\Documents\PlugInGuru Links while making your unified patches. Afterwards, you can move it out again, and use Guru Link to replace it with a symbolic link.
If you don't have Guru Link, I posted download links here: https://forums.pluginguru.com/postid/8210/. I'll talk to John today about making these more easily available to all PlugInGuru customers.
If you make new unified libraries this way, and post links to them here, at least the Windows users (>80% of all Unify users) will be able to use them. Provided you do so using a version of Kontakt earlier than 6.5, I will be able to convert them automatically for Mac.
Thanks, Shane. I can certainly unify within the PlugInGuru Links folder and then move it back to its original location. My recent batch was done with Kontakt 6.5.2 but, fortunately, there has been a lot of debate about Kontakt versions on the VI-Control forums recently. From these posts, I have gleaned how to roll-back to a previous version which I have now successfully done so I am now going to use 6.4.2 again. To save some questions, here is the Windows method. I understand that Mac is broadly similar.
There are four main files which you will need to locate. On Windows, these are kontakt.exe (find path in Native Access), kontakt.dll in your 64 bit VST folder, kontakt.dll in your 32 bit VST folder, and kontakt.aax (C:\Program Files\Common Files\Avid\) if you are a Pro Tools user. There is no VST3 component of Kontakt.
Before updating to a new version of Kontakt, copy your present version (all files as above) into a separate folder and place the respective dll files in folder named either 32bit or 64bit as they have similar filenames.
Shane has suggested contacting NI support about the new Kontakt changes, and, if you wish to roll-back to a previous version that correctly worked with Unify, you could also ask them to supply the previous Kontakt 6.4.2 files to allow you to do this. That might also help with moving it up their agenda with regard to the change that NI have said can be implemented to assist Unify. As Shane has requested, politeness when contacting NI helps a great deal.
Thank you for these details. Note that for creating unified libraries, you will need only the VST version of the Kontakt plug-in (called Kontakt.dll on Windows), and you can simply move the pre-6.5 version to another location on your PC, then drag/drop it into Unify's Known Plug-Ins view (or use "Select plug-in file(s) to scan..." from the Operations menu if you can't drag/drop) to let Unify know where it is.
It should be perfectly safe to leave your pre-6.5 Kontakt.dll in the new location indefinitely, even after updating the Kontakt plug-ins in the standard NI folders to the latest version.