Brian Gruber

When I create a new patcher in js or in MXJ with 

, and put some DSP objects in it with newdefault, they don't seem to work (although debugging shows that the messages are getting to the DSP objects).

An alternative which does work is to create a 'p' object and then get its subpatcher:

var p = this.patcher.newdefault(0, 0, 'p', 'somepatcher').subpatcher();

The first version has a few benefits, one of which is that you can't accidentally save the dynamically-created patcher as part of your patch.

Is this the intended behavior? I couldn't find it documented anywhere.

When I create a new patcher in js or in MXJ with new Patcher(), and put some DSP objects in it with newdefault, they don't seem to work (although debugging shows that the messages are getting to the DSP objects).

An alternative which does work is to create a 'p' object and then get its subpatcher:var p = this.patcher.newdefault(0, 0, 'p', 'somepatcher').subpatcher();

no-sound-from-patchers-created-through-scripting

can anyone confirm this? can anyone from cycling confirm whether this is how it's supposed to work?

no sound from patchers created through scripting