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.
This seems like the kind of problem that’s hard to figure out without the controller and software in front of you. Maybe the Bank switching on the Yaeltex doesn’t behave like you expect it to? I’m guessing that because of when you get no MIDI messages on the monitor (that’s not a CSS or Ableton problem, I think). Maybe the button loses its MIDI configuration when switching back to Bank 1 via the button press?
I would need more insight in the MIDI configuration. Maybe if you could provide the following:
– Screenshots of the MIDI Config in Kilowhatt for all banks
– Some info on how the bank switching can be done for 1 button at a time.
– The controller template you are using with your CSS script.
– A video that focuses on the MIDI Monitor while you call out which buttons you press and knobs you turn, while you recreate your problem.
I want to point out a small detail: one controller doesn’t communicate with the other controllers, at least not directly. The controllers communicate with Ableton and Ableton gives them feedback. If a controller doesn’t receive feedback, then its communication with Ableton isn’t functioning properly.
It is possible to have a Control Surface script where one controller is the input and another is the output, but there’s always Ableton in between. A practical use case for this would be to control the effects of an instrument/hardware device that has no MIDI IN but does have a USB connection (e.g. a Boss Katana).
Sign up
User registration is currently not allowed.