Buffers inside poly patcher

ulodin's icon

Hi guys,
i know there are tons of topics about this out there; even i red all of them, Max still makes me crazy. Straight to the problem:

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

MAIN PATCH:

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

SUB PATCH:

Turning on the DSP, the Max window tells me that record~ and groove~ don't recognize any buffer~; where do i wrong?!

Thanks in advance, cheers!

Floating Point's icon
Max Patch
Copy patch and select New From Clipboard in Max.

I can't really explain why your approach doesn't work, but this way should (haven't tested it):

ulodin's icon

Hi Terry, you have not to test it, it works! :)
Your approach seems the ones i've seen here around in the past using [sprintf], by the way it's sad that the simple way suggested by Max tutorial itself can't work...

Thanks again!

ulodin's icon

A problem seems to remain: obviously every time an instance works, it passes from busy to mute by its relative thispoly~ object. Due to this, every time thispoly~ throws out messages, it initializes its buffer, groove and record with different names. The result seems to be that only the first instance do the job.

Just to be clear: the goal of my patch is to have a x-number of simultaneous buffer/record/groove that record/playback the same audio source at different times; their playback material must overrides themselves, here is the why i want to use a poly~ patch.

----

Doing this without using a poly~ approach is not that difficult: i could design a given number of copies of buffer/record and playback them in one single patch; but i'd want to learn to do this through a poly~ approach!! :)

ulodin's icon
Max Patch
Copy patch and select New From Clipboard in Max.

Yup, this one seems to allow interaction between thispoly~ and buffer/record/groove only once, at the loading, and never more...isn't it?

Floating Point's icon
Max Patch
Copy patch and select New From Clipboard in Max.

ok sorry for leading you up the garden path-- i now remember there is an idiosyncratic thing about variable arguments in poly~, you need to have #0 immediately followed by a symbol, such as #0foo, otherwise it won't 'bind' to the argument name.
so try it like this:

another thing is that even if you have two copies of thispoly and bang one, the other one will also output-- very annoying!
apologies again--
T

ulodin's icon

Hi Terry, no problem! Anyway, thanks to this entire topic, i'm more efficient using poly~ patches! :)