Tips using R S nodes on a boygroup

i’m using 40beta23 for some boygrouping and experience issues using S R nodes on the boygrouped machines.

on the server I have a few different values going into a few different S nodes. I then boygroup the S node. Then in other patches I’m using a number of boygrouped R nodes but experiencing issues with them receiving the correct S.

Any tips to ensure the R receives the correct S?

thanks

for sure you know it already:

the SendString enumeration of any R-node has to be changed at least one time to create it’s description in the XML.

my workaround:
*i create the S-node (default SendString “devnul”
*i duplicate the S-node and set the SendString
*i create the R-node and select the appropriate SendString.
*save

i assume that in some of your cases you created an R-node, looked at the Sendstring, but didn’t change it because the correct enumeration was already selected.

in this case vvvv only saves

xml:
   <NODE nodename="R (Value)" componentmode="Hidden" id="2">
   <BOUNDS type="Node" left="4560" top="4590" width="0" height="0">
   </BOUNDS>
   </NODE>

only once modified the pin is created.

xml:
   <NODE nodename="R (Value)" componentmode="Hidden" id="2">
   <BOUNDS type="Node" left="4560" top="4590" width="0" height="0">
   </BOUNDS>
   <PIN pinname="ReceiveString" slicecount="1" values="zzzz">
   </PIN>
   </NODE>

great, thanks loads kalle. sounds like that will solve the issue. Explains why sometime it seemed some R’s constantly received the correct S’s and other times not. Must have got luckly and selected the receive on the ones that worked.

So I’m guessing this is a bug devs?

it’s more the concept behind vvvv than a bug. when you know that pins in the XML are only created if you alter their value from the default value this behaviour is quite logical.

but the helppatches of all S/R nodes should point to that issue…