I was wondering if it is alright to change the location of samples on the same set?
Will it cause havoc to previous projects created in the current SET?
thanks!
You can do a ācollect samplesā for each of your projects, itāll duplicate the samples to your project directory. Youāre then free to move your samples hither and yon within the audio folder and it wonāt corrupt your sample link, as itāll use the local copy in the project directory.
Itās not as nice as the magic hashtable lookup that they use on the digi-series as youāll end up with duplicates, but this keeps the samples safe for each project your run the this function on. Hope this helps!
2 Likes
I always keep mine set to save samples in the project folder. 64gb is so much storage for normal use that Iāve never seen any reason to worry about duplicates and it makes it easier to manage things. If I use something thatās in a setās audio folder, it gets copied over to the project foder and never have to even think about accidentaly making a change that would mess up other projects on the card - every project is essentially sandboxed from every other project that way. It also means that incremental saves are all completely self contained, so if a project gets corrupted you can roll back to a new copy of your last working version and delete the entire folder ofthe corrupted version without worrying about sample locations (itās happened to me three times in 5 years, not a lot but enough that I always save as new before I make any major changes to a project AND after I have a project in a ācompleteā state).
The only reasons Iād ever use the default shared audio pool is if I needed to use multiple LONG samples (like 1-2 hours each) across multiple projects to the degree that using the auio pool would save gigabytes of storage space per project, or if I was using a smaller card (but even the 16gb factory card is a LOT of storage for audio - audio isnāt that big in modern storage terms).
It made a LOT of sense in 2010 when storage was more expensive. In 2023, when you can get an SSD for under $50 that would have cost over a thousand three or four years ago, storage space mostly doesnāt matter much until you start dealing with things like lossless video where even 480p takes something like 60gb per hour.
2 Likes
Great point, supercolour. Totally forgot to mention this is a possibility, cheers.
I also do this, however I am getting a little frustrated with recorded sample buffers being stored within the project, I occasionally want to share some of these snippets between projects and need to remember which project they were generated in.
Just a heads up of my own experience that it does have some downsides, and isnāt a fix all panacea for sample management woes :P.
Yeah, this is definitely one of the downsides. Less of an issue for me since I rarely save my record buffers anymore (a lot of what I do on the OT relies on using pickup machines with negative gain so that the record buffer changes every cycle, and that means thereās really never a finished recording to save), but when I DO save something in a record buffer I try to remember to also copy it into the audio pool so Iāll be able to find it easily if I want to use it again. Itās a little bit of a hassle but not bad (and if youāre saving a lot of buffers, you can just copy them all to the pool in USB disk mode later on). Basically, I use the pool like a sample library and project folders more like disks in an oldschool sampler.
