Message sending problem
Oct 02 2012 | 8:31 am
Anybody has the same experience using Max/MSP?
I create an message box and give it an integer value [36]
When I connect a button to it and click this button,
the [36] message would be send to the variable "trigger",then it would go through a calculation procedure to be converted from decimal to binary,then reach another computer through the parallel port(I use the object staalport).
It's weird that when I press the message box directly, I can watch the scanning program presenting the correct value. But if I click the button to bang the message, I get the wrong number [26] on the scanning computer.
Is this the Max's own bug or something I'd done were incorrect?
the connection thread is like this:
[message]---->[object staalport]------>[parallel port on PC1]-------->[PC2]-------->[scanning program]
below is the patch
https://dl.dropbox.com/u/33630645/post3.maxpat
Thank you my friend.
- Oct 02 2012 | 6:50 pmI couldn't take the time to figure out what to do with your patch, but this sort of thing is usually caused by the event model in Max: the UI thread vs. the Scheduler thread.A judiciously placed defer or deferlow will probably fix it.
- Nov 11 2013 | 2:05 pmHi Bream, I know it's a bit awkward to post this here, but i've been looking everywhere for the staalport object and it's not available anymore, i've searched it on the owner's page, but it's unavailable, i've found your post mentioning the object, do you think you can send me the object?Thanks in advance,Mário
- Nov 11 2013 | 3:54 pmHi,I've got the object!:D
