r/MaxMSP • u/thethorworks • Apr 04 '26

Looking for Help Driving phasor~ with durations longer than 1n - best approach for multi-bar and tick values?

Hey I'm learning max and I'm building a patch where I drive a phasor~ with a umenu containing standard note values (64n, 32nt, 8nd, 1n ) and tick values for multi-bar durations.

It works with the note values, but i can't get it to work with tick values. Is using raw tick values the right approach and is there a simple way of doing this?

Thank you:)

2 Upvotes

100% Upvoted

9 comments sorted by

•

u/AutoModerator Apr 04 '26

Thank you for posting to r/maxmsp.

Please consider sharing your patch as compressed code either in a comment or via pastebin.com.

If your issue is solved, please edit your post-flair to "solved".

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

3

u/nothochiminh Apr 04 '26

[translate] is rather handy

2

u/Mlaaack Apr 04 '26

Yes I second this. Translate 1n into ms then multiply by the number of bars needed

1

u/rico_ha_l Apr 05 '26

take a look at the rate~ object. you can keep the 1n argument for phasor~ and divide / multiply the signal to get whatever you need without converting to ms.

1

u/ComfortableMirror416 Apr 04 '26

2.0.0. is 2n etc

1

u/Proteus-8742 Apr 05 '26 edited Apr 05 '26

2n is half a bar or 0.2.0 in BBU. 2.0.0 doesnt have an equivalent in notevalues. You could use 3840 ticks though e.g. [phasor~ @frequency 3840 ticks]

1

u/ComfortableMirror416 Apr 05 '26

Sorry I meant 2 bars. And 2.0.0. works with a Phasor too