Your shopping cart is empty.
🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left...
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
Inconsistent Feedback from script to controller during track navigation
Submitted by thx538 on Mon, 03/28/2022 - 07:57
Control Surface Studio User
Good morning,
I bought a CSS license a few days ago and noticed what it seems to me an inconsistent behavior during track navigation.
I am building a script for a midi fighter twister (using the controller template from your website) and a factory settings in my MFT.
I have assigned two buttons for track (Highlight) navigation : Previous & Next tracks.
What happens is the following :
1/ When the next button is pressed, the feedback from the script to the controller (CC Value is 0 to the next button and 127 to the previous button)
2/ When the previous button is pressed, the same happens : the feedback from the script to the controller (CC Value is 0 to the next button and 127 to the previous button)
The downside of it is that the (default) LED feedback is inconsistent, as the Previous button get lit ("on" status) in any case, as opposed to the next button.
Please see the attached : Test script and evidence (using Bome Midi translator)
I could implement a workaround with custom led feedback but it seems to me that next/previous should be symmetrical.
Thanks for your support and comments.
upload files:
Topic Category:
Comments
Hello thx538,
Welcome to the community!
In order for the Next button to light up, simply inverse the Led Feedback on and off states, like in the png file here included ;-)
That should do the trick for now.
I'll check if it is a bug, it might have something to do with the increment control type.
Greetings
Thanks for your answer,
As those buttons are temporary (and not toggles), feedback is not needed. Buttons should stay in their "off" state/color once pressed/depressed.
As per your indication I implemented a workaround with custom feedback (Send feedback=No) on both buttons.
Have a nice day !
Hi thx538,
That is true.
Glad you found a solution.
As a side note; In this example though, the led can help you as a guide. When the led is on, there is a track to be selected, when the led is out, you are at the end (or beginning) of your tracks.
Have a very nice day yourself! :-)
Understood !
Thanks for your support
What should happen with track highlight navigation is,
let's say you have a button to move the navigation left, the LED should be lit whilst there are more tracks available to move to in that direction.
Once the highlight gets to track 1, the LED should turn off.
Thanks John,
It works as you mentioned now, but with the opposite custom LED Feedback setup (See attached), which does not seem very logical to me, but it's not a big deal, even if I tend to think that left/right feedback should be symmetrical (See the sequence of Midi events in my first post).
Please also note two other issues :
1/ [minor] Regarding navigation right: on the last track (before return tracks) the LED is turned off as expected .... but pressing the button to move the navigation right selects the first return tracks (regardless of whether return tracks are made visible in the Live "view" menu) and subsequently cycles to the 1st track.
2/ [major]Track navigation is blocked when encountering grouped tracks, with a slightly different behavior between right (which selects the group) and left (which does not select the group) navigation.
This second issue really defeats the purpose of track navigation.
Let me know if I should open a separate bug report for it.
Thanks for your support and have a nice day !