Richard Waltman

In 2020, is there an accepted way to handle precision floats coming from Node for Max?

"0.000012979321998580815 0.000015883354135707453 0.000014019014122368587 0.000020023423132229268"

Convert output to List of floats(pack/unpack) or jitter matrix

fromsymbol() and sprintf() objects seem to round this pretty hard, or maybe I'm not doing this correctly. Any help would be appreciated on this matter.

In 2020, is there an accepted way to handle precision floats coming from Node for Max?

Output Example:
"0.000012979321998580815 0.000015883354135707453 0.000014019014122368587 0.000020023423132229268"

Expected:
Convert output to List of floats(pack/unpack) or jitter matrix

fromsymbol() and sprintf() objects seem to round this pretty hard, or maybe I'm not doing this correctly. Any help would be appreciated on this matter.

In 2020, is there an accepted way to handle precision floats coming from Node for Max?

Output Example:
"0.000012979321998580815 0.000015883

handle-doubles-coming-from-node-for-max

https://cycling74.com/forums/increase-floating-point-accuracy-tiny-input

https://cycling74.com/forums/max-and-floating-numbers/

Here is the solution to my problem for posterity (fromsymbol -> unpack f f f f -> flonum):

Indeed, flonum does the trick.

Here is the solution to my problem for posterity (fromsymbol -> unpack f f f f -> flonum):



Handle precision floats coming from Node for Max?