Observation about Multisampla

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Evening!

Not sure if this is a bad thing but it kind of screams memory hog to me...

When you open an instance of Multisampla, flick through a few presets and then go to the multisample level, (perhaps to edit the multisample of the instrument you've chosen), it pops up a list of all the samples used in all the presets you've tried (but not chosen) as a kind of favorite list.

Wouldn't it be much more logical to only have the samples used in that particular preset? If you go through a dozen drumkits before finding the one you're going to use, you could easily wind up with hundreds of samples on that favourite list before you're reaching the slot at the bottom where you can choose a new one.

Also: Does that mean they're all loaded into the song's RAM even if you've changed the preset?

Marco :)

Post

When clicking the library presets at the left, the samples are indeed loaded.

When using the "Open Patch" button at the top of the plug editor, then a file browser opens, then when previewing patches, only the samples of the effectively chosen patch will stay in memory.

When you want to cleanup samples that are not used in the session then goto Edit menu -> Sample Manager -> Options -> Delete Unuseds.

Post

Hm, just tried the Sample manager and I'm not sure it's the best possible way - you really should be able to say "delete all unused" and do it with one click, instead of confirming every sample I think.

Ideally, I think Multisampla (and for that matter Sampla) should unload all the samples of a preset as soon as you choose another preset, elimiating the need for a "delete unused" function altogether.

Marco :)

Post

I know what you mean. Will work on it.

Post

Cool!

To be honest.. the more I'm thinking about this the odder this school of thought seems to me. There's absolutely no harm in deleting a sample from a session ("no undo!") really.
You can always load it into the session again.

I don't think we need a duality of deleting from a sample-slot vs. deleting from a session. You just wind up deleting everything twice.

Marco :?

Post

I'm not sure what you mean with "deleting it twice"?

Anyway, note that a sample could be used in several multisamplas.

Deleting it in 1 multisampla may not automatically delete it in the other.

Only the "Delete From Session" will delete it everywhere in the session.

Post

It's probably to do with my way of doing things - preset change = start from scratch.

True, when two or more instances of Mulitsampla/Sampla share some samples, I see how it's RAM saving to have a function like this, but I still think that once they're completely unused by any synth they should go from the session - no reason for them to just hang around because I already made a conscious decision that I don't need them.

That's what I meant by "deleting twice" -if you want an unused sample/unused samples to disappear from the session you have to change the preset and do the cleaning up in two different steps.
:)

Post

Ok. Will work on it!

Post

there's also something strange going on with the drumset multisample - when you first select the drumset and then the Stand-in piano, then the drumset again, there are two multisamples called drumset(1) and (2) all of a sudden. Doesn't happen with Stand-in piano.

:?

Post

Thanks for reporting. Researching...

Post

A little bug.

Will soon be fixed in 2.5.8.

Cheers :)

Post

Hehe! :D

Post

It's a very Fruitfull conversation, glad to see Mu.Lab is getting bug fix at this rate, the more I use Mu.Lab the more I'm liking it!

Post Reply

Return to “MuTools”