🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left... mailtimers.com
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
Your shopping cart is empty.

Reactions: Nature of controller input response

CSS Questions
Submitted by Image_Engine on Mon, 08/31/2020 - 00:33
Image_Engine
Control Surface Studio User

Hi John
I posted this question at the end of another thread but its such an important thing to understand, I thought I should split the thread if thats ok;

I have controllers that produce a series of values dependent on the gestures applied. When I view the reference found here;

https://remotify.io/tutorials/reactions-reference-guide

Its implying that any change made to the listener produces an event, however, check the monitored events in the attached pics

When I trial a reaction eg with a condition of val > 126, its showing me that its responding to the initial button down value of 127 and executes fine

BUT

I want the response to be the last received value which should be 98. If I set a reaction condition of val == 98, the event does not fire.

?

Cheers

upload files: 
Image icon CC56.PNG
Topic Category: 

4 Responses

Comments

JohnC
Forum Admin
JohnC - Mon, 08/31/2020 - 08:33
#1

This is correct
"Its implying that any change made to the listener produces an event,"
Do you have more than 1 condition in your reaction? i.e. cur_val > 127 , cur_val == 98
Make sure you have the and/or selection set to 'or'

Image_Engine
Control Surface Studio User
Image_Engine - Mon, 08/31/2020 - 09:11
#2

Hi John
Good to have confirmed.
Its a very simple reaction; please check the pic

upload files: 
Image icon Condition.PNG
JohnC
Forum Admin
JohnC - Mon, 08/31/2020 - 12:09
#3

you're missing this value in the first input box of the if condition:
.cur_val

Image_Engine
Control Surface Studio User
Image_Engine - Mon, 08/31/2020 - 13:00
#4

Hi John
hehe...I just saw it in another post and was going to answer my own question...Im getting it but its taking a while...sorry but I hadnt seen that explained and in m4l, pure data etc its a lot more obvious.
Simply put for any other noobs;
To be able to select a specific controller value as a target, the LOM path element called;
".cur_val"
must be used to singularise the variable.
In other words, the activity of a button simply fires everything and the condition box needs this path element to report only the last value received.