Hi,
First, have a look at “spat5.tuto-osc-3.maxpat” which provides information about initialisation order.
As mentioned there, it is recommended not to mix multiple initialisation strategies. It seems like that’s what happens in your patch.
You have the speaker coordinates typed in the spat5.oper box, using @initwith. Supposedly, that should be enough for proper init.
However, your patch also contains spat5.speaker.config which is triggered multiple times: from loadbang, and from the [live.menu 29] which is “initial enabled”. So that causes some confusion (and multiple inits with actually different speaker coordinates).
When spat5.speaker.config receives the “/speaker/number 29” message, it first initialises with a default speaker layout containing 29 speakers. This default setup is planar, which triggers error messages from your vbap3d renderer.
I would recommend that you simplify the patch by removing/disconnecting some of these elements.
Feel free to use [spat5.osc.print] to try to see which coordinate messages are actually triggered in the various places.
Meanwhile, I’m also investigating if things can be improved on the spat5.oper / spat5.spat~ side. Maybe with more user friendly debug information…
Hope this helps,
T.
