istnv
commented
2 years ago @pmaillot Your docs have been extremely helpful! Thank you! Internally, the module keeps track of fader position, not value. The float values from the console are the best source for this. The module has an increment/decrement fader by a 'tick'. Not every float translates, though. Early versions of the module, you bump up 5, then bump down 5, and not end up back where you started. Specially when crossing between slope boundaries. Internally the module generates an array equivalent of the float to db table from your docs. The bump up and down actions then walk this array. The only times the float conversions are actively used used is during a timed fade to keep the db variables updated.
pmaillot
(Note really an issue, but here goes...)
In the function below:
instance.prototype.pulse = function () { var self = this; self.sendOSC("/*s", []); .....
You could use S instead of s and receive a single OSC value rather than 3; This would certainly help in simplifying some of the functions, including fader level values that you would always receive (and send) in dB, avoiding the need for dB2float and float2dB.
Also glad to see the documentation I wrote has been useful :)
-Patrick-Gilles Maillot