Holiday notice: Cycling '74 will be closed on Dec 25th, 26th, and Jan 1st. Manual authorization, support cases, and manual order processing will be delayed.
"Bad" bang when line~ is finished?
Jul 08 2014 | 8:02 pm
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?
- Jul 09 2014 | 2:35 pmYou'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?
- Jul 09 2014 | 3:18 pmFWIW 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 Inspectorsconfused[dot]com !Max 6.1.7 32bit on Win7
