Matrix Modulation System - Last Call for bugs fixes & changes!!

[Christoph Hart]

Well it shouldn’t be a straight accumulation (aka addition) because a positive value can compensate a negative one perfectly, drawing no arc at all, while the modulation actually moves following the combined value

The range display covers the min max value while the modulation value combines it.

If you have two modulators, one set to -25% intensity, the other to 25% intensity (both in unipolar mode), and the value is at 50% position, then the modulation range will cover 25% to 75%. If both modulators crank out 1.0 as mod value, then the modulation value will sit right in the middle where the value is supposed to be.

That being said there might be a few edge cases and combination of modes & intensity where the math doesn't math, but in general that should already be the case.

[DanH]

@Christoph-Hart look forward to testing asap :) Thank you!

[Christoph Hart]

@DanH It's pushed now.

You can just load the exlusive mod snippet posted above, the changes should apply without modifications (I assume nobody is using this feature in a product yet so I don't care about backwards compatibility).

[DanH]

@Christoph-Hart working well so far but there is one issue:

The draggers are obviously drawn at the top z level.

This means that if you switch your 'main' panel (like FX / ARP / MAIN or whatever you've designed) the draggers remain on top of whatever the new panel is, even if the ui control is hidden, but it's parent panel isn't. The draggers seems tied to their panels - is that correct?

So I guess we have to hide the panels that our ui controls are in, and if, like I've recently done, you've moved all your main UI controls into one 'base' panel, you need to put them (back) into other panels in order to hide the draggers too.

Not the end of the world for me by any means but thought I would flag it up.

[Christoph Hart]

@DanH not sure what you mean, the draggers are just like any other component, no?

[DanH]

@Christoph-Hart actually it could because the offending ui controls aren't in a panel at all. Trying to test my theory but moving a panel up the component tree is causing instant crash in this project : /

[DanH]

@Christoph-Hart ah yes ok - so if your component isn't in a panel at all the the dragger remains on top of any other ui component i.e visible at all times (when that source is selected). Will DM you a video

[DanH]

@Christoph-Hart Is there a way to make the source select buttons behave more like a radio group? At the moment if you click an already selected button it deselects it and hides the draggers.

[Christoph Hart]

@DanH yes that's intended, otherwise you will never get back the behaviour of showing the accumulated mod value. How would you do this instead?

[DanH]

@Christoph-Hart ah yeah I see. This might be a me problem / ui design problem (for me).

My source select buttons show the selected modulator's controls and a little border around the selected button to show which one is selected. That doesn't change when clicking the source select button again (good) but I guess I need a way of communicating what the mod system is showing in terms of why the mod ranges change, and probably another button element to display it's state.

I'm not 100% sure that other devs show the accumulated mod range.... actually some do, some don't, but not either / or, they display it on top of the current mod range.

[DanH]

If we could get a delete button in the Mod Matrix itself for each row that would be super useful!

[Christoph Hart]

@DanH said in Matrix Modulation System - Last Call for bugs fixes & changes!!:

I'm not 100% sure that other devs show the accumulated mod range.... actually some do, some don't, but not either / or, they display it on top of the current mod range.

I'm pretty sure that's the case, otherwise you end up with invisible modulation that is super annoying.