In REAPER, Sitala can keep a copy of all its samples inside your project folder, so projects are self-contained: you can move them, archive them, back them up or open them on another computer, and every Sitala instance still has its sounds.
This is Collect Samples in Project, in Sitala’s options menu. It’s on by default, and it’s a global setting: it applies to all Sitala instances in all of your REAPER projects. It’s only available in REAPER, with the VST3 and VST versions of Sitala.
When you save your REAPER project, each Sitala instance saves its pads as a kit
file inside the project folder, in a Sitala folder in the project’s media folder
(Media by default, or the project folder itself if you haven’t set one):
Drum Demo/
├── Drum Demo.RPP
└── Media/
└── Sitala/
├── Sitala-15e590fc.sitala
└── Sitala_Percussion-8a41c2d7.sitala
The file is named after the track (with spaces replaced by underscores), followed by an ID for that Sitala instance, or just the ID if the track has no name. From then on, the instance loads its samples from that kit file, not from your sample library.
Sitala/.recycle folder the next time you save, rather than deleted, so Undo
still works. Recycled kits are cleaned up after about a week.Copy the whole project folder. When you open the project, each Sitala instance finds its kit file in the project folder, even if the project is in a different location or on a different computer, without looking for the original samples.
Uncheck Collect Samples in Project in the options menu. Sitala instances go
back to using the original sample files from your library. Once all of an
instance’s original samples are back in use, its collected kit file is moved to
Sitala/.recycle and cleaned up later.
Pads whose original samples have been moved or deleted keep playing from the collected kit, so it’s best to turn collection off on the computer where your sample library lives.
← Multiple Outputs · Contents · Next: Standalone App →
Contact