REAPER host undo/redo not working

[Dandruff]

TX16Wx 2.0.1 + REAPER 4.31

-> load plugin and add a sample
-> tweak a knob in TX16Wx

Result: No undo point created in REAPER's undo history (FX parameter adjustment)

Expected: Uno point (FX parameter adjustment) created in REAPER's undo history (as is does for all other VST plugins here)


Why is this not working for TX16Wx?

[elcallio]

TX16Wx 2.0.1 + REAPER 4.31

-> load plugin and add a sample
-> tweak a knob in TX16Wx

Result: No undo point created in REAPER's undo history (FX parameter adjustment)

Expected: Uno point (FX parameter adjustment) created in REAPER's undo history (as is does for all other VST plugins here)


Why is this not working for TX16Wx?

I will try to explain this as simply as possible.
When you load a "simple" synth plugin into your DAW (in this case reaper), in most cases one knob will map to one "automation parameter". When you turn this knob in the simple VSTi, the plug in will send a "beginEdit param#" + "param#-><value>" + "endEdit param#" to the host. Now, this is the sequence that reaper captures and creates an undo point for.

TX16Wx however is by far a simple plug in. Since its a full blown sampler, with unlimited channels and unlimited groups, and thus unlimited permutations on a single parameter (i.e. "AEG attack" is not a singular aspect, but an attribute that might exist in any number of groups), parameters cannot map to a knob like it can in a single channel VSTi.

Automation in TX16Wx is done via mapping automation or external controllers through the modulation map, and likewise, undo is actually built into the plugin itself (undo/redo buttons). And lo, behold, the plugin can do undo/redo of stuff that is not possible through parameter edit record (standard reaper), so really, you should be very happy.

Also, feel free to read the manual which at least might give an idea on why controls cannot 1<->1 map to automation parameters.

Cheers (from Tokyo)

[Dandruff]

Alright, thanks!