- Prefers to be called
- Uses pronoun
- Seattle, USA
- Work website
- Facebook profile
- YouTube profile
- Personal website
- 1 year 7 months ago
- Last seen
- 2 weeks 2 days ago
Seems a shame to have to specify the IP address rather than just port number. I suppose the IP address won't change without you knowing.
So the problem with a 'Make OSC Output' setup is really on the receiving side, where clients take all messages even when a single port is specified?
If it is a bug it's been there since 1.2.8. But I agree if this is intentional it really should be more obvious how to avoid the duplicates. You may be on to something with multiple OSC channels (something like an Auto/Omni being added) but the tests do specify particular ports throughout.
I just tried the test composition on a brand new machine - with default network settings - and and saw the same behavior; with WiFi enabled incoming OSC messages are repeated. If I disable WiFi before starting the App, I don't see the duplicates (either in OSCulator or VDMX). Not really sure what to try next, other than run without a network obviously :-)
I spoke too soon. The cause of the repeated OSC messages is network related, and I had my network disabled during my last tests. I think there is some sort of loop. With my wired adapter connected I get two repeats, and with WiFi on also I get two or three more. Nothing appears to be out of place with network settings, so I'm not sure where the problem is...
I may have cracked it. Perhaps the duplicates were caused by the App running at a super high frame-rate, or Syphon couldn't provide new fames fast enough. Anyway, the attached simple composition works as expected. I'd still welcome any insights, though. I'm definitely a beginner at this.
(I tried throttling a plugin with 'Fire Periodically' but only the simplest Compositions didn't impact VDMX frame rate.)