I found some problems with Sumu's VST3 parameters.
The toggle parameters (envelope\to_zero, envelope\x_vel, gates\lopass
and output\clip) behave suboptimal and inconsistent compared to Sumu's
other two-state parameters (input\unison, pulses\sync, scope\mode,
oscillators\amfm). Instead of reporting two text-states to the host
("off" and "on" would be fitting in this case), they report a normalized
value as string and also behave like a continuous float parameter. This
is in contrast to the other mentioned two-state parameters which report
both states as string and behave like a stepped parameter with two
possible values. Fixing the toggle parameters would improve consistency
and general behaviour of these plugins (esp. when using host automation
or external controllers).
Another issue is that some parameters (pulses\rhythm and pulses\amp)
report weird symbols as value strings to the host. Those would be much
better to read if you were to use ASCII characters like "-" and "_" to
differentiate between pulse types for the rhythm parameters. Also, the
"x" character in the amp parameters is turning into some asian symbol
over here. This would improve readability when automating those
parameters or controlling them via external controllers.
Lastly, the readability of the pulses\shape parameters could be improved
by removing the "img" from the beginning of all these values. It feels
unnecessary to name those values all with "img" prefixed, so getting
rid of that would make it easier to quickly see what shape the current
parameter value is.
I found some problems with Sumu's VST3 parameters.
The toggle parameters (envelope\to_zero, envelope\x_vel, gates\lopass and output\clip) behave suboptimal and inconsistent compared to Sumu's other two-state parameters (input\unison, pulses\sync, scope\mode, oscillators\amfm). Instead of reporting two text-states to the host ("off" and "on" would be fitting in this case), they report a normalized value as string and also behave like a continuous float parameter. This is in contrast to the other mentioned two-state parameters which report both states as string and behave like a stepped parameter with two possible values. Fixing the toggle parameters would improve consistency and general behaviour of these plugins (esp. when using host automation or external controllers).
Another issue is that some parameters (pulses\rhythm and pulses\amp) report weird symbols as value strings to the host. Those would be much better to read if you were to use ASCII characters like "-" and "_" to differentiate between pulse types for the rhythm parameters. Also, the "x" character in the amp parameters is turning into some asian symbol over here. This would improve readability when automating those parameters or controlling them via external controllers.
Lastly, the readability of the pulses\shape parameters could be improved by removing the "img" from the beginning of all these values. It feels unnecessary to name those values all with "img" prefixed, so getting rid of that would make it easier to quickly see what shape the current parameter value is.
I've used Sumu 1.0.0b20 VST3 with Reaper 7.25.