Thank you for your time and help! I got the parameter scroll working. I’ve followed the tutorial you sent and I have been able to locate my Audio Effect Rack on tracks and is working as intended, but I’m unable to get it to find the same EQ Rack within individual Drum Rack tracks, is […]
This is completely broken in v2.9 and v3.1.1. Is there a working version?
and im still trying to figure out how to do the first part of your question lol
Hi, here’s a new version for the LiveCtrl script deactivated combine mode (links 2 different controllers via session box) for the time being. I’ll look into a more robust/working solution. Sessionbox navigation should work again. changed some parts in track name mapping There’s still a bug preventing sending track names opening a session without devices […]
In answer to this: Also ideally I’d like any information on the possibility of setting up the push buttons on the encoder to scroll through different velocities, i.e. -20db-0-20db on the EQ bands. I’ve attached a Reaction which can do this. Import it into your script, then select the listener to be your button. This […]
From your screenshot it looks its the second device in the first chain of the parent device. So to control a parameter in there you would use the “chain targeting” section in a Device Parameter mapping. See the settings in theis screenshot, that should target the device correctly (assuming the parent Device rack is the […]
Hi John, thank you for coming back. Yes, there are more tracks than the session box width (8 tracks). Also, it only works with the session loaded right with the start of Ableton Live and stops working after loading any other session or a new project. For me this is 100% reproducible also with two […]
Firstly you need to set the ‘current input value’ to the knob/encoder’s current value, or else the input value will never change meaning the knob will never move. Example: midi controller > current velocity values > knob 1’s latest velocity value The output rand for these sends goes from 0.0 to 1.0 so set those […]
Check you have added enough tracks to your Ableton session before attempting to move it and see if that avoids the issue.
It sounds like the midi controller is sending conflicting MIDI channels when you move it. I’m not sure about the Launch Control but some midi controllers have touch sensitivity meaning when you touch it it sends a MIDI message (usually a different channel), then sends another midi message when you move it. I’d suggest figuring out […]