Sofian Audry
Sofian Audry
Currently the pq_trig8.h is used to compute quickly sin(x) in Plaquette, however this approach is much less precise than the 24-bits resolution of floats. Could we improve precision without hampering...
It would make sense to have a common API for timing units such as Alarm, Chronometer and Metro and oscillators such as TriOsc and SineOsc. In particular functions such as:...
It could be interesting to introduce some user-friendly sources and possibly filters for random processes. Some ideas include: * a source similar to Metro but that would generate random pulses...
See this discussion: https://chat.openai.com/c/f3b632b9-744f-4372-8953-4ba92f46e315 The P2 algorithm was suggested: https://www.cse.wustl.edu/~jain/papers/ftp/psqr.pdf Code: https://github.com/FooBarWidget/p2/blob/master/p2.cpp Also: https://scikit-learn.org/stable/modules/generated/sklearn.preprocessing.RobustScaler.html
It is confusing to have both -- and Timer functionality is better handled by Ramp.
Currently we are forced to declare each Plaquette object individually, therefore preventing us from using the power of arrays. For example, imagine I would like to control 10 LEDs individually...
min, max, abs, constrain, round and sq are all defined as macros in Arduino which is shitty for a number of reasons. Consider undefining them (```#undef```) and redefining them as...
There is only another class that derives from Unit (Chronometer) and it would be totally fine that every Plaquette object would need to abide by Node's API.
cf. PqCore.cpp:48-51 If I create a unit during of after call to PlaquetteEnv::begin() the unit's begin() function will never be called. - Could be fixed by using a boolean in...
I find the mode INTERNAL_PULLUP is a bit confusing: - for Arduino users it is confusing cause it is very similar to Arduino's INPUT_PULLUP - for non-Arduino users/beginners it is...