giancarlo wrote:which operating system do you have exactly? windows 8?
Yes win8.1 , but win7 also needed admin right after installation, updates or new 3rd party nebula stuff.
jorismak wrote:Do use created a 'C:\Programs' yourself? Or do you mean 'c:\Program Files' ? Cause in the 2nd case, it's sort of a special folder under Windows and there are special access rights (non-admin users can't do much there).
If you want to change it, you can move the folder to whatever place you want, and in your VST dll plugin folders, change the .xml files of Nebula. If you open the XML files in an editor (for example, notepad) you see a parameter 'DATAPATH' somewhere near the top, which you can edit to your new path.
Do this for all variations of the Nebula plugin you got (like 'Nebula3', 'Nebula3 Reverb' or more if you used Nebula Setups or something similar).
it's the same folder just in programs and not on C:\
but that's what I wanted to know: it's working if I just move the folder and change the xml files in the vst folder? or will I get problems with my registration of nebula itself and 3rd party libraries.
I would have checked it myself, but I already burned one nebula license by upgrading from win7 to win8.
in version 1.3.677 we improved further nebula setup loading time. Even if you will not use FROZENBOOT tag you'll get fast startup times (for 2000 presets I get around 1 second instead of 4).
I'm improving it further fixing the memory usage and removing the 10.000 presets limit. Actually I'm betatesting our library for the exception of alexb MFC and a couple of other libraries, and I have 13006 presets. I think nebula could be considered usable without frozenboot even in this particular case.