MXXX MultiParameter issues

[Tagirijus]

Hi Vojtech,

I am making some presets right now and I try to give best information about the controlls I set up. Unfortunately it seems that the information about the MultiParameters are not saved correctly. At the moment the fields are blank even if I saved something before. Sometimes the MultiParameter contain information about the preset which was loaded before (or saved before?). I am still trying to reproduce the bug exactly. For now I can just say that all the information I already wrote is gone.


By the way: is there another place in which these information will be showed up in the future?

[MeldaProduction]

Hi Tagirijus,

damn, you are right! The information shall be fixed! It is currently not visible anywhere, but it might be used when user clicks F1 over a control in easy screen, which MPS doesn't have though...

[Tagirijus]

Wow. I did not know that the information appears like the help text - what a great idea! Thanks for the hint and thanks for the upcoming fix.

[MeldaProduction]

Don't thank me just yet, but I'm pretty sure this will be manageable!

[Tagirijus]

Hehe, I am sure you will fix it.

[Tagirijus]

I changed the title a bit so that it fits better and I have not to open another topic.

(A) Multiparameter controlling other Parameters
1. Set up M1 which controls something within a range (maybe lowpass from 50-100 Hz)
2. Set up M2 which controls the max. value inside M1 (maybe from 100Hz to 200Hz)
3. Change M1 to 100%: lowpass is 100 maybe
4. Change M2 to 100%: lowpass is still 100 - you have to tweak M1 so that it "updates"

This also happens in other plugins and most important: I would not call it a real bug of course! I understand the logic behind it. I am just wondering if there could be improvements in the future regarding this technique? Or maybe it already works somehow, but I am doing something wrong?

(B) Multiparameter reorder
1. Make the same as in (A)
2. Reorder M1 to M4 maybe: M2 is now M1 and is not controlling the max value of M4, but of itself instead.

I would call this some kind of bug, am I right? Like it is now the MPs seem to be linked to the ID, which refers to the position. Maybe every MP should have a unique ID so that reordering updates the links between the MPs ?

(C) Too many Multiparameters
I have a preset in MXXX in which I use all 16 MPs. Unfortunately on my resolution (1440x900) the MXXX window is rather big (set to 100%). I attached a picture in which you can see that the last controls are not really visible anymore:

mxxx_size.jpg

If I set all to 90% size I can see them again.

My questions now regarding (C):
- Will it be possible to close the active-ppresets-search/tag-engine to have more space for the MPs?
- Is this hidden MP thing because of the demo restriction (where you cannot resize the tool at all)?


Thanks for your help!

[MeldaProduction]

Ok so:

A) Well, that's how it is I'm afraid. Whether it should update the attached parameters or not is rather a grey area and it would actually be a little problematic to implement, so I'd like to keep it this way .

B) Yeah well, the multiparameters are just indexed. Think of each parameter are automation lane in your host - if you reorder them, they will just point to a different parameter. Basically in these situations you simply need to be careful and think ahead. I know it can be a little problematic, but it's a rare situation and fixing would be very very problematic...

C) Oh, well, you officially created the biggest GUI! I like that! Ok, so this definitely should be solved anyway... added to to-do list.

[Tagirijus]

A) Well, that's how it is I'm afraid. Whether it should update the attached parameters or not is rather a grey area and it would actually be a little problematic to implement, so I'd like to keep it this way .

No problem for me. I just wrote it into the information of one MXXX preset that the one MP has to be re-tweaked then. I hope such a thing is okay ...
(for me it would be, hehe)

B) Yeah well, the multiparameters are just indexed. Think of each parameter are automation lane in your host - if you reorder them, they will just point to a different parameter. Basically in these situations you simply need to be careful and think ahead. I know it can be a little problematic, but it's a rare situation and fixing would be very very problematic...

Oh, I see the problem. Again: no real problem for me. "Thinking ahead" is beter, indeed.

C) Oh, well, you officially created the biggest GUI! I like that! Ok, so this definitely should be solved anyway... added to to-do list.

Nice to hear and thanks for takign a look at!

[dmbaer]

Oh, well, you officially created the biggest GUI! I like that!

Actually, no. I had a few presets that exhibited the same problem of not everything appearing on the non-Edit screen. I solved the problem by reducing the number of categories, which reduced crowding and allowed everything to be visible. But what got sacrificed was clarity. The larger number of categories with appropriate descriptions can make the intent of the controls a lot more intuitive. I was almost considering suggesting that a mechanism to collapse the top preset menu area be added.

[Tagirijus]

I found another bug, but it's not that bad: if you name a multiparameter and save the preset without assigning things to this mp, the name of the mp will not be saved.

[MeldaProduction]

It's not a bug, but an optimization . Basically, if you have a multiparameter or modulator which isn't attached to anything, it's useless, so it is not save, to save space. You'd be surprised how much data the plugin needs to store the settings... I envy the rest of the market having a few dozens parameters and that's all...

[Tagirijus]

Oh I see. Thanks for the info. Luckily it's not bad after all of course.

[Tagirijus]

I think I found more bugs ... or again: misunderstood features?

1. Let MP1 control at least 5 other values in the effects section.
2. Let MP2 control the range of parameter >4 (5 for example) inside the MP1 with the learn feature.

(A) Nothing happens afterwards. You also cannot chose the parameter 1 or parameters above 4.

(B) The parameters inside MP2 (if you can chose them) do not have the correct value caption. Instead it just says 0% - 100%. But if it controls a frequency for example it does NOT say 0Hz or 14.0Hz.

[MeldaProduction]

Since there is potentially unlimited number of parameters you can control, there's a limit to those you can control the limits - to 4 . And (B) is that way correct too, it's more like a technical problem really (potential deadlocks & cycles...).

[Tagirijus]

I nearly knew it, hehe. Nevertheless: why does the controlable parameter inside a MP starts by 2? Either I made a mistake during my tests, or it is true and you cannot control parameter 1, but 2. Is this for purpose?