@frequency

ward de jager's icon

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


Max Patch
Copy patch and select New From Clipboard in Max.

ward de jager's icon

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

Jean-Francois Charles's icon

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.

Roman Thilenius's icon


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?

Roman Thilenius's icon


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

Jean-Francois Charles's icon

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

ward de jager's icon

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

Roman Thilenius's icon


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. (?)

attributes