button behaviour

[bmoussay]

Hello usiners,

First of all thanks Olivier for the version 4, it's really an amazing job you've done.
Just a suggestion about "buttons", I can't remember if it's been discussed or not...
Actually, now buttons send a fast 1 and 0 message after the button is released.
This behaviour is Ok for most situations, and CPU friendly I imagine.
But in some cases it would be more logical that a button sends 1 when it is pressed then keeps sending 1 while pressed, and then 0 when released.
This would be more CPU hungry for sure because Usine would have to watch the button all the time, but very useful in some situations.
So maybe the best would be to have the two options available (or two different "button" modules).
What do you think?
Olivier would it be difficult to implement?
Best regards,

B.

[bsork]

You can in fact use the Separator & Panel module like that; it has a mouse down outlet. The down side is that that module doesn't have any key or MIDI learn.

BTW, I checked the button's behaviour, and the trigger is sent when clicked, not released. The right thing to do in an application like this.

[SylvainT]

Hello Benjamin,

If I understand your question, I ask you why don't you use a switch. When the switch is lighted it send 1, and 0 otherwise.
So with a midi or key learn in absolute mode, when you press the key, the switch send a 1 and that until you release the key, then it send a 0.
Is it what you want?

All the best

Sylvain

[antwan]

Hello,

Yes, slydeparis is right but there's one more thing to consider. I'm also quite sure Benjamin already knows this - and this might be behind the whole question. The switch solution works only when midi or key learnt. Not with the mouse. The Sep&Panel solution was an interesting one, but I guess it could be good to have something that works for both, all in one. My own guess is, that an option on the button or switch module is the way to go.

antwan

[senso]

interesting discussion.
Benjamin, the behavior you describe is closer to the switch philosophy than the button.
In Usine and generally, in most softwares, a button sends shorts triggers and a switch can be switched ON a longer time.
So this functionality has to be implemented in switches better than buttons?
A kind of remote mode 'absolute' but works also with the mouse...

Let me think about a way to implement it.

[Vincent]

Hi,
The button's behaviour described by Benjamin (1 when pressed, 0 when released) is a "Gate".
In Reaktor, you have three different behaviours: Trigger, Gate, and Switch, all on the same module (options in a list).
It would be OK to have three different modules in Usine, but it's true that it would be "complete" to have choice between these trhee kinds of behaviours.
About he actual behaviour of the button in V4, it's triggered (1, then 0) when pressed; OK then. In v3.66, it's triggered when released: not OK...

[moody33]

In memory of things past...

http://www.sensomusic.com/forums/viewtopic.php?id=845

Senso said :

good suggestion,

the best direction is to have the same idea than the actual right click options:

-toggle = click to switch ON and re-click to switch OFF
-absolute = stays ON while the mouse is pressed

something like that

I'll find a solution.

[senso]

oups... it's a big memory crash!

[moody33]

oups... it's a big memory crash!

We know that this buggy thing will be solved in the next release !

[bmoussay]

Hello,

Yes, I think an "absolute" switch would be useful. (1 when pressed - 1 while pressed - 0 when released)
Maybe an additional module would be the good solution, or an option in either the switch or button module.
Actually the behaviour of the button which was sending a short 1-0 message when released was what I've observed in V3.68, it's a good thing it has been modified in V4 where the button sends 1-0 when pressed.
To be continued.
B.