>From my experience with OSC, different implementations support drastically >different OSC packet formats/configurations. the OSC protocol is beginning to >be widely adopted but I would expect only "basics" to be supported, such as >"/path/variable value" vs bundles and or multiple paths like >"/path/all/effects/color 1.0 0.2 0.4 0.9" , wildcards or multiuple variables.
OSC is ... awesome but kind of a mess in the real world, from my experience. Unfortunately my advice would be to go for the lowest common denominator format / messaging :( QC is not alone in treating this stuff On Dec 4, 2010, at 2:57 PM, Rob Duarte wrote: > Hi all, > > I just want to make sure I'm not missing something... > > We can't send an OSC message like: /path s:somestring f:somefloat > > (ie: messages with more than one value - aside from a list of floats which > OSC Sender does do) > > I'm pretty sure OSC Sender doesn't do it, but I just wanted to check with you. > > Thanks, > 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/doktorp%40mac.com > > This email sent to [email protected] _______________________________________________ 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]
