I usually make a photo or take notes about the sample pool so i can remap sample in their according slots… Also i force myself to not fill everything in the RAM i usually keep some free slots so i can map missing sample if required. A Backup is always system files + sample (and remap them if required) it’s nice to take notes… and usually help to save as sounds… on the +Drive. Also i always keep and dump what i find interesting so i can dump back when i need it…
That’s why i post adding sounds from kits… Adding sounds from Kits into project
I always keep a clone of the same file organization (Internal AR) on my computer /project folder/ , /+Drive folder/ , /Kits folder + sample pool folder/ it’s huge thinking and self organization but it’s worth the price DON’t TRUST THE MACHINE EVER hahaha
That’s my experience of the Octatrack lead me that way
Also post by @Speedball
Transfering Sounds or Kits between different Projects require to save each sound to the +Drive first.
If you have saved a sound (which contains a sample) on the +Drive and you want to load this sound in a new project, the AR will automatically load the needed sample to a free slot in the projects sample list. No extra work to be done. Same goes for the Kit. All the sounds of the Kit must be individually saved on the +Drive. You are then able to copy a kit (Load Kit, mark the Kit you want to copy, FUNC + REC) to another project. In the new project, Load Kit, mark a free slot, Paste with FUNC + Stop. Done.