Why does Multisampler data get saved in the edit?

[ForrestH]

Why not treat it like imported wave data, and either leave it where it is or keep it as a single instance in the imports section of the Project structure?

[FigBug]

This is on the todo list to fix. The reason behind the current implementation is so that presets 'just work', but it slows down saving and bloats the edit. So the samples and preset need to be separated. Still thinking about the best way to do this.

I'd be interested in how people think it should work:
- Samples get copied into project folder
- Samples live in a common 'samples' folder
- Something else

[Cheve]

I think the same happens with Drums Sampler.
I would like to have the option. Sometimes it is nice to have the samples included in the edit.

[ForrestH]

Options are good. A common Waveform Samples folder would make sense for samples created in Waveform, while handling imports on the same basis as audio files.

[jabe]

I'm wondering about when it is that its presence in the edit is actually inconvenient. It could be part of the archive process, for instance. If users are sharing projects then it'd be useful to include the data.

[ForrestH]

I'm wondering about when it is that its presence in the edit is actually inconvenient.

500 MB of samples in every backup is half the reason I stopped using MultiSampler. Giant edits also multiply the odds of failures during saves by three orders of magnitude...

[jabe]

I'm wondering about when it is that its presence in the edit is actually inconvenient.

500 MB of samples in every backup is half the reason I stopped using MultiSampler. Giant edits also multiply the odds of failures during saves by three orders of magnitude...

I could have worded that bit better. What I was really wondering is when it might be needed as part of the project.