mpuckett at man104-1.ucsd.edu
Tue Mar 23 17:53:30 CET 2004
Oops, sounds like pd's 'native' atan2 simply has the inputs backward! I
have no idea what I was thinking doing that - perhaps I thought the
Max one was backward too. 'Traditionally' (since Fortran I think) atan2
has always been (y, x).
At this point, is it worse if I try to fix it or if I leave it alone???
On Tue, Mar 23, 2004 at 10:41:44AM +0100, Krzysztof Czaja wrote:
> hi marius,
> the internal [atan2] just takes its inputs as "x y" (or you can
> read them "real imaginary") -- a bit more naturally, perhaps, than
> the C function, which is atan2(y, x).
> Btw, there is a, `weird' as would IOhanness say, compatibility
> issue here too, bacause in max, [atan2] takes inputs as "y x".
> Same for sickles/atan2~... having Atan2 in hammer would clarify
> this incompatibility (although people tend to use cartopol rather
> than atan2?).
> marius schebella wrote:
> >I assume this is a known bug (or is it a feature), that the atan2-object
> >takes its arguments twisted. like [3 2( --> [atan2] is not the same as
> >what lovely source of error...
> PD-list mailing list
> PD-list at iem.at
More information about the Pd-list