Page 1 of 1
script getting evalated twice for pads?
Posted: 05 Jun 2014 19:11
by leehu
Hi, in the following patch I get the following output:
osc: test 1.
osc: /Pads/x 1.
osc: test 1.
osc: test 0.
osc: /Pads/x 0.
osc: test 0.
The normal x message is sent as expected, but my on_action() script appear to be evaluated twice on the pad down, and twice on the pad up...
Can someone else give this a go?
thx
Re: script getting evalated twice for pads?
Posted: 06 Jun 2014 06:12
by Macciza
Hi
What are you monitoring with? You need to log, not watch values . . .
The project looks fine - OSC messages are fine in Max here ...
MM
Re: script getting evalated twice for pads?
Posted: 06 Jun 2014 09:01
by leehu
the output comes from printing out the OSC input stream in Max, i.e. the output of the test message is being logged twice...
"You need to log, not watch values . . ."
are there any internal logging functions? not quite sure what you mean here
Re: script getting evalated twice for pads?
Posted: 06 Jun 2014 11:36
by Macciza
Hmm
In a basic Max patch?
I just used udpreceive into both a capture and a print and both look fine. Try the simplest system possible and make sure it is only patch open.
If printing to the Max window you should be able to click the arrow and get it to tell you which object sent that message . .
Sorry but it all looks good at this end.
- temp.tiff (82.89KiB)Viewed 1681 times
Just meant that you need to record values somehow not just watch them changing onscreen if that was the case . . .
Re: script getting evalated twice for pads?
Posted: 06 Jun 2014 13:18
by leehu
cant't see the tiff for some reason...
yeah, that's why it's so freaky
it is the only stuff running... i'm going to reboot and try again this eve. thx
Re: script getting evalated twice for pads?
Posted: 07 Jun 2014 16:15
by leehu
Hi, I rebooted and retried this - the test message gets output twice.