View Single Post
Old 14th November 2019
Here for the gear

Originally Posted by SteDal View Post
Roeland, please let me understand a thing: what do you mean by "N4/VST2 version"?

I'm asking you because AFAIK the so-called N4-x64 installation is the 'normal' way to install an Acqua library, which you can find in the regular N4 program browser under the 'Acqua Library or Effect' tab.
This kind of file format doesn't need to be scanned and enabled by Cubase or any other DAW. It's an entry within the N4 browser.
Then you may install the same library as 'N4 VST2 (or3)-x64'. This is a regular VST format and as such it's scanned and listed in your DAW as a separate entry in the VST plug-in window.

So I need to get this thing right first, before attempting a solution...

And re: the lost setting at reload time, as I wrote you yesterday, just try to rollback N4 version to N000 (Aquarius, Update tab). It should solve the problem.
Hi SteDal,

By the N4 version I mean the N4-x64 installation which you explain is the ‘normal’ way to Install an Aqua library. In my case the DLL’s from the N4 installation do get scanned by Cubase. I have figured out that this is the result of my choice to install the n4temprepository on a different drive then my operating system.

I do this for 2 reasons. 1) All the samples of my ‘old style’ N4 libraries (TimP, Cupwise etc.) my Aqua’s and your Mantis library, take op 50 Gb of disk space, which put unnecessary strain and take up unnecessary space on the SSD with my operating system. And 2) I understand that is still good practice to run your samples from a different drive then your operating system which has Cubase. All major companies producing VST instruments with samples (Spitfire, NI and VSL, East West etc, etc. advise this). As all Aqua’s or N4 libraries are built from samples, which have to be loaded every time you use a plug-in or adjust a setting, I gathered that it would be wise to put them on a disk exclusively dedicated to samples.

In Cubase it is no problem using a different drive then the operating system for samples. You can tell Cubase to scan any drive you wish for VST2 instruments and or FX plugins in the preferences of the VST plug-in Manager. So in these preferences I have included the N4temprository on my F drive as a location to scan for VST2 plug-ins.

So all the XLM’s in the n4temprepository on my F drive are scanned by Cubase – as of course they also would if I installed my temprepository on my C drive. I have Azure2, Magenta, Titaniumbasstard, your great new Scarlet4, and your great older Water2 (Wow what a compressor!), the Caribou compressor by Prime Studio and the older Violet compressor from Acustica. Not one off their XLM’s is blacklisted by Cubase – your Water and Scarlet libraries also don’t give any trouble.

Only the Mantis XLM’s are blacklisted, also if I install the VSTt2 version (the separate VST plug-in). As stated earlier, this is strange, but no problem as at all because although Cubase blacklists the XLM’s the plug-in is loaded as it should. I only discovered that when looking under the hood by clicking the edit button on N4, In a 96 K project, Mantis loads 44K samples. (Sorry for this new problem).

PS. I understood that the loss of the settings of the N4 libraries is a bug that needs to be addressed in a future update of N4 and that at the meantime rolling back tot the N000 version is the temporary solution.

Sorry for this long post…

All the best!