FR - Across the Board

[dmbaer]

Unless I'm overlooking something (been known to happen ), it's often not at all easy to find the source of modulation for a parameter, especially in the more complex plug-ins like MPowerSynth and MXXX.

I would like to suggest a capability to call up an information-only panel (nothing more than a close button) that displays all the modulation mappings. Nothing fancy - just source and target. If we want more details we can go to the source (now that we could easily find it). It would also be useful to include any MIDI to MP mappings as well.

Edit: I should have said more than "all the modulation mappings". I would also think that any control influenced by a multi-param would also need to be in the information panel. Again, just target name and source name is all we need here.

[MeldaProduction]

Well, not that it wouldn't be completely useless... I'm not sure how much is this worth the effort to be honest. And then there are rather complex problems - imagine a multiparameter controlling another multiparameter controlling the first one . Right now it is handled in such a way, that closed circles (hence neverending loops) are always forbidden, but it would look kind of crazy in the log and if I imagine a complex scenario, with lots of mods and multiparams (for which this is actually useful, I don't think the log is useful for simple stuff), it would just be a nasty huge set of information, and I'm not sure if it wouldn't be more confusing than not looking at it at all . Not sure really...I'll think about it.

[dmbaer]

Maybe you're overthinking this. Here's what I'm suggesting. For any parameter that's influenced by an MP or a modulator, give us the name of that parameter and the name of the MP or modulator that's the influencer. Also, if any MP is a slave to a MIDI event, give us the name of that MP and what MIDI event type is involved.

That's it. That's the hard thing to track down as a user who didn't define a preset. Once we know where to look, we can do any further research ourselves. Granted, for many situations this is not all that useful - there aren't all that many places to look for this kind of information when there's only a couple of modulators and/or MPs. But for MPowerSynth and *especially* for MXXX, hunting down what's-affecting-what relationships can be a bit overwhelming.

Anyway ... yes, please to give it a little thought. It's not an essential feature to add, but upon further consideration it turns out to be not-so-challenging, it would be a welcome addition to the architecture.

[DarkStar]

If I understand correctly, you are looking for an easy way to see what Multiparameters / Modulators / MIDI Controllers / MIDI Note Controllers are controlling each parameter. At the moment you would need to look through al the 'controller' windows to find out.

Perhaps a list (in parameter order) like this (mock-up hacked together from various plug-in existing windows):
>>> http://i.imgur.com/EfWcBZJ.png

And if you click on a 'Controller' its window will open automatically, so that you can edit the details.

[MeldaProduction]

Don't worry, it's in the todo list for investigation. But you know, hard to say where it will lead us .

[dmbaer]

Perhaps a list (in parameter order) like this (mock-up hacked together from various plug-in existing windows):
>>> http://i.imgur.com/EfWcBZJ.png

And if you click on a 'Controller' its window will open automatically, so that you can edit the details.

I was actually suggesting something even simpler along the lines of this:

Code: Select all

Target               Modifier
--------             ----------
Wet/Dry              Multiparameter 1
Cutoff               Modulator 3

And then later, if appropriate:

Code: Select all

Slave                   MIDI Master
------                  --------------
Multiparameter 1        CC 1, Ch. 1