awesome, thanks for that... its got me going ....
but theres a definitely a bug somewhere 🙂
the above works because its not setting
s.options.maxLogins = 4
this actually is wrong, and actually leads an error on connection, we see the following error
Requested notification messages from server 'belaServer'
belaServer: no maxLogins info from server process.
belaServer: setting clientID to 1, as obtained from server process.
WARNING: Server belaServer couldn't set clientID to 1 - outside of allowed server.maxNumClients range of 0 - 0. clientID is still 0.
see that WARNING, it sets to clientID 0
this leads to everything being created in the default group....
now lets look at what happens when we set maxLogins as we should.
Requested notification messages from server 'belaServer'
belaServer: no maxLogins info from server process.
belaServer: setting clientID to 1, as obtained from server process.
belaServer : setting clientID to 1.
we still get the no maxLogins info (not sure if thats a red-herring or not)
but note how it gets clientID =1
this is actually correct behaviour, because it also means the new client gets its own group.
(the server creates a group for each user)
Now... Ive no idea why this works for everything other than Ndef (and things like proxyspace)
unfortunately thats a bit beyond my understanding of SC... Im guessing its something to do with audio channels and routing , but no idea how to get any more info about it....
note: I did in the meantime test the same processing running scsynth on my iMac, and scide on a laptop, and that seemed to work without issue.
so it seems to either something to do with the bela SC build!?
is the current build of SC based on the 3.9.0 release code? (from January, as i note the logs say 3.9dev), is it worth trying the release code base?
I guess at the moment its not an issue for me, as Im not going to do any multi user stuff, so doing things in the default/local group is no issue...
but it might have some consequences we dont know about 😉