New Patcher argument behavior?

Mar 2, 2011 at 9:11pm

New Patcher argument behavior?

For some reason, I am surprised by how patcher arguments work for me right now. Everything works as expected in a ‘proper’ abstraction that i have saved in max’s path. but if i encapsulate something the topmost patcher arguments apply. i remember the difference being that #1 in an encapsulation would be the patcher name but after that arguments were ‘normal’

I am using Max 5.1.8 44740

#55284
Mar 3, 2011 at 4:17am

does the radio silence mean it is just me?

#198956
Mar 3, 2011 at 5:16am

It just works this way. You can use the patcherargs objects, though.

#198957

You must be logged in to reply to this topic.