MeldaProduction folder structure (no rant)

[Autobot]

There a two different folders created on my system...

C:\ProgramData\MeldaProduction
C:\Users\noise\AppData\Roaming\MeldaProduction

I now wonder (a) for what there for? and (b) where are my stuff (presets, defaults, etc.) stored?
Thanks

[jmg8]

App data, is for your presets.

[MeldaProduction]

Correct. Situation got a bit complex, because of shared computers with multiple accounts. So there's the ProgramData, which is like a seed of factory data, and Users, where are your own data.

[Autobot]

Correct. Situation got a bit complex, because of shared computers with multiple accounts. So there's the ProgramData, which is like a seed of factory data, and Users, where are your own data.

So if I understand correctly this means when I switch my system I can without any problems copy C:\Users\noise\AppData\Roaming\MeldaProduction to my new laptop and keep therefore all my presets and configurations (like defaults etc.)?

[DarkStar]

The .winstate files define the position of the various windows. I think that you can delete those and they will be recreated when needed.

[dmbaer]

This brings up a question I was recently thinking about. With MSF supporting sample playback, some soundsets might be large enough to warrant user direction as to where they are placed on disk. On my own DAW, for example, my D drive (2TB) is pretty much dedicated to holding sample data. Will MSF have a provision to support that sort of custom placement?

[DarkStar]

I haven't tried it yet, but I'm pretty sure that you can put the samples and the compiled sample banks wherever you want.

Compile and assign sample bank takes all samples used in the module and compiles them into a sample bank (msamples) file, which stores all samples in a custom highly compressed format optimized for (pre)loading, caching and distribution.

When creating an instrument using samples, you are likely to initially use classic samples, typically in WAV format. The sampler needs to load them fully (no preloading is possible) and these are not convenient for distribution.

At some point, when the samples are processed just as you want, you will want to compile them into this msamples file, which provides a solid compression designed specifically for samples using this feature, and which also automatically maps all instances to these new compressed samples. From that point loading the instrument will only preload each sample (the load time depending on value selected in the global Settings / Sampler panel) and do all the necessary memory management. This will highly speed up loading the instrument, memory consumption and sample data size.

You may use this feature on an existing sample bank file as well. This is handy when multiple instances of the sampler module are used and may potentially share samples, or if you want to put all samples into a single msamples file. If you use this feature on such an existing sample bank, it will search for the samples and if they are already present in the sample bank, it will only map them to the existing ones. Samples, which are not found, will be added to the sample bank and mapped as well.

Before you start using samples, it is highly recommended to set the sampler root path in the global Settings / Sampler panel, then keep all samples and sample banks in there for easier maintenance. Storing samples in that folder is optional, but sample banks should be stored there, especially if you are going to distribute your sampled instruments. In that case you should put your sample banks into sub-folders named like this:
{sample root path}/company name/product name

This way you will ensure simple installation for the end users and minimize the chance of collisions with other sample banks. It will also simplify creating the product file to be distributed to the customers.

[dmbaer]

Before you start using samples, it is highly recommended to set the sampler root path in the global Settings / Sampler panel, then keep all samples and sample banks in there for easier maintenance. Storing samples in that folder is optional, but sample banks should be stored there, especially if you are going to distribute your sampled instruments. In that case you should put your sample banks into sub-folders named like this:
{sample root path}/company name/product name

Useful information. I hope that sound developers will make it straightforward to get your samples placed where you want them without having to think this all through every time. That shouldn't be too difficult, hopefully.