Possible to have default controller mapping for Multisampla?

[LYTZ]

And another question...

Is it possible to save user default controller mappings for muSampla and Multisampla?
Or is there a possibility to save muSampla and Multisampla like a device default preset?
(kinda like default plugin presets in other hosts, you instanciate the VSTi and the default preset gets loaded)

So that when I drag in a sample or slice some stuff up, I have my basic bread n butter stuff mapped already?
Or is there maybe any other way to do this?

We have already the ability to import and export note names. Wouldnt it make sense to be able to import/export controller mappings as well?

Thanks,

tL.

[MuTools]

You can setup eg a MuSampla as you wish and then save it as MyMuSampla.Mux in your user library. Then whenever you need it, drag-drop it from your user library.

[pljones]

You can save anything as a user preset and it'll be there for when you want to recall it. In the modular area, to the right of the patch name are "Open", "Save" and "Save As" buttons. To create a new patch, you want "Save As", then click the smiley face, then Go to favourite, User Library and save the patch where you want (creating any directories you'd like).

[LYTZ]

Well, I know. I was asking about defaults. Not saving and loading basic presets.

Consider this: I audition loops or samples into the arrangement area. Mulab asks me what to do with this. (stream/slice/sample)
I slice it up. Then I get the default Multisampla. Question is, can this instance of the default Multisampler "Template" be
saved somehow, so that whenever I drag something into the workspace, I have the default device mapped already?

However, I already have a pretty smooth workaround for that, because Mulabs sampla file handling is pretty slick.
I just replace the sampla with the one I want and reload the sample into that one. One step more, but still darn quick.
Also that markers are saved within the file is pretty nifty and quick enough.

Also kudos for the ability to save .xml marker files, I use this a lot already. Love it...

Thanks,

tL.

[pljones]

You can save pretty much anything - including an entire project - as a template.

EDIT: Or do you mean you want command macros: stringing together sequences of command actions?

[sl23]

Do you mean save midi controller mappings? So if you have say, 5 presets using the same mux config, and change from one to another then the midi map stays active even though the preset has changed.

So it's like saving anything else but the maps are seperate entities like editing and saving a sample, preset or whatever. Basically, midi controller maps as templates themselves.

I asked for this quite some time ago, is there any update on this Jo?

[LYTZ]

Do you mean save midi controller mappings? So if you have say, 5 presets using the same mux config, and change from one to another then the midi map stays active even though the preset has changed.

Exactly.

[MuTools]

Well that's the problem, there is no such thing as "the same mux config", each MUX can be different and thus it's not obvious to have a MIDI controller map that serves multiple MUXes, cause what if a map points to a module that does not exist in another MUX config?

[LYTZ]

Indeed. Thats why I am happy with the workaround anyways, because it makes more sense that way and is still very fast to do.

[sl23]

Well that's the problem, there is no such thing as "the same mux config", each MUX can be different and thus it's not obvious to have a MIDI controller map that serves multiple MUXes, cause what if a map points to a module that does not exist in another MUX config?

I understand the problem, but how about saving mappings in some generic way? Like for example, filter, resonance, amp ADSR, so that they can be set to a specific controller and saved as a preset. Then when loading a MuX preset you would choose a mapping preset to fit. Any controls not mapped simply would have no effect.

At least then you'd have a simple way to dial in mapping to get you started.

Or, maybe if you had several MuX presets in a folder for the same config, yes I know all MuX presets are different, but certain ones are also the same. If you had 10 presets for the same synth config for example, ie, 10 patches, then a mapping is easily compatible between these 10 presets/patches. This is where it becomes seriously useful. I mean are you telling me you all use a Mux only once and never tweak to make new patches? Of course you do.

Whether a synth or effect, we all save different versions of a MuX preset even if it's just one or two. But if you like making new patches then you could end up with hundreds of different patches for the same MuX config each being identical with the only exception being the parameters have different values. This is where the idea of saving MIDI controller mappings is really helpful and can save a massive amount of time.

You could say well save one as a template and work from there, but life's not always that simple. Perhaps, like someone here said before, you work on a laptop away from MIDI controllers on the way to work, or just away from your studio for a day or two. You make a load of presets/patches, get home and find you then have to go through the laborious process of mapping every parameter in each of your patches rather than just do it once and dial in the mapped preset for the rest.

I hope that all makes sense, maybe it's not for everyone, but then there are many things in MuLab that aren't for everyone, that's the whole point to provide variety, to make things faster, easier and more intuitive, and try to please as broad a user-base as possible whilst making the most of dev time.

MIDI map presets would be useful, it would save time, though I do realise it would need researching to find a good way to implement it, hopefully it's something that could benefit MuLab and it's users.