Montross

Hello FYI I'm a complete beginner with Max MSP and I'm sure there is a very simple explanation for this, but after some time spent reading the manual and forum I am stumped

I made a very simple abstraction, but it doesn't pass signal at all (see attached patch)

The abstraction is only a send~/receive~ pair hooked up to an inlet and outlet. 

if you're wondering why Im trying this, its so I can play with feedback routing with BEAP modules. I want the single signal vector delay from send~/receive~ so that BEAP will allow a feedback routing. This works just fine without the abstraction, but for some reason once I save it as an abstraction it won't work

whynosound.maxpat

I  made a very simple abstraction, but it doesn't pass signal at all (see attached patch)

The abstraction is only a send~/receive~ pair hooked up to an inlet and outlet.   

if you're wondering why Im trying this, its so I can play with feedback routing with BEAP modules.   I want  the single signal vector delay from send~/receive~ so that BEAP will allow a feedback routing.   This works just fine without the abstraction, but for some reason once I save it as an abstraction it won't work

Hello FYI I'm a complete beginner with Max MSP and I'm sure there is a very simple explanation for this, but after some time spent reading ... 

abstraction-will-not-pass-signal

Apparently the issue is coming from the "#0" naming feature on send~ & receive~...

If I enter "send~ #0" the send will then appear with a unique name like "send~ 1031". That's the expected behavior and is what I want (so that if I use the abstraction multiple times in a patch, the routes stay separate), however no sound is passed in this case

However when I use a static name , e.g., "send~ osc01" it passes sound just fine?

Apparently the issue is coming from the "#0" naming feature on send~ & receive~...   

If I enter "send~ #0"  the send will then appear with a unique name like "send~ 1031".   That's the expected behavior and is what I want (so that if I use the abstraction multiple times in a patch, the routes stay separate), however no sound is passed in this case

You didn't post the abstraction patch, so really, we can't see what it's about.

Suggestion: select the abstraction code, Edit->Copy Compressed, then paste in your post.

You didn't post the abstraction patch, so really, we can't see what it's about.
Suggestion: select the abstraction code, Edit->Copy Compressed, then paste in your post.

send~ and receive~ must have a symbol as an argument. With just #0, you are giving an integer, and it doesn't work.

Instead, try something as simple as #0-connection (any word starting with #0). It will work.

But I think I know what your problem is:
send~ and receive~ must have a symbol as an argument. With just #0, you are giving an integer, and it doesn't work.
Instead, try something as simple as #0-connection (any word starting with #0). It will work.

Many thanks Jean-Francois! Yes, the second suggestion resolved the issue. I tried "Send~ #0---" and now it works as expected.

Many thanks Jean-Francois! Yes, the second suggestion resolved the issue.   I tried "Send~ #0---" and now it works as expected.

abstraction will not pass signal?