Live11 Macro bug
Hi there,
I just noticed a pretty bizarre bug that I couldn’t duplicate in Live10. On Live 10, the efx mode of my Beatstep script works so that I can control the first 4 Macro-Parameters of a device (on a selected track) with my first 4 endless controllers, the other 4 I can control with my first 4 pads. Now in Live11, in my older sessions only random macro controls react to my controller. When I make a new track (or a new session) and load an instrument rack, the macros react fine. As soon as I map anything from an instrument to a macro, my controller commands don’t seem to get through – though I see midi coming into Ableton. The same is true for Efx racks, audio and midi. Is this the case for everyone? I hope this can be figured out, because this is a biggie 🙁
Hi Annette,
Thank you for reporting this, it could be an issue related to Python 3 but we will investigate this further and hopefully have a fix soon. To help with this, when the issue happens do any errors display in the Control Surface Studio log? (located at the top of CSS).
Thanks
Hi Annette, we released a fix on the server yesterday which ‘might’ fix your issue.
Could you try installing the script again – there’s no need to update the Control Surface Studio App.
Thanks,
John
Hi Annette, those errors are very very strange, it looks like the script has somehow been encoded wrong.
Can you email the folder containing all files to us here: help at remotify.io
…and we can have a proper look at it.
The folder is located on your computer at: /Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy
Thanks.
Hi guys,
I’ve been doing some investigation of the above error (Can’t obtain live set at this time) and to me it looks like it isn’t actually related to our midi scripts, but is an issue with Live 11.
How I came to this conclusion…
I removed all CSS custom scripts from my Live 11, added one of the default scripts available in the preferences (Advance). When I load certain saved sets, the error is still displayed. This doesn’t happen with all of my saved sets and not sure what the connection is with the ones that cause it to appear.
But in my opinion, this is an issue for Ableton to fix. I will send a report to them and hopefully get a response.
The good thing is that this shouldn’t stop scripts from working, it just means the log needs to be cleared a bit more often 🙂
Ableton have come back to me regarding the error messages.
They said “These errors are caused by an error in a Max for Live device that you loaded.”
Sign up
User registration is currently not allowed.