Convert bang to message 0 127
Hi,
I think this is pretty "simple" but I'm stuck.
How with a band can I send a 127 message and when it's off 0 ?
best
Z
More in detail I have some kind of sequencer that send some bangs, this band as to trig ctlout 8 bangs 8 ctlout but wish that the bang send an 0 message after the 127 one.
This is the patch I'm working on, I think it can be improved if you have suggestions, sometimes the sync is not perfect.
Best
dood, a bang does not have two states, so you can not do anything when it turns "off".
you are already walking into the right direction with the use of the trigger object, you just dont speak triggering fluently yet. for example this deferlow has nothing to do there.
in a sequencer context you often want to do things like "stop this whenever that starts", and trigger would read [t 1 0] in that case.
a few other thoughts
1)
i cant open the upper [p ]
2)
in the upper [p ] you are using the last inlet as hot inlet as it seems. it is better to ape the cycling externals´design and use the leftmost inlet as hot inlet (or as the "main" hot inlet of many hot inlets)
3)
are you sure you want to use controller #0 as control change?
4)
try these 3 versions of your clock
Hey Roman
Thank you for your help !!
1)
this the inside of the patcher you weren't able to open :
2)
This is a part of an other max4Live device I found (little_scale)
It's an euclidean sequencer.
3)
I will not use the ctrl change 0
4) Is it me or the first and second one is the same ?
My problem with my current is that is working when I have 8 steps and 8 fills but if instead I have 8 and 3 fills so the "off " message will not work.
So I am looking for a solution where each step will de independent
this is the patch with fews modifications
4) no. :)
4) but ... lol
So I found a solution using a [t 127 0] and connect a [pipe 4n ] on the 0 output
But when I'm using a menu to change the pipe time everything goes to short (I used the menu in the pipe help)
4.) that is the mean thing about order of messages: sometimes it does not matter, but in other cases it does.
about pipe: i dont know much about this 4n global tempo stuff, but i think it is normal that it does not immediately auto syncs everything after a change. in case that is true here, you would have to use milliseconds instead. it involves a bit rule of three but it is doable and more flexible on the long run.
in fact when I don't change the either in ms and bar division I get weird result :/
I will try to find the solution
Thank you for your help - The path is almost working fine
still have the plugsync~that sometimes doesn't run with ableton ?!