What is the "automated value" modulation destination for global modulators?

[sag_the_great]

I can set the global modulation destination of MOD2 to the MOD1 automated value in MSF or MPowerSynth for example, but it doesn't seem ever to do anything. Does any one know what this destination actually does, if anything? Just curious.

[MeldaProduction]

The "automated value" is the actual value of the modulator, which you can record/play using the R/W buttons in the title, basically to record automation. Hypotetically you could control one using another modulator and set it to R state, in which case it will probably just duplicate the other, so it's probably not exactly useful

[sag_the_great]

Thanks for the reply. But I can't get the W button to work. If I create say Automated value MOD1 automation lane in cubase and draw in some data, then enabling the R button in MOD1 title bar does indeed work and follows my manually entered data. But I can't get the W button to do anything. If I enable W and wiggle any controls in the MOD1 dialog nothing ever happens, and no data seems to get recorded. What am, I doing wrong, or have I misunderstood what the W button does? Im on the lateest version of the plugins and have tried in MSF and MPowersynth. Can someone walk me through how to use this function?

[DarkStar]

Don't know the details in Cubase, but you would need to enable automation writing in Cubase itself. What the "W" is doing is sending the output value of the Modulator to the host.

Here I am recording Mod1's value in Reaper. Note the red W button in the track header, indicating "Write automation".



And, I do find it useful, especially when capturing automated values from a Follower or Envelope Modulator. Once captured I can edit the values and use them to automate some other parameter or plug-in.

And wiggling the controls in the Modulator is something different. Those controls are not exposed as plug-in parameters so their changing values cannot be captured in the host.

[sag_the_great]

Thank you, this is what I initially thought should be the case. BUT it definitely doesn't work in Cubase, tried with versions 13 and 14, with MSF, MPowersynth and with MFilter as per your example. Enabling W in both cubase track and MOD1 does nothing. Read however seems to work. So there is a problem with either Melda plugins or Cubase, can any one else confirm this? Im on the latest versdion of Melda. Thanks

[Held]

I can confirm that this doesn't work in Nuendo. If I enable write automation in Nuendo, it records manual parameter changes in MFilter, but it doesn't record the modulator output.

In REAPER it works for me as well, so it looks like some incompatibility with Cubase/Nuendo.

[sag_the_great]

Same in cubase. So may be a bug in Melda