tag:support.nodebox.net,2012-11-01:/discussions/nodebox-2-3/153-osc-connection-with-maxmspjitterNodeBox: Discussion 2014-02-05T10:41:51Ztag:support.nodebox.net,2012-11-01:Comment/265396662013-04-24T08:42:28Z2013-04-24T08:42:28ZOSC connection with Max/Msp/Jitter<div><p>The documentation page you mentioned is for NodeBox 1, and so
wouldn't be useful for NodeBox 3.</p>
<p>For NodeBox 3, the OSC nodes are labelled "experimental": that
means they lack documentation and can change.</p>
<p>Here's a short tutorial on how to listen to events FROM Max
MSP:</p>
<ol>
<li>In Preferences, make sure "Device Support" is checked. Restart
NodeBox if needed.<br></li>
<li>In File > Devices, create a OSC device. In the first field
(where it says "-1" enter the port NodeBox should listen to). Press
start. (You can also enable auto-start if you want to start the OSC
listener automatically when the file is opened).<br></li>
<li>Start Max MSP and create a "send OSC" node (or whatever it is
called). Use the same port to send to.<br></li>
<li>In NodeBox, create a "Receive OSC" node. Leave the device name
as-is. Optionally, change the address prefix to only listen to
messages under an address (by default it listens to
everything).<br></li>
<li>If you want the arguments to have names, you can fill them in
under the "arguments" port. For example, if you receive events with
an x,y coordinate, use "x,y" (without the quotes) in the arguments
field.</li>
</ol>
<p>I've included an example that uses PD to send OSC events (I
don't have Max MSP).</p></div>Frederik De Blesertag:support.nodebox.net,2012-11-01:Comment/265396662013-04-24T15:32:35Z2013-04-24T15:34:02ZOSC connection with Max/Msp/Jitter<div><p>Hi Frederik,</p>
<p>Thank you so much for your help, I am really enjoying this tool
a lot.</p>
<p>I have tried what you suggested for connecting nodebox and max
msp, and here I am attaching what I have so far. So, I followed
your instruction and created my max patch using the "udpsend" node,
(it seems like it's working with vvvv here, <a href=
"http://www.youtube.com/watch?v=NR0F3uCzTmo">http://www.youtube.com/watch?v=NR0F3uCzTmo</a>)
and also set up my node in nodebox. but, I don't see they are
connected yet, so here I am asking you some more questions. ; )</p>
<p>what I am not sure about current state is</p>
<ol>
<li>
<p>whether the address prefix in the receive_osc node should
reference the folder structure of the max map file, like the way I
have right now.</p>
</li>
<li>
<p>also what kind of data the arguments in the receive_osc node can
have when receiving numbers from max msp. I know you had set up
size, hue and rotation in your example file, but I am not sure how
these can be received from max msp.</p>
</li>
<li>
<p>maybe this has something to do with the PD file that you sent
me? I have no idea what to do with it except that knowing that is a
pure data file.</p>
</li>
</ol>
<p>Thank you in advance, I look forward to hearing from you.</p>
<p>Best,<br>
Sang Un Jeon</p></div>sjeon01tag:support.nodebox.net,2012-11-01:Comment/265396662013-04-25T13:14:19Z2013-04-25T13:14:19ZOSC connection with Max/Msp/Jitter<div><ol>
<li>The address prefix is not the file path. You could see it as a
relative URL. In my PD example, the address is set to "/output",
and so that's what I listen for in NodeBox. I'm not really sure how
this would work in Max/MSP. A quick Google Search I could find
<a href="http://opensoundcontrol.org/topic/222">this blog post</a>,
but I don't really understand it.<br></li>
<li>The arguments are always numbers, I think.<br></li>
<li>I made the example in PD because I don't know / have Max/MSP.
PD is free software, so you might consider it if you can't get it
working in Max.</li>
</ol></div>Frederik De Blesertag:support.nodebox.net,2012-11-01:Comment/265396662013-05-25T02:45:41Z2013-05-25T02:45:42ZOSC connection with Max/Msp/Jitter<div><p>Is it possible to send OSC from Nodebox3 to PD ??</p></div>edontag:support.nodebox.net,2012-11-01:Comment/265396662013-05-28T10:06:17Z2013-05-28T10:06:17ZOSC connection with Max/Msp/Jitter<div><p>Currently, sending OSC data works, but is very hacky. The
problem is that NodeBox only calculates the rendered node and its
dependencies. This means that if you have some node in your network
sending OSC events, and it is not the rendered node, it won't
work.</p>
<p>A trick is to combine your output with the "send osc" node. This
way you can send message and have NodeBox show output at the same
time.</p>
<p>Again, this is a hack. We're thinking on how we can make this
work correctly. We reserve the right to change the way sending and
receiving works: that's why the nodes are labelled
"experimental".</p>
<p>Best,</p>
<p>F</p></div>Frederik De Bleser