Laggy behavior after update to Live 12.3
Since updating to the latest version of Live, my script for my Nanokontrol 2 is lagging heavily in updating faders and knobs in Live, It seems to be a script issue because I tested it with the generic MackieControl script and everything is smooth sailing. I also tested out building a new script that was super basic just for 8 volume fader controls and it has the same issue.
Heya!
It looks like this fix was important enough for Ableton that they released a 12.3.2 with only this!
https://www.ableton.com/en/release-notes/live-12/
And indeed, it seems to be fixed for my Launch Control XL2 template!
🥳
We’re kind of a big deal haha 😀
I’ve tested 12.3.2 too and the lagging issue is gone.
A massive thanks to you and everyone who contributed to this discussion and who contacted Ableton about the issue.
Also if anyone from Ableton is reading this, a huge thank you for the lightning fast bug fix and update!
Hi,
I have the same problem with my Midi Fighter Twister and the generated script for Live 12.3. Like you, I tested it with a script assigning a single knob to the volume, same result.
Best Regards
Just to confirm, your scripts were working fine in Live 12.2 but 12.3 the same scripts are are laggy?
correct, I did the latest update for CSS as well (as I was loading in my scripts to the updated version) so not totally clear if it’s definitely a 12.3 issue or one with the latest iteration of CSS, or a bit of both
Ah ok, thanks for clarifying.
The same here ! eveything is updated !
I have submitted a support request from Ableton too !
Same for me here, some things changed too, like setting a cue point always happens at the current playing position and not at where you scrolled to with your header (scroll Arranger left/right)
Ok. It seems a few of you have experienced this.
We will need to narrow the issue down as I haven’t experienced this problem.
1. Roughly how many mappings do you have in your script,
2. Which mapping types are you using in your script
Any information on this will be very helpful, thanks all
It doesn’t really seem to matter, like I said, I had a pretty big script with 5 modes, session box, faders, knobs and such controlling all sorts of things, volume, panning, sends, device macros, etc… when I noticed the issue. So I just wrote a very basic script to test whether it was my script, or something else, it was just 8 faders mapped to track volumes in the main mode, and it still had the same problem
I did a similar test with 8 track volumes mapped to 1 input on the midi controller and experienced the same lagging issue in 12.3.1
Hi,
Thank you for your research.
For my part I have around 16 encoders (button and knobs) by mode, and 3 modes.
I use a lot of native functionality from remotify and a lot of specific code for deep mapping
(for example with one knob, when a clip is highlighted I can change gain of this clip).
Every mapping in code was working fine with Live 12.2
Thanks to you
Thanks jmw.
Roughly how many mappings do you have in it, would it be around 96 mappings across the 3 modes, 32 per mode?
You’re welcome.
EDIT > I count last night and I have 83 mapping 😉 (but a lot of block juste to init Led feedback !)
But everything was fine with Live 12.2.
I observe something in Live 12.3. If I want to scroll by exemple, everything work well if I slowly scroll but lag if I do it “normaly”. It seems like Live send too many “feedback” info
Same here. I have 3 controllers, one with lots of mappings (launch contrl XL) , and two smaller controllers. the smallest has less than 20 mappings. Both encoders and faders/knobs are affected. However the encoders mapped to device parameters seem fine. Whilst the encoder moving my session box is lagging, sometimes not even moving actually (this one is made with a reaction and a script). Faders and knobs controlling device parameter are all lagging.
Sign up
User registration is currently not allowed.
Would not recommend to use Ableton 12 and higher as it has no midi PC messages support in vst.