Forums > MaxMSP

Issues with subpatches/ abstractions in 5

June 20, 2008 | 3:37 pm

Hey, has anyone else encountered these problems/know of a solution?

I’m running Max 5 on a mac with OS 10.4.11

While trying to use abstractions I’ve created I’m having a lot of problems with "identifiers" You know those things like #1, or #0 to make multiple instances of an abstraction unique. Well I kept getting the message that, when using #0 Record~ or Groove~ could not find buffer~. similar problem when I use #1 to identify. If anyone knows a solution to this, let me know. Also I’ve had trouble finding help with Identifiers in the documentation, anyone know where that is? Thanks in advance for your help.

- Kevin


June 20, 2008 | 3:50 pm

I know this is a stupid question, but you did make a buffer~ that has the same #name as the record~ and groove~, didn’t you?

-C


June 20, 2008 | 4:03 pm

As I understand it, it should work correctly if I set it up so I have "buffer #0" "record #0" and "groove #0" they should all be assigned a number within the patcher. What I see graphically in my patch confirms this, when I load it up I see "buffer 1105" "record 1105" and "groove 1105". Same thing applies with #1, if I type in the argument "a" I look and see "buffer a" "groove a" and "record a". If theres something incorrect about that let me know.

- Kevin


June 20, 2008 | 4:25 pm

I can’t tell whether this might be related to your problem, but when used as a buffer~ argument, #0 needs to begin a symbol, such as #0foo, which results in 1183foo when a patch is loaded as an abstraction. The name argument to buffer~ must be a symbol; it can’t be a number, even though you can use #0 by itself in Max 5 — a somewhat strange and pointless feature I suppose.

If you can make an example that demonstrates the difficulties you’re having everyone will be very interested to see it.

David Z.


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