Metro in Hertz (what does work and what does not?...)
Oct 03 2016 | 1:52 pm
Dear Max users,
I have been using Max for sometime but I am still a rookie so sorry my ignorance on this eventual non-problem.
I have been using metro in Hz because of a convenient approach of my way of thinking time to control events. I have been using the following form: [metro 256 hz] (note: the number is only an example).
I discovered that the following forms [metro 256hz] and [metro 256Hz] (without a space between the number and the Hz expression) also work. However they do not "count/tick" at same speed... does anybody ever arrived to this "issue". Can anyone explain why both work and why they do not "count/tick" at the same speed? I searched the forum but I did not find a discussion on this specific theme.
Thanks in advance.
Findest regards,
Horácio
- Oct 03 2016 | 2:22 pmMax doesn't understand [metro 256Hz] and will by default tick at a 5ms period. If you check metro's reference, you'll read that you should anyway use the interval attribute (I don't know why…). So [metro @interval 256 hz] is the correct syntax (hz and not Hz).If you attach an attrui object to your metro, you'll see its real interval setting.
- Oct 04 2016 | 8:48 amDear Patrick,thanks so much for the prompt answer and advice.Best,Horácio
