Ndef with Pbind ordering question

Questions
1

Is this the expected behaviour?

(
Ndef(\test,
	Pbind()).play(vol: 0.2);
)

NODE TREE Group 0
   1 group
      1982 group
         1987 default
      1983 group
         1984 system_link_audio_1
         1985 system_link_audio_1


(
Ndef(\test2,
	Pbind()).play(addAction: \addToHead, vol: 0.2);
)

NODE TREE Group 0
   1 group
      2003 group
         2004 system_link_audio_1
         2005 system_link_audio_1
      2002 group
         2007 default

i.e. add action applies only to the link? I know it may not matter in most cases, but I found an edge case where it causes an issue.

2

I’m not 100% sure (I haven’t used this feature myself) but the help for BusPlug:play says “addAction: Where in the node tree to play the monitor synths” so I believe it’s intentional.

hjh

3

Yeah, the problem is the location of the source synths, which seem impossible to order. My weird case involves one Ndef reading from a bus that multiple other sources write to. If the reading happens at the wrong place in the order, some sources may overwrite data from last block before it is read.

Exotic I know…

4

I’d probably just take the Ndef groups and manually order them.

hjh

5

If you need to order several Ndef groups relative to each other, you can use the message orderNodes(a, b, c, ...).

1 Like
6

Perfect! Thanks @Julian