ward de jager

Why is the frequency of the phasor going up instead of down when using @frequency $1 , @frequency as attribute message ?

1.jpg

number

message

gain~

ezdac~

phasor~

Why is the frequency of the phasor going up  instead of down when using @frequency $1 , @frequency as attribute message ?

frequency

@ myself , because in that case frequency is expresseed as milliseconds :)

You have to tell Max that you want to use Hz as unit for frequency: your message can be 'frequency $1 hz'.

Who had the incredible idea of using ms as default unit for frequency?

Maybe we need a 'period' message, with kHz as default unit.

You have to tell Max that you want to use Hz as unit for frequency: your message can be 'frequency $1 hz'.
Who had the incredible idea of using ms as default unit for frequency?
Maybe we need a 'period' message, with kHz as default unit.

this fits perfectly into my current "ignore everything beyond max v4" campaign.

default of phasor is Hz - just not for the @frequency attribute.

why use symbols when you can use numbers? because it is more modern? 


 this fits perfectly into my current "ignore everything beyond max v4" campaign.

default of phasor is Hz - just not for the @frequency attribute.

[phasor~  50.]

 why use symbols when you can use numbers? because it is more modern? 


or use 31.6227766017 , then it doesnt matter if hz or ms. facepalm.


or use  31.6227766017 ,  then it doesnt matter if hz or ms. facepalm.


As we say in French: "Pourquoi faire simple quand on peut faire compliqué ?"

I know sliders , numboxes are easier and more straight forward . 

I just wanted to get the hang of the @ message

I know sliders , numboxes are easier and  more straight forward . 
I just wanted to get the hang of the @ message 

in case he expected that the @ has the same default like the object i can somehow understand that.

but i believe (i dont have not much own experience with it) is that the right advice is to 

generally not use no unit description at all

for example if you enter "50" into [attrui], it will automatically change to "50. ms" and does not allow to only send a number.

so eventually it is even wrong to call the "ms" the "default unit" of this attribute - it is just the first in the list. (?)

grafik.png


in case he expected that the @ has the same default like the object i can somehow understand that.

but i believe (i dont have not much own experience with it) is that the right advice is to generally not use no unit description at all with objects which support those.

for example if you enter "50" into [attrui], it will automatically change to "50. ms" and does not allow to only send a number.

so eventually it is even wrong to call the "ms"  the "default unit" of this attribute - it is just the first in the list. (?)
