OSC data from max to quartz composer?
Hi, not sure if anyone has used the OSC receive function in Quartz composer but i’m currently having very little success. I’ve tried it on various different ports and IP addresses and still no luck. Maybe there is a specific IP address i need to use or a port or something?
If any one has figured out how to get this working your help would be appreciated.
Without detail, its hard to point to the precise cause of your problem, but, in my basic tests I had no luck with the QC OSC REceiver either, while got this custom QC patch to receive from max pretty quickly.
I did some tests a while ago and had no basic problems. Attached is a QC example that receives the coordinates of a circle. Note however that x and y must be sent with separate messages because QC can handle only single arguments.
Interesting… thnx broc.
Well, I don’t know what I was doing wrong with QC OSC receiver, it appears to work now.
What I can say comparing the two is that qcOSC appears to be a lot smoother (read less glitchy) than the built in OSC receiver which appears to jump to 0. 0. (origin) arbitrarily. Which according to the author of qcOSC, the reason they created the plug-in…
Yes, I can confirm some glitches with the built in OSC receiver.
So for serious work the qcOSC plugin seems indeed very useful.
Cheers for your help guys.
I’ve moved that qcOSC into the appropriate folder but i can’t quite figure out how to open that with in QC… any advice?
I’ll try out the patch you’ve attached and see what comes of it.
The plug-in should go in Library/Graphics/Quartz Composer Plug-Ins (or user/Library/Graphics/…)
In Quartz composer the plug-in should appear in the Patch Creator window list as qcOSC under the Plug-in Category. In the settings item of the inspector pane set the port to the port you expect to receive OSC data on.
Below is a patch to send OSC x y messages to control brocs QC Composition.
----------begin_max5_patcher---------- 563.3oc0Vt0aaBCFF9Z3WAxR6trTeHPfc2T+AzKZuapZhDbR8DXi.iV5p5+8 4Cv5IRBI.oLEEawmM1u9weu17jqCXkXGsD38Mue3437jqiiIjNfS8yNfr3cq SiKMcCvo+Vr5WfY1ljzcRS3q7PP37lvaDbYI6OTcSH3bXcXdUFimRklQB+RP QkrIJpNpMj7wbpUbfMohX0Tcec6rDyzpjxWQjWOs73Lyq.9dAKNsok7X45GX 7s+rftVZGw.ektTpKPWQLknv4Pu60uwytt5hY++BE7YAEzBhkJ9C.Uxnkkwa oe.K4hBolLPTqnAM2OxGEtb.3S6nAcdnIJTSCLDoqBFkDlx7BFWtw6pcdeYy oj2fFBt.6iOhXRbBH8BK4r0xxTVBs.z8ce79VkJTBlYqZa8RN9hZgtLZotLD MVt.3mhKH5LMAQ1M3gvDrpRJEbv.jOuJlus0UY3AVKKrp2OvZqaJGR+7M4T9 shJdx0JHWHRUSvd1tOIeMYu6zyr+u41quikQuKtcp3edFcKuVZrCHLZLN.rJ IujxSTCuZVT+PGvgbRHC9QJf6wwcXr8fN7hQ8ZfG+LtFnWe3.w+.WCXlNPJi +9O4zLf53ukUkhph0Mhs4paO3+TcBsTx3wRl5TjW5D9M84AVRBk+5TfLVRtP w2ZMrmMttJI+ImhhlbJR+kEGURgWVIQ5fjdmtGcMM8nDtKT5hJovNnH+Kph5 TlD4hKIzwjzD7L.+ImeqOJR8vyt+Efeb3yB -----------end_max5_patcher-----------
I wonder why you don’t simply use the Max built-in udpsend like this.
----------begin_max5_patcher---------- 399.3oc0U10aCBBEF9Z8WAgqcsfV0tc29crzrPE5JKJXDLytl9eeBpqej9gq swz4EdBGNbxy6q.t10ANWVwTPvKf2.NNqccbroLIbZG6.yHUIoDksLnf8kb9 mPulozrJsMcIMWwDTPpLgjtTpz.Lp9oqtERgVw+lYpEiFgZSKJy3hTl11Zba xbhNYIW7w6ErDcCZXTP8Z.33Xav22FlNBAl0tHN0hQMZOEC21cYotq8ncPQP xrn.esfSRglI135Zd4ca1PdAK2XCiWcuT9jFkGLwDBmdNgGcbg208lT5U4rl VCg+1jgwSptSdRTXusjvGSKYr4zwn+hc3eQ6.EYBAQmyNvA+Q+XQpjn+OZJc maPg8vU7eDbkbdhVkxorB30sAvJ3ms2PNEebkdhO+9mRnbgF50D.y1QS1dCS 4hC+2gkNS98EpRVVjz0zVP.aIjxTZtfn4RwN0f2unkbJkI18l7LNMWVyVKC6 Qn2UgD9RH4OnHg6iMENnHE1ChhGThhd3H5fcIGGona.o5Aab+AvifuSX -----------end_max5_patcher-----------
Yeah, I had to remind myself. Goes back to doing some network OSC stuff a while back (OTUDP) and having some issues and more recently reading about better OSC compatibility in the UDP help file [p cnmat_compatibilty] which I just checked again and is still there. For most purposes its probably redundant, but old habits die hard…