If one wants to keeps using m1.x, then one needs to keep the library folder intact - the option if one needs to save disc space is to update the sample path per project which means one must locate the samples by name. Simply put, maschine 2 does not need the maschine 1 library, but maschine 1 does need it. unfortunately, there was no import feature option for m2 that would update the samples used from the factory libraries to convert them to use only the new library.
Maschine library 1.3 how to#
perhaps a better method to suggest if one wanted to save disc space would be just to put the machine 1 library on an external disc or flash drive and update the library path in machine 1 to reflect this new location of the library, provided one reads the manual first on the library and how library paths work and how to change them. i wanted to save disc space and not have two folders of identical 32 bit stereo samples, but before i removed or changed anything, i backed it up on another disc so i could easily move it back or update the path from m1 to it in the m1 preferences. after i did this, i then did the alias thing with the sample folder only in case i wanted to still use m1.x. i chose to force my projects to not be able to find the samples and ask me to locate them which after it did i saved the updated project to the default m2 user lib. it really depends on if you want to still use 1.x still. I just meant the samples and for the mac version (i have not tested it on windows - but the behavior of the app should be the same when encountering a missing sample per the manual info), if you want to save 5g of disc space, they are the same.
0 kommentar(er)
