Hi all,

I have a couple problems with the OSC Receiver patch in Leopard QC V3.1 (632).

---

#1 ... It seems to have trouble attaching to the port that I put in the settings. Even if nothing else is using the port, I get this error in the console and the composition won't run...

1/18/10 11:27:42 PM Quartz Composer[40178] *** Message from <QCOSCReceiver = 0x16357F00 "OSCReceiver_1">:
UDP Receiver initialization failed

---

#2 ... Every program I use to view the OSC messages that are arriving shows that the messages from the slider that I'm twiddling come over with a very simple format: /slider/1 0.0 <-- ie: a float (the spec for the OSC sending software says that this is what it sends as well)

In QC, however, if I move the slider too quickly then the messages look like this (according to QC running in debug mode - but not any other software I've used to dump OSC messages)...

1/19/10 12:14:12 AM Quartz Composer[40373] *** Message from <QCOSCReceiver = 0x17E7A180 "OSCReceiver_1">:
Packet received on port 1338:
{
    "/slider/1" =     (
        0.3715953,
        0.3754864
    );
    "__timetag" =     {
        fraction = 1;
        seconds = 0;
    };
}

It does show it properly most of the time (with one float), but like I said when I move the slider fast this trouble occurs. I am assuming that somewhere in the OSC Receiver patch code, it is polling too slowly for messages and concatenating the values into a newly formatted osc message itself??? It's a problem, because I am of course expecting a float.. not two floats with a comma.

I'm about to submit this as a bug, but I figured I'd check to see if anyone else has been monkeying around with OSC in QC and had troubles like these...

Thanks for any info,
Rob

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to