You are very likely going to understand very much of the xml file i posted as my second post just by looking at itĪnd are probably already making sub folders for you're 3rd party developers to keep you're libraries organised If you did understand this first explanation You can just copy this path and fill in the name of your external hdd with the name you gave itĪnd fill in your nebula libraries folder with the name you gave itīut i highly recommend creating organised subfolders within your main nebula libraries folder as this libraries will be a huge mess if you just drop them all in the same place, it will still work this way though so thats up to youĭont be afraid to ask if you cant make it workĪGAIN MAKE SURE YOU TAKE A COPY OF YOUR XML FILE BEFORE YOU CHANGE ANYTHING JUST TO BE ON THE SAFE SIDE I hope this first explanation helped a little
Now take a look at the first xml file i posted and see what changed from this new path to New hdd i created, you will learn a lot from that What i did not find and understand before i obviously found it my self was that the ALTERNATIVEDATAPATH have to start with volumes on osx to work So heres what the new path would look like with the new external hdd : So now we can go in to our xml file(located in component folder for logic users) and direct to that external hdd Ok now we have made our folder:Nebulalib, placed it on the root of our external hdd we called: New hdd So in this Nebulalib when you open it it should be two folders Vectors and Programs, i know you knew that, but for the sake of not keeping anything out i mentioned it hehe
Lets say we install all our vectors and programs in this one folder Nebulalib the first time around to keep it simple Lets call the new external hdd for: New hddįirst thing i would do is to place my nebula libraries on the root of the new hdd, so lets call the nebula library folder for Nebulalib So lets pretend now that i just bought a new external hdd where im gonna put my nebula libraries on ( in between here is where you change your path/paths )Īnd change nothing under this line and the line it selves Library/Audio/Presets/AcusticaAudio/Nebula3/ Its between these lines you have to make the changes with the ALTERNATIVEDATAPATH who directs to you're external hddĭo not change anything over this line and this line it selves Osx external hdd nebula libraries explanation : Im gonna fill in a better explanation in this post trough the day, so bare with me ,its work in progress Volumes/osx hdd/nebulapro/cdsoundmasters/ WITHIN NEBULA AFTER REMOVING YOUR LIBRARIES FROM THESE FOLDERS VECTOR AND PROGRAM So you can not delete Vector and Program folders where nebula is installed as those files need to stay in thereĮverything else in vector and Program folders in the nebula directory should not be a problem to remove and be placed on external HDD INIT.N2P and INIT.N2V must not be deleted,
You can do the same with the reverb versionīut once you understand this you may want to organise your folders within the main nebula libraries folder different than i did it, thats totally up to you When you have successfully gotten this to work with the regular nebula xml
MAKE A COPY OF YOUR XML FILE BEFORE YOU MAKE ANY CHANGES TO BE ON THE SAFE SIDE
Im a Logic Pro X user so its the Nebula3 圆4.xml you should start with within the component folder if you use Logic Pro Xīut you should first look at your own xml file located in component folder if you use logic and see whats different
Ill start with posting a copy of my xml file with path`s for external hdd So we can have it in one place rather than scrolling trough countless of Nebula tip of the Month
Ok, we need a place to explain and share information on how to for nebula
Its not that different from osx but it always helps to see the correct paths for understanding the patterns for those who struggle a little, i struggled my self in the beginning so i know exactly how that feelsĮxternal HHD`s can be used with great success on both windows and os x, even with sub folders Edit (Mai 7th 2016) : im gonna cover Alternative datapaths for windows too very soon since i recently moved to Windows Reaper