MIDI Mapping doesn't save w/ preset

[sdv]

When I create my MUX synths & tools I'd like to map out my MIDI controllers and have that mapping be saved in the actual patch. Right now that doesn't happen. The mapping is saved in the patch that's in the original Project I created the patch in but when I bring that patch into a new project (from the MUX Presets > Users folder) those mappings aren't attached meaning I have to manually re-map my controller. It seems like this just shouldn't be. Is there a way to have the CC mappings saved with each preset I make?

[MuTools]

See http://www.mutools.com/info/docs/mux/us ... llers.html

Does that answer your question?

[sl23]

Unless I miss something, no, it doesn't.
Do you mean to say that mappings are saved within a modules? So if I use a patch with a filter module and map cutoff to CC1 save the patch then that CC1 is saved to control cutoff regardless of project it is used in?

[MuTools]

Those questions are answered on that doc page.

[sl23]

There is no mention of saving anything, only stored is mentioned on this page.
Data is stored in RAM, but it is not saved.
My question was "are mappings saved within modules?"
That page does not answer that question. I reread it to make sure.
Where are Mappings actually saved to? If at all.
Can they then be transferred across projects?

[sdv]

Does that answer your question?

Yup, it sure does. I can see where saving as a rack makes sense in an object sort of way. All is good now.
I wish other apps like Fruity Loops worked that way.

sl23: you have to save the entire rack that holds your synth (or whatever you have mapped). Just right-click on the rack then Presets > Save As Preset File...

[sl23]

Thanks sdv that answers my question

Perhaps that statement should be included in the manual as that explains better what to do.

[MuTools]

The doc page also says that if you want to store=save MIDI controller mappings in a specific module (eg a MUX Modular preset) then use that module's Map MIDI Controller / Edit MIDI Controller Map function.

[sl23]

Also, this doesn't make sense:

If you map a MIDI CC by right-clicking a parameter (as explained above), then the mapping is stored into the module that currently has MIDI input focus, which not necessarily is the module itself.

Not your fault Jo, but it's a poor translation.
I believe it should say this:

If you map a MIDI CC by right-clicking a parameter (as explained above), then the mapping is stored in the module that currently has MIDI input focus, which is not necessarily the module itself.

What is meant by itself? That doesn't make sense. Do you mean the current module focused in the GUI?
I appreciate English isn't your first language and that it's difficult to get it perfect, but things like this can make sentences nonsensical.

If I had time I'd proof read the whole manual and suggest changes, but I don't at present. But I may start to do so at some point to help make it easier for us native English to understand.
If you are ok with that, that is?

One thing that seriously needs doing is adding columns to the pages, minimum of two, but three would be better for HD screens. It makes it easier to read and keep your place in the text. Perhaps you can change a page at a time when you go to edit a specific page rather than take time out to do it in one go?

Here is an example of a better, not perfect, translation of the About these docs page:

About these docs.rar

Hope this helps

[MuTools]

I've fintuned that doc page.

[sl23]

Thank you, please read my last post again as it may be of use to you and your users.

[sl23]

Sorry I missed your reply before that last post.
I understand your perception of the word stored=save, but it is not a concrete term and is open to interpretation, as I have shown.
Save(d) is not. Stored could mean temporary, it is open to the user to interpret it's meaning. Save(d) cannot be misinterpreted.

I can help with translation if you wish it. It will take quite some time to change the whole docs page by page, but I'm willing to help. The offer is there...

[sl23]

I will say that your English is very good, but obviously you aren't going to be perfect. Not even the English are perfect at it, myself included.

The only thing I will say about is, it's all about impression. Now, I know most users don't judge, but surely you're after creating a professional image? In order to do that you need to redo much of the docs.

Part of the reason I never bother with them is because they are difficult to read both physically and grammatically.

Ok, so, look at it like this... When anyone from any country speaks their own language, they are very fluent. When that same person learns a second language, it takes a long time before fluency kicks in. Even then, there are always subtle nuances within a language that you miss. Going back to the fluency part, don't take this as a judgement, I am not being harsh as I understand how hard it is to learn languages. But... look at the forum, there are several users who write with poor English as it is their second/third language. But they APPEAR as fools in a way because they stumble with the grammar like children, ie, unprofessional.

I mean no disrespect, completely the opposite, I think they've all done well to learn a second language. I simply try, poorly, to point out the issues the docs poor translation and it's knock on effects.

Anyway, I don't want to waste your time, so I'll leave it up to you. As I said the offer is there, just let me know if you like help.

[sdv]

The doc page also says that if you want to store=save MIDI controller mappings in a specific module (eg a MUX Modular preset) then use that module's Map MIDI Controller / Edit MIDI Controller Map function.

That's smart as well. That way if you *always* want say filter cutoff to be CC102 then save that in the filter module before creating a larger synth.
If one wants to create a MUX tool/synth and perform the mapping afterwards save the rack.
Forward thinking all around!