I have been getting the repeated error message " multiply defined" when I use multiple sends with the same name. When I remove them, the error message disappears.
However, I was reading in the documentation that you can have as many send and receive objects with the same name as you want.
Can anyone clear this up?
-
Multiple sends: problem/no problem?
-
Hi George
This is my first post on this forum, so please don`t be to angry if I am wrong.
If you use the [send] and [receive] objects, you could have as much objects with the same name as you want.
But if you use the [send~] and [receive~] objects for signals, you could have as many [receive~] with the same name, but only one unique [send~] object. If you have more than one [send~] with the same name, there is an error.
-
That may be right. Still, when I had the problem, I wasn't using send~. But I'll check it out. Thanks.
-
what dertatsch said is indeed correct:
-
Why is it an error though? It seems very useful to me to route your final sound from various subpatches to your [dac~] using sends, rather than patch cables.
Like:
[s~ output] [s~ output] [s~ output] [s~ output]
[r output]
|
[dac~]If you use patch cables it looks really messy
-
@Faranta Best to use........
[throw~ output] [throw~ output] [throw~ output] [throw~ output]
[catch~ output]
|
|[dac~]Made specially for this purpose....... many to one.
[throw~] and [catch~] have the added bonus that you can set (and so change..!) their addresses too....... with a [set whatever( message.[send~] and [receive~] are only for one to many.
David.