Yes those server commands are the ones you'll need to use. To create
two synths, you'd send two /s_new commands, and you'd give the synths
*different* node IDs (the second argument). So maybe the first is 1001
the second is 1002. You'll need to do the book-keeping for the ID
numbers, if you have lots of them...
Dan
2012/1/25 Coma <guill...@gmail.com>:
OscMessage noteMessage = new OscMessage( new Object[] {"/n_set", OscMessage.defaultNodeId, "amp", 0f});OscMessage noteMessage2 = new OscMessage( new Object[] {"/n_set", gameNodeId, "amp", 0f});
OscMessage noteMessage = new OscMessage( new Object[] {
"/n_set", OscMessage.defaultNodeId, "amp", 0f,"/n_set", gameNodeId, "amp", 0f
});
The best way to do this is using Groups. The things running on the
server can be arranged in a "tree"-like layout (sort of like a
folders-and-files layout). By default, all synths get added as
children of the root node, but what you can do is use /g_new to create
a group (let's say you give it the ID 1234), and then add your two
synths to it. So you end up with a layout like this:
Root
-- Group 1234
-- -- Synth 1001
-- -- Synth 1002
Then you can send your /n_set messages to node 1234, and they
automatically go to all its children. Hooray!
Dan
2012/1/25 Guillem Coma <guill...@gmail.com>: