Norbert

Please see the attached patch to view a modified version that works as intended.

What I have here in my studio does not. The idea is that when line~ is done it should send a bang from the right outlet to random. Random then passes its value to route where it is filtered to one of ten outlets to retrieve a new data file to fill a coll. (Here I've left out the coll and related messages for simplicity sake).

When I use buttons to send bangs manually everything works as expected. When the bang comes from line~ it does not. I've even tried "filtering" the bang with a button before it arrives at random but no luck.

Any ideas as to why a direct bang from line~ does not work?

bad-bang-when-line-is-finished

your patch uploaded here works 100% for me even when i delete the button between line~ and take the bang out its right outlet straight to the 'random' object.

hope i've not misunderstood what you're saying.

(it could be that something else is causing the scheduler to be overtaxed at the particular time you need that bang.... uh... however, that wouldn't explain why adding regular buttons in between everything would then work for you.... so i'm not sure...)

hope i've not misunderstood what you're saying.
(it could be that something else is causing the scheduler to be overtaxed at the particular time you need that bang.... uh... however, that wouldn't explain why adding regular buttons in between everything would then work for you.... so i'm not sure...)


You're not missing anything. random will flat-out NOT accept the bang coming from line~

Does anyone have any ideas as to how I can troubleshoot to see if there is something else going on with the message? My printing to the Max window and using message objects I am certain that the bang coming from line~ is a real bang, but perhaps it's getting converted to another message type in some way?

You're not missing anything. random will flat-out NOT accept the bang coming from line~
Does anyone have any ideas as to how I can troubleshoot to see if there is something else going on with the message? My printing to the Max window and using message objects I am certain that the bang coming from line~ is a real bang, but perhaps it's getting converted to another message type in some way?


your patch works as expected here - i.e. it does what you say it isn't, and should be, doing.

Here's a duplicate version of your patch for you to test; I really can't think what the issue might be - you might have a patch or external called "line~" or "bang" somewhere, but you say that the bangs are working ok; sounds like maybe an error with [line~] or [random]; the only way I can get temporary/undesired functionality is by banging the envelope, before the previous one is finished - but that's normal . . .

My suspicion is that [line~] or [random] are broken; or have some unique properties set in their Inspectors

FWIW
your patch works as expected here - i.e. it does what you say it isn't, and should be, doing.

Here's a duplicate version of your patch for you to test; I really can't think what the issue might be - you might have a patch or external called "line~" or "bang" somewhere, but you say that the bangs are working ok; sounds like maybe an error with [line~] or [random]; the only way I can get temporary/undesired functionality is by banging the envelope, before the previous one is finished - but that's normal . . . 

"Bad" bang when line~ is finished?