Forums > MaxMSP

argument with a #0 question

July 8, 2008 | 3:19 pm

hi there !!!!!

this has been mentioned before , but I just need some clarification !!

using mutilple instances of the same Bpatcher , consisting of a simple triggerd groove object with it’s corresponding buffer.

so far so good

now I have named the buffers using the "#0_buffername" rule so each buffers have there unique generated assigned adress , ( to avoid the same buffer been played in all 6 instances of my bpatcher.)

Now my question ! , will the groove object buffer name also follow with the proper generated #0 ?? I just can not seem to get the groove object buffer name , to be the same as it’s corresponding buffer .

How would I come about that ???

thanks !


July 8, 2008 | 3:53 pm

if i’m not mistaken #0 will generate a random number. in the past i have used #1 which then gets defined by an argument which has to be sent to the bpatcher (or via the args field in the inspector).

this worked for me…

hth,

j


July 9, 2008 | 7:59 am

sebastian schrieb:
> Now my question ! , will the groove object buffer name also follow
> with the proper generated #0 ?? I just can not seem to get the groove
> object buffer name , to be the same as it’s corresponding buffer .
>
> How would I come about that ???

if the groove~ is in the same (b)patcher as the buffer~ and you assign a
#0_MyBuffername to both of them, they share the same name…

All #0_whatever, #0_another, will share the same preceding number if
they are in the same patcher. Just try and look yourself. You can find
out these questions easily if you ask Max, no list necessary… ;-)

Stefan


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


July 9, 2008 | 8:33 am

Ok guys !!!! thanks for that

will go ahead and test this right now !!!!!


Viewing 4 posts - 1 through 4 (of 4 total)