Replacing [buffer~] with [dropfile] causes error but works fine.

Nov 20, 2009 at 12:07pm

Replacing [buffer~] with [dropfile] causes error but works fine.

In the patch I posted below. I’m replacing a [buffer~] with the patch coming out of dropfile, and i get an error message in the Max window while the replacing of the buffer works fine.
The error says at object: “buffer~”, at message: “s: can’t open”.

You’ll see in my patch the way the path from dropfile goes to buffer is not the most straightforward way but this is the way it has to be in the orignal patch were this system comes from.

It is a very simple patch (I isolated the problem). Maybe you can have a quick look if I’m doing something wrong, or maybe tell me a better way to route the path from the [receive] object to the [buffer~].

– Pasted Max Patch, click to expand. –
Nov 20, 2009 at 12:15pm

The pak object (pronounced pock) should be replace by it’s big brother pack. The s that can’t be opened is the first item in the list that is sent whenever the second inlet is triggered.

Nov 22, 2009 at 10:26pm

Thank you.


You must be logged in to reply to this topic.