personal_username

I have a very large patch with many loadbangs, loadmess.

i see that some events which should be triggered by loadbangs sometimes are not happening.

I try every time to put [del] and so on, but is there a more elegant way to have them triggering events for real?

Hi all!
I have a very large patch with many loadbangs, loadmess.
i see that some events which should be triggered by loadbangs sometimes are not happening.
I try every time to put [del] and so on, but is there a more elegant way to have them triggering events for real?
thanks!


too-many-loadbangs

If the things that not being triggered are reading files, then a deferlow might solve some of your issues.

It's good practice (in complex situations) to have only 1 loadbang in your patch with a trigger object below it with different sends. This is useful if you want to init stuff in a particular order

In addition:
It's good practice (in complex situations) to have only 1 loadbang in your patch with a trigger object below it with different sends. This is useful if you want to init stuff in a particular order


I'm up to my ear in loadbang/loadmesses. Time to go back and clean that mess up....

thanks everyone, actually deferlow helped! I need to digg a little more into max manual, the are many object i don't use often which are amazingly useful. Thanks again!

i always use only one, and split it into two or three triggers for ordering. no problems.

What's the best way to handle loadbangs inside poly's?

The main poly's I'm using (where it's actually multiples of it rather than dsp muting) have loadbang->thispoly

Should I replace those out with my send version of loadbang or is it best to leave those self contained?

What's the best way to handle loadbangs inside poly's?
The main poly's I'm using (where it's actually multiples of it rather than dsp muting) have loadbang->thispoly

Should I replace those out with my send version of loadbang or is it best to leave those self contained?


too many loadbangs?