You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
as such, you should never use float or double of any numbers that communicate with Pd, as this will guarantee to break once Pd changes it's internal number representation to double precision.
instead, always use t_float for numbers and t_sample for signals.
The text was updated successfully, but these errors were encountered:
BTW, thanks for your last PR, it seems to solve most parts of the problem.
I still need to figure out a way to deal with the .w_float needed to access the actual array values, though. I'll test your patch but I bet it will need a few more tweaks to get the object back working (and maybe some modifications to jl.cpp.lib, too).
Pd is (slowly) moving towards double-precision.
as such, you should never use
float
ordouble
of any numbers that communicate with Pd, as this will guarantee to break once Pd changes it's internal number representation to double precision.instead, always use
t_float
for numbers andt_sample
for signals.The text was updated successfully, but these errors were encountered: