Syncing parameters across modules is kinda difficult

[AlvanMerri]

Hello,

Just wanted to post about an user experience issue that's been bothering me for a bit

This mainly comes from parameters related to time: syncing them can be quite difficult when it's across different modules.
I wax trying to create a one shot ADSR (I wish this was an option for this module) which wouldn't take into account sustain and simply play Attack+Decay+Release over their respective lengths regardless of how long the note was held. Well I couldn't bother with Attack so I was just using a note length modifier to fix the note length to the Decay time.
Unfortunately these parameters aren't linear. I assume they use the same function for knob position to value, but since their limits are different (40 sec for Decay time, 2 sec for Min Length in note modifier), they do not yield the same values for the same (relative) knob position, and I have to resort to a rather approximate curve via a modulation mapper to sync them

If it were possible to edit in-module the behaviour of knobs, like position-to-value functions as bezier curves, min-max values, etc, this would make syncing their behavior easier I feel, without needing approximate [constant modulator]-[modulation mapper] setups. although I can imagine this would involve a lot of work to implement.
I also have to wonder why the note length modifier's max values are so low, especially with the note on upon not off event generator being dynamic in its max value (This module is linear in its knob-to-value function though, so syncing it also requires modulation mapping)

A more extreme example is me trying to match a note stutterer's frequency to an event delay's delay time, to have a note played randomly but on average every x sec. Since those quantities are inverses this is really complicated to approximate with a bezier curve.

What I want to say is, there is a disparity in the behaviour of various time-related parameters across modules (ADSR, resonator, note length modifier, audio enveloppe follower, event delay, mono echo, and to an extent LFO and note stutterer), which is understandably necessary for the user experience of each individual module (though I still wonder why note length modifier and audio enveloppe follower's max values are so low), but becomes frustrating to work around when trying to get them to work together.

[tiger001]

i refer to the implementation of this value(s) from EMU perspective

in their proteus 2000 and command station series, you dial clockwise value in the realms of (e.g.) 0-100, where 100 is the maximum, but when you go counterclockwise, below zero you can dial in musical values that refer to MIDI clock (e.g.) 1/8, 1/32th etc etc ; which are much more consistent values, which result in much more predictable results

[MuTools]

Just wanted to post about an user experience issue that's been bothering me for a bit
This mainly comes from parameters related to time: syncing them can be quite difficult when it's across different modules.
...
What I want to say is, there is a disparity in the behaviour of various time-related parameters across modules (ADSR, resonator, note length modifier, audio enveloppe follower, event delay, mono echo, and to an extent LFO and note stutterer), which is understandably necessary for the user experience of each individual module (though I still wonder why note length modifier and audio enveloppe follower's max values are so low), but becomes frustrating to work around when trying to get them to work together.

Thanks for your feedback. Unfortunately i don't have an immediate solution for that, except, as you know, using Modulation Mappers. I'll reflect on it with an eye on future developments.

About a "one shot" decay-release: You can use a Multi-Point Envelope for that.

[AlvanMerri]

Thanks for your consideration.

I did think about multi-point enveloppes, they're among my alternatives, but also are less direct to work with (sometimes you just want "one knob"), and not yet properly integrated into front panels, so it's kind of a trade-off yet.

On another note, are you able to share the formula for mulab's bezier curves?
I would have an easier time interpolating if I could plot both the knob's position-to value function and the bezier curve in say, desmos, and tweak parameters here.

[MuTools]

I did think about multi-point enveloppes, they're among my alternatives, but also are less direct to work with (sometimes you just want "one knob"), and not yet properly integrated into front panels, so it's kind of a trade-off yet.

I understand your points.
It's on the wishlist to add kind of meta-parameters to the MPE that can change the time and level of specific points. When that's implemented then these MPE meta-parameters can also be put on a front panel, just like any other module parameter.

On another note, are you able to share the formula for mulab's bezier curves?
I would have an easier time interpolating if I could plot both the knob's position-to value function and the bezier curve in say, desmos, and tweak parameters here.

It are rational quadratic beziers.
For example see https://demofox.org/bezquadrational.html