Group2 on Server Boot

Community
1

Hello,

seems there is a Group 2 created along with the Default Group when booting the server on SC 3.14.1. Cmd period removes it. Wondering what creates it!

2

It comes from Volume:

Volume {
	... vars omitted...
	*new { | server, startBus = 0, numChannels, min = -90, max = 6, persist = false |
		^super.newCopyArgs(server ?? { Server.default }, startBus, numChannels, min, max, persist).init;
	}

	init {
		// hardcode group nodeID to 2, so multiple clients can use it
		group = Group.basicNew(server, 2);
		... snip
	}
}

I think I see the point, though – all clients playing stuff on this server should go through the same main volume control.

There is a redundancy in that group 2 is created upon server boot, and then it’s created again when setting the volume to non-zero dB.

s.volume = -10;

[ 21, 2, 1, 0 ]
[ 9, "volumeAmpControl2", 3, 1, 2, "volumeAmp", 0.316228, "volumeLag", 0.1, "bus", 0 ]

At g_new, 2, 1, 0, shouldn’t it complain about a duplicate node ID? I’m guessing this was added as a workaround for group 2 disappearing on cmd-. (when ServerTree would be a better solution).

hjh