I could not reproduce the issue of the gain value not registering.Please upload a screenshot or a short video. ^^ The issue needs to be reproducible in order to be resolved.
Could there possibly be a function to do a negative tether on values? For instance: morph A = 0.1 then morph B is automatically = 0.9, if morph A changes to = 0.2, then morph B automatically changes to = 0.8 and so on.14mhz updated MultiCurveMapper with a new update entry:
MultiCurveMapper v0.3 20260528
Read the rest of this update entry...
1. Thanks! I'll try that when I have a chance.김영오님?
1. about negative tether on values
The calculation formula of the filter is very simple.
The negative tether you mentioned can be implemented as follows: By setting shift = -1 and gain = -1,C#:val += shift; val *= gains;
2. As you said,,, so that you could draw segments and then have the plugin choose random segments to play ...C#:(0.1 - 1) * -1 = 0.9 (0.2 - 1) * -1 = 0.8
I don’t quite understand what you mean. Could you please explain it a bit more?
hi 14mhz,The random playback feature is not currently supported.
That sounds great!Hello, @FantasiWrapper
In the upcoming version, this will be implemented with the following considerations:
(1) Random playback is executed according to tab-level invocation.
(2) If the chosen graph is empty or identical to the last one, another will be selected.
(3) If the randomly chosen graph has a loop property, it will keep playing until the next random selection.
Are there further aspects to take into account?![]()
Hi, Back again. Summer always busier. Sorry for delay in replying.That’s how it works. Would you like to take a look?
A point we need to consider together :
If Expression A is playing randomly and then switches to Expression B, the morph values of Expression A remain without being reset. When Expression A is randomly selected again, the difference between the starting value and the previously interrupted value causes the morph to jump erratically.
Of course, a solution is possible, but since the purpose of this plugin is simple mapping, handling it within the plugin would go beyond its intended scope and end up turning into spaghetti code.![]()
Perfecto!!! Exactly what i wanted!Perhaps what you want is the Start Random (Continuous) feature — is that correct?