Bang on message object
Hi guys, first time I write so I hope to be clear enough.
I'm working on a big patch using Maxuino and I need to send to some HW a certain data that is a string composed by two numbers, the first is the channel number and the second a boolean variable. I make some controls to trigger data when a timer reach the time I want. I'm using a message object to store the string and then I trigger data whit a bang.
The problem is that, sometimes, data are not triggered and my HW don't receive anything. That's because the message object don't let data pass through it (I forced a bang manually and checked if another connected message had received data). Then I replaced the object with a new one and that's worked. But it seems to be a casual problem.
Does anyone have ever had this problem with message object? Alternative ways to store data like that?
I'm working on Max 7.3.1, Mac.
Thanks
Working example:
On my setup your patch and the message box work. In general with Max I have seen that when an object is misbehaving, replacing it for a 'new' one can fix the problem.
Thank you Maarten. I have to avoid this kind of bugs so I'm trying object zl reg to trigger messages, I hope this will be less subject to abnormal behavior.
Hi,
usually I found that sometimes messages take some time to fill, so try to use a slight delay (10 ms) for the bang. When time is critical I use also a short delay that repeats the bang. I don't know if for your patch is a problem to receive the message twice. In this case you can filter out repetitions before sending the message
You must consider also the old school style (right to left order) in triggering messages.
Here enclosed a patch showing the problem and some alternatives.