Advice on M4L Patch -> Module Naming "convention"
I am the author of the M4L Drum Box :-) and I did it thanks to you (I put all your names in the About page)… anyhow, I am facing a strange issue with my patch:
1/ On ableton live, I create a midi track and put in it the M4L Drum box.
2/ If I duplicate this track (so duplicate the M4L Patch)… well, I get strange behavior:
- the second patch doesnot start from time to time :-(
- I can select a preset in the presets PADs UI :-( from time to time
- certain toggle buttons can not be activated from time to time
I don’t know why this is happening :-(
My question is:
* I did not named very well my modules inside the patch :-(
* I use "S —#1accentvolume" to send values to other modules but I have only one big patch!!!
(I know that using the ‘#’ means that the value will be sent to another file. but I copied this from a tutorial :-( )
* do you think I should give specific names like this I don’t have any collusion between two M4L patches?
* Shall I remove the "#" and the "—" ?
you cannot use "—" and "#" in the same name declaration. it will just fail, so that the reason your multiple devices in a set are not working is that the objects are globally scoped in the set and interfering with eachother, same as if you named them all "foo".
"#" must come at the beginning of a name, so must "—".
"#" is for scope within an abstraction. in the top level it does nothing.
"—" is for scope throughout the entire M4L device no matter how deep (and does nothing in Max alone).
you need to go look at the manual or so.
Yeap, perfect, thanks to your remarks I went deeper in the documentation and find answers!! many thanks, I had some doubts but thanks to you I am more confident :-)
I can’t find documentation for the send # formation… Can you point me at it? Thx
Fund it I think, seems just add #0 to the front of the name for send/receive
I searched for "—" and for "send" "receive" "#" in the search box :-(
— in front of a parameter means that this data is unique to the patch.
# in front of the parameter means that MAX4LIVE will search the data into the sub patches as well :-)
if you combine both symobls, you get M4L to search for unique parameter into the main and sub patches.
I hope I am clear and not too wrong!
Hi egnouf. U r very wrong. Look at my post above which explains it. I agree that documentation on this issue should be 100 times better.
ooppsss.. sorry :-(