Re: Ideas for an OSC receiver workaround?

• Subject: Re: Ideas for an OSC receiver workaround?
• From: Vibeke Bertelsen <email@hidden>
• Date: Thu, 9 Jul 2009 01:27:11 +0200
• Delivered-to: email@hidden
• Delivered-to: email@hidden

OK so I found an answer or at least a clarification of how the OSC
receiver works if you have more than one active at a time on the same
port.
This is the case if you start multiple instances of the same QC comp
(e.g. as I do through my VJ application) or if you have two QC
compositions that both have an OSC receiver listening on the same
port.

If you send OSC from another application to QC to ip 127.0.0.1 only
one of the OSC receivers will get the message.
The same if you send from a Quartz composition to ip 127.0.0.1: Only
one OSC receiver gets the message.

However - if you send from within a Quartz composition to ip 0.0.0.0:
all instances of the OSC receiver will get the message.
I haven't had any luck sending from another application to Quartz on
port 0.0.0.0. However that might be a local problem or due to an error
I made. I'm not sure.

My workaround is to make a small "rerouter" within quartz. All
messages sent to 127.0.0.1 are rebroadcast within QC to ip 0.0.0.0
using another port and now all my comps get the message on that port.
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden

This email sent to email@hidden

• Prev by Date: Re: QCCompositionLayer Rendering Thread
• Next by Date: protocolInputs from iTunes
• Previous by thread: Ideas for an OSC receiver workaround?
• Next by thread: Maths Expression Error (Or Feature)
• Index(es):
  • Date
  • Thread