88mph

is there a way to retrigger all the load bangs on the stage without connecting a bang to each?

loadbang

My favourite solution to this is not to have loadbangs scattered all 

over the patch - wherever you have a loadbang replace it with a receive 

with an appropriate name - in a separate patcher (I usually call it 

'init') put one loadbang, which bangs a message box with messages for 

all the receives - this makes it easy to add a reset button to bang all 

It also allows splitting the messages into two or more message boxes 

with delays, which can sometimes be very useful. It also makes it very 

easy to alter your loadbang values if that becomes necessary at any 

time, and having it all in one place makes it easy to remember what 

Lawrence Casserley - lawrence@lcasserley.co.uk

Lawrence Electronic Operations - www.lcasserley.co.uk

Colourscape Music Festivals - www.colourscape.org.uk

My favourite solution to this is not to have loadbangs scattered all 
over the patch - wherever you have a loadbang replace it with a receive 
with an appropriate name - in a separate patcher (I usually call it 
'init') put one loadbang, which bangs a message box with messages for 
all the receives - this makes it easy to add a reset button to bang all 
the 'init' messages again.

It also allows splitting the messages into two or more message boxes 
with delays, which can sometimes be very useful. It also makes it very 
easy to alter your loadbang values if that becomes necessary at any 
time, and having it all in one place makes it easy to remember what 
those values are.

Lawrence Casserley - lawrence@lcasserley.co.uk
Lawrence Electronic Operations - www.lcasserley.co.uk
Colourscape Music Festivals - www.colourscape.org.uk


I also do like this. Then you can have a list of init messages, using 

the [;somewhere do_something] messaging style, and store them in a big 

init message or a coll. With this, you can send bangs, read presets, set 

parameters, change DSP settings for each part of your patch.

f.e chanfrault | aka | personal computer music

> >>>>>> |sublime music for a desperate people|

I also do like this. Then you can have a list of init messages, using 
the [;somewhere do_something] messaging style, and store them in a big 
init message or a coll. With this, you can send bangs, read presets, set 
parameters, change DSP settings for each part of your patch.

f.e chanfrault | aka | personal computer music
> >>>>>> http://www.personal-computer-music.com
> >>>>>> |sublime music for a desperate people|


yeah, but i recently (+/- 1 year) started using Bpatchers a lot - 

using it a little bit like modules of a modular synth, from project 

in such a case the initial init (!) message is not that handy....

and it also remind s a LOT the ircam way of building patches (not 

yeah, but i recently (+/- 1 year) started using Bpatchers a lot - 
using it a little bit like modules of a modular synth, from project 
to project

and it also remind s a LOT the ircam way of building patches (not 
sure if this one is a plus or not ! ;-)

kasper
-- 
  Kasper T. Toeplitz
noise, composition, bass, computer
http://www.sleazeArt.com

I do this as well. Even more since I only recently started building 

Someone posted a example patch for such initialisations procedures on 

the list. I can't remember who (maybe Stefan Tiedje ?) but one may 

I do this as well. Even more since I only recently started building  
bigger patches. Very useful.

Someone posted a example patch for such initialisations procedures on  
the list. I can't remember who (maybe Stefan Tiedje ?) but one may  
find it in the archives.

On 21 May, 2006, at 13:02, Kasper T Toeplitz wrote:

> yeah, but i recently (+/- 1 year) started using Bpatchers a lot - 

> using it a little bit like modules of a modular synth, from project to 

> in such a case the initial init (!) message is not that handy....

In this case the init can be within each bpatcher, but I would still 

> and it also remind s a LOT the ircam way of building patches (not sure 

I have no problem with that - some things just work! :-)>

> yeah, but i recently (+/- 1 year) started using Bpatchers a lot - 
> using it a little bit like modules of a modular synth, from project to 
> project
>
> in such a case the initial init (!) message is not that handy....

In this case the init can be within each bpatcher, but I would still 
put it all in one place in that patcher.
>
> and it also remind s a LOT the ircam way of building patches (not sure 
> if this one is a plus or not ! ;-)
>
I have no problem with that - some things just work! :-)>

>>in such a case the initial init (!) message is not that handy....

>In this case the init can be within each bpatcher, but I would still 

>put it all in one place in that patcher.

>>and it also remind s a LOT the ircam way of building patches (not 

>>sure if this one is a plus or not ! ;-)

>I have no problem with that - some things just work! :-)>

>>
>>in such a case the initial init (!) message is not that handy....
>
>In this case the init can be within each bpatcher, but I would still 
>put it all in one place in that patcher.

>>and it also remind s a LOT the ircam way of building patches (not 
>>sure if this one is a plus or not ! ;-)
>>
>I have no problem with that - some things just work! :-)>
>
of course - that was meant by the ;-)

you can just double-click on a loadbang object to re-loadbang your patch.

create a [thispatcher] object and send it the message 'loadbang'

Could you talk again about the Notation, you have mentioned two weeks ago?

(you said : very flexible, is compatible with Final, Sibelius.....), Thanks.

Hi!, Peter,
Could you talk again about the Notation, you have mentioned two weeks ago?
(you said : very flexible, is compatible with Final, Sibelius.....), Thanks.

This will trigger only the loadbang you double-click on. To retrigger 

every loadbang in your patch/subpatcher you can send the loadbang 

message to a thispatcher you put in the toplevel of your patch.

This will trigger only the loadbang you double-click on. To retrigger  
every loadbang in your  patch/subpatcher you can send the loadbang  
message to a thispatcher you put in the toplevel of your patch.

so it does! thanks. i guess i always only use 1 loadbang...

On 22 mai 06, at 11:12, Jeremy Bernstein wrote:

> so it does! thanks. i guess i always only use 1 loadbang...

Right, in any case having only one loadbang allows you to make clean 

Right, in any case having only one loadbang allows you to make clean  
initialisations...

the new version of JMSL has mxj objects that interface the Jscore common

music notation classes with max. max patches are also included to get

you started right out of the box. jscore can export scores so that

other cnm apps can open, edit and print the scores.

JMSL (java music specification language)
www.algomusic.com

the new version of JMSL has mxj objects that interface the Jscore common
music notation classes with max.  max patches are also included to get
you started right out of the box.   jscore can export scores so that
other cnm apps can open, edit and print the scores.
