Strange One – Midi Velocity Value
Hi Gang,
I have attached the .json Script incase its useful.
Weird one here, I am using Ableton, A Yaeltex Turn & Ableton Push 2.
I have a set up here, an instrument rack (1) with two other instrument racks (2a & 2b) or ‘chains’ embedded within.
I have set up my CSS script so every-time a new chain is selected the encoder on my Yaeltex is updated and will control Macro 1 on that chain.
The feedback between the Yaeltex and Ableton is fine. When I move the knob on one or the other then I get a feedback response every time.
The issue comes when I introduce Push into the mix. When I open Ableton I do get three way feedback between Ableton, Push & The Yaeltex – each device feeds back to the other. When I change to a different chain I still get feedback from Ableton and the Push but the Yaeltex stops giving me visual feedback.
When I move the endless encoder on the Yaeltex there is a Jump from the encoder to the Value on Ableton. I know Value Scale is out there but this is not a viable solution for this issue.
What I need is the value across all of the devices to be the same at all times. I’m very close but there is just one glitch which I need to iron out.
Hi Glenn,
Thanks for the feedback – I am aware of the error and initially also thought this would be part of my problem. I troubleshoot what was triggering the issue and found out that it was to do with the chain selector going beyond the scale of the number of chains.
In my utilisation of the script I have paid attention to make sure not to make this error code occur and the problem persists.
To go a little further into what happens just incase this sparks some inspiration.
When I change the chain selector value I see the value of the desired Marco (Chain x, Macro 1) on all of the controllers (Push, Yaeltex & Ableton).
If i turn the encoder on the Yaeltex or Ableton first, it works fine without issue. It is only when I change the value on Push first that I don’t get tri-directional feedback. The values in Push and Ableton are updated but the yaeltex is somehow frozen.
When i turn the encoder on Yaeltex then the midi value jumps (to that of the Yaeltex controller) and then functions properly. The other way I can get it to function is by pressing the macro or by selecting the device rack with the mouse.
This new (also stripped back script) moves towards solving the problem. I have added a select device mapping to the script (with the M1 chain select modifier within it). when I press this button it syncs the the push and the Yaeltex. What I need now is to have that done without having to press a button, so when the chain selector is changed, the selected device button is activated.
I’m gonna work on this now and see what I can come up with.
Sign up
User registration is currently not allowed.