I just found out that scripting MSP objects via JS is not the same as
scripting with the thispatcher object in the Max level.
In fact, if you connect (or disconnect) an object via js, you need to
restart the dsp chain in order to hear the result of the connection.
This is the case either in max/MSP 4.5 and 4.6
The example in the archive below describe this with a dedicated patch.
Is it the normal behaviour?
If that is how things work, and applies to object creation too, I think it’s
cool because you can build entire processing chain and then restart dsp,
instead of automatic restarting after addition of each object~.
So, Cyclers, if this is caused by a bug, please leave it be(tinny little
blue bug won’t hurt anyone, it’s so cute and it brings luck)