You are not logged in. Please login or register.
RemoteXY community → Ideas and suggestions → Audible Feedback on buttons, switches, and selectors.
Trying to set up audible feedback (key-clicks) via the sketch and the interface is tedious to the extreme.
Timing is critical, all the sounds are different lengths, and there are no suitable sounds for this.
IMHO it shouldn't be done via the interface anyway, but should be done in-house on the app.
An option to enable key-clicks on objects would be a great feature.
Yes you are right. What you want can only be done by sending events. Now only the current states of the variables are transferred. We are working on events. It will also allow to add many cool things like notifications, message monitor.
Yes you are right. What you want can only be done by sending events. Now only the current states of the variables are transferred. We are working on events. It will also allow to add many cool things like notifications, message monitor.
Why would you want to send an "event" to the app when a button is pressed, for example?
If you made the "key-click" sound locally in the app it doesn't need to go to the sketch through the interface....
Trying to set up audible feedback (key-clicks) via the sketch and the interface is tedious to the extreme.
Timing is critical, all the sounds are different lengths, and there are no suitable sounds for this.
Yes, now it's like that.
For example, if we do this. If sound starts playing 1 time the entire sound file from start to finish when the variable is changed from 0 to sound value. Everything looks very good.
But how can you play a file twice in a row? How can you constantly play a file? For example, turn on a siren if your parameter is out of range?
You can say that you will change the sound variable twice. But it won't work. This quick change will not have time to reach the smartphone, because it will not even be transmitted, the connection is slow. The value of the variable is transferred to the smartphone only at the moment when the transfer window opens. If you change the variable several times between communication windows, then these changes will not be noticed by the smartphone. If you change a variable multiple times in the same loop() then the RemoteXY will only see your last value when you call RemoteXY_Handler()
It is for the transmission of such one-time events that the functionality for the transmission of such events is needed.
Daba wrote:Trying to set up audible feedback (key-clicks) via the sketch and the interface is tedious to the extreme.
Timing is critical, all the sounds are different lengths, and there are no suitable sounds for this.Yes, now it's like that.
For example, if we do this. If sound starts playing 1 time the entire sound file from start to finish when the variable is changed from 0 to sound value. Everything looks very good.
But how can you play a file twice in a row? How can you constantly play a file? For example, turn on a siren if your parameter is out of range?
You can say that you will change the sound variable twice. But it won't work. This quick change will not have time to reach the smartphone, because it will not even be transmitted, the connection is slow. The value of the variable is transferred to the smartphone only at the moment when the transfer window opens. If you change the variable several times between communication windows, then these changes will not be noticed by the smartphone. If you change a variable multiple times in the same loop() then the RemoteXY will only see your last value when you call RemoteXY_Handler()
It is for the transmission of such one-time events that the functionality for the transmission of such events is needed.
Understood, but why can't the key-click sounds be generated by the smartphone app? They don't need to go anywhere near the sketch.
RemoteXY community → Ideas and suggestions → Audible Feedback on buttons, switches, and selectors.
Powered by PunBB, supported by Informer Technologies, Inc.