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
script getting evalated twice for pads?
script getting evalated twice for pads?
- Attachments
-
- test.jzml
- (2.61 KiB) Downloaded 73 times
Re: script getting evalated twice for pads?
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
What are you monitoring with? You need to log, not watch values . . .
The project looks fine - OSC messages are fine in Max here ...
MM
iMac 2.8G i7 12G 10.6.8/10.7.2, Legacy Dexter/Lemur, Liine Lemur/iPad2, KMI SoftStep, 12Step & QuNeo , B-Controls, Mackie C4 etc
MaxMSP, Live Suite, Native Instrument stuff, etc Modified Virtual Guitar System etc All Projects/Modules © CC-BY-NC-SA[*][/b]
MaxMSP, Live Suite, Native Instrument stuff, etc Modified Virtual Guitar System etc All Projects/Modules © CC-BY-NC-SA[*][/b]
Re: script getting evalated twice for pads?
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
"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?
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. Just meant that you need to record values somehow not just watch them changing onscreen if that was the case . . .
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. Just meant that you need to record values somehow not just watch them changing onscreen if that was the case . . .
iMac 2.8G i7 12G 10.6.8/10.7.2, Legacy Dexter/Lemur, Liine Lemur/iPad2, KMI SoftStep, 12Step & QuNeo , B-Controls, Mackie C4 etc
MaxMSP, Live Suite, Native Instrument stuff, etc Modified Virtual Guitar System etc All Projects/Modules © CC-BY-NC-SA[*][/b]
MaxMSP, Live Suite, Native Instrument stuff, etc Modified Virtual Guitar System etc All Projects/Modules © CC-BY-NC-SA[*][/b]
Re: script getting evalated twice for pads?
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
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?
Hi, I rebooted and retried this - the test message gets output twice.