🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left... mailtimers.com
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
Your shopping cart is empty.

Live11 Macro bug

CSS Bugs
Submitted by Annette Brosin on Sun, 02/28/2021 - 23:35
Annette Brosin
Control Surface Studio User

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 :(

Topic Category: 

15 Responses

Comments

Annette Brosin
Control Surface Studio User
Annette Brosin - Sun, 02/28/2021 - 23:46
#1

Small edit: I should correct my previous observation: in existing sessions, SOME macros will still work if I assign previously unassigned ones, some won't.

Annette Brosin
Control Surface Studio User
Annette Brosin - Mon, 03/01/2021 - 03:20
#2

Bug "identified": after another round of trial and errors, I found what the specific issue (1) is that specifically creates another problem (2) in Ableton11.
(1) If I open a session previously created in Ableton10, I need to "recalibrate" my controller knobs affecting (only!) macros, by dragging the dial with the mouse all the way to 0. That's when my mappings start grabbing again. If I create a new device with an empty rack, as described in my original post above, all is good since the macro dials are all the way to the left (0) or right (127) to begin with. However, when I drag a preset into the rack, it obviously "externally" changes the macro values. This is when my controller can't control anymore. Only after "recalibrating" by going back to 0 does it work again.
(2) This becomes a continuous issue if I use Ableton11's variations - one of the main motivators for me to purchase the upgrade. Launching a variation inevitably affects a similar "external" change to the macro values, which again renders my mappings inactive until "recalibrated". I found out that if you when through this "recalibrating" for all the macros PER variation and THEN take a snapshot, it will actually be recalled. If there were variations where you didn't recalibrate before taking a snapshot, the mapping will not work.

I'm not sure how Ableton changed something in their update that creates this behaviour. I'm also not sure if this is an issue coming up for other parameters, so far I've only found it in macros, while I'm using mappings for volume, pan, arm track, mute successfully.
All this being said, I'm not even sure if this is only the case for me? Anyone else have this?

JohnC
Forum Admin
JohnC - Thu, 03/04/2021 - 20:52
#3

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

Annette Brosin
Control Surface Studio User
Annette Brosin - Sat, 03/13/2021 - 08:14
#4

Hi! Sorry for the delay, I didn't see there was a response yet.
There is an entry in the log indeed, every time a mapping doesn't work (until recalibrated). Attached is a photo of two if the log entries.
In the meantime I found out that every now and then faders, pans, macros seem to have lost their mappings between the last time the session was open and then.

upload files: 
Image icon Screen Shot 2021-03-12 at 6.13.20 PM.png
Image icon Screen Shot 2021-03-12 at 6.12.56 PM.png
JohnC
Forum Admin
JohnC - Tue, 03/16/2021 - 08:10
#5

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

Annette Brosin
Control Surface Studio User
Annette Brosin - Tue, 03/16/2021 - 15:53
#6

Thank you!
Just tried it and still got a log entry upon loading the session, but I forgot to take a screenshot. After I cleared it and tried my mappings, almost all was fine. However, whenever I change a fader, pan or macro with the mouse, the mapping won't work until I drag it (per mouse) all the way down to 0 or up to 127.
And before doing any of that, one channel brought up this novel:

Traceback (most recent call last):
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/ControlSurface.py", line 428, in receive_midi
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/ControlSurface.py", line 437, in _do_receive_midi
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/ControlSurface.py", line 453, in handle_nonsysex
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/InputControlElement.py", line 489, in receive_value
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/EncoderElement.py", line 76, in notify_value
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/SubjectSlot.py", line 71, in notify_method
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 94, in __call__
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 12, in default_combiner
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 99, in _slot_notification_generator
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 22, in __call__
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 1701, in midi_cc_ch_3_val_70_mode1_listener
self.pick_brain(self.parameter_1_id_170)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9170, in pick_brain
self.val_brain(cnfg)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9251, in val_brain
new_val = self.relative_decision(cnfg)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9313, in relative_decision
new_val = self.step_in_line(cnfg, max_min)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9376, in step_in_line
if cnfg["current_position"] > previous and cnfg["current_position"] < step_val:
TypeError
:
'>' not supported between instances of 'float' and 'str'
Traceback (most recent call last):
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/ControlSurface.py", line 428, in receive_midi
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/ControlSurface.py", line 437, in _do_receive_midi
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/ControlSurface.py", line 453, in handle_nonsysex
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/InputControlElement.py", line 489, in receive_value
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/EncoderElement.py", line 76, in notify_value
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/SubjectSlot.py", line 71, in notify_method
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 94, in __call__
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 12, in default_combiner
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 99, in _slot_notification_generator
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 22, in __call__
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 1701, in midi_cc_ch_3_val_70_mode1_listener
self.pick_brain(self.parameter_1_id_170)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9170, in pick_brain
self.val_brain(cnfg)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9251, in val_brain
new_val = self.relative_decision(cnfg)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9313, in relative_decision
new_val = self.step_in_line(cnfg, max_min)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9376, in step_in_line
if cnfg["current_position"] > previous and cnfg["current_position"] < step_val:
TypeError
:
'>' not supported between instances of 'float' and 'str'
Traceback (most recent call last):
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/ControlSurface.py", line 428, in receive_midi
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/ControlSurface.py", line 437, in _do_receive_midi
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/ControlSurface.py", line 453, in handle_nonsysex
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/InputControlElement.py", line 489, in receive_value
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/EncoderElement.py", line 76, in notify_value
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/SubjectSlot.py", line 71, in notify_method
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 94, in __call__
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 12, in default_combiner
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 99, in _slot_notification_generator
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 22, in __call__
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 1701, in midi_cc_ch_3_val_70_mode1_listener
self.pick_brain(self.parameter_1_id_170)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9170, in pick_brain
self.val_brain(cnfg)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9251, in val_brain
new_val = self.relative_decision(cnfg)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9313, in relative_decision
new_val = self.step_in_line(cnfg, max_min)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9376, in step_in_line
if cnfg["current_position"] > previous and cnfg["current_position"] < step_val:
TypeError
:
'>' not supported between instances of 'float' and 'str'
Traceback (most recent call last):
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/ControlSurface.py", line 428, in receive_midi
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/ControlSurface.py", line 437, in _do_receive_midi
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/ControlSurface.py", line 453, in handle_nonsysex
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/InputControlElement.py", line 489, in receive_value
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/EncoderElement.py", line 76, in notify_value
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/SubjectSlot.py", line 71, in notify_method
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 94, in __call__
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 12, in default_combiner
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 99, in _slot_notification_generator
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_Framework/Signal.py", line 22, in __call__
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 1701, in midi_cc_ch_3_val_70_mode1_listener
self.pick_brain(self.parameter_1_id_170)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9170, in pick_brain
self.val_brain(cnfg)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9251, in val_brain
new_val = self.relative_decision(cnfg)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9313, in relative_decision
new_val = self.step_in_line(cnfg, max_min)
File "/Applications/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/css_beatstep_script_midmarch2021_with_macropresets_copy/css_beatstep_script_midmarch2021_with_macropresets_copy.py", line 9376, in step_in_line
if cnfg["current_position"] > previous and cnfg["current_position"] < step_val:
TypeError
:
'>' not supported between instances of 'float' and 'str'
Clear Log

Annette Brosin
Control Surface Studio User
Annette Brosin - Tue, 03/16/2021 - 20:17
#7

I've been going through all my modes and mappings and saved the Ableton session. Restarting Ableton and loading the session looks like the mappings stuck. But
1) as stated above, whenever I make a change in a controller value with the mouse, the mapping doesn't work anymore. Not sure if this is only an Ableton11 issue though.
and
2) once the session is loaded I still get this log entry:

Traceback (most recent call last):
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1316, in install_observer_listener
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1348, in _observer_install_listener
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1470, in _observer_id_callback
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 262, in _get_object_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 252, in __init__
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 320, in _calculate_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 261, in _find_root_object_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py", line 1068, in get_root_prop
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py", line 1062, in
RuntimeError
:
Can't obtain live set at this time
Traceback (most recent call last):
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1316, in install_observer_listener
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1348, in _observer_install_listener
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1470, in _observer_id_callback
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 262, in _get_object_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 252, in __init__
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 320, in _calculate_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 261, in _find_root_object_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py", line 1068, in get_root_prop
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py", line 1062, in
RuntimeError
:
Can't obtain live set at this time
Traceback (most recent call last):
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1316, in install_observer_listener
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1348, in _observer_install_listener
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1470, in _observer_id_callback
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 262, in _get_object_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 252, in __init__
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 320, in _calculate_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 261, in _find_root_object_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py", line 1068, in get_root_prop
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py", line 1062, in
RuntimeError
:
Can't obtain live set at this time
Traceback (most recent call last):
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1316, in install_observer_listener
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1348, in _observer_install_listener
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1470, in _observer_id_callback
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 262, in _get_object_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 252, in __init__
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 320, in _calculate_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 261, in _find_root_object_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py", line 1068, in get_root_prop
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py", line 1062, in
RuntimeError
:
Can't obtain live set at this time
Traceback (most recent call last):
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1316, in install_observer_listener
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1348, in _observer_install_listener
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1470, in _observer_id_callback
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 262, in _get_object_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 252, in __init__
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 320, in _calculate_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 261, in _find_root_object_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py", line 1068, in get_root_prop
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py", line 1062, in
RuntimeError
:
Can't obtain live set at this time
Traceback (most recent call last):
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1316, in install_observer_listener
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1348, in _observer_install_listener
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 1470, in _observer_id_callback
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py", line 262, in _get_object_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 252, in __init__
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 320, in _calculate_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py", line 261, in _find_root_object_path
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py", line 1068, in get_root_prop
File "output/Live/mac_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py", line 1062, in
RuntimeError
:
Can't obtain live set at this time
Clear Log

JohnC
Forum Admin
JohnC - Tue, 03/16/2021 - 20:56
#8

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.

Annette Brosin
Control Surface Studio User
Annette Brosin - Wed, 03/17/2021 - 05:29
#9

Email sent!

idfalk
Control Surface Studio User
idfalk - Sat, 03/20/2021 - 16:39
#10

John - Just posted a couple of minutes ago in 2.5.6 thread, but I think I am getting the same errors as Anette here.

Annette Brosin
Control Surface Studio User
Annette Brosin - Sat, 03/20/2021 - 17:36
#11

Just a little update: I've been in email contact with John who instructed me to re-install my script and restart Ableton, as they did some changes to their server. I now have a properly working script, even though on startup of my Ableton session I still get these log entries. But the script with its mappings works! :)

JohnC
Forum Admin
JohnC - Sat, 03/20/2021 - 18:36
#12

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 :)

JohnC
Forum Admin
JohnC - Mon, 03/22/2021 - 17:35
#13

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."

Annette Brosin
Control Surface Studio User
Annette Brosin - Mon, 03/22/2021 - 22:49
#14

Thanks for doing all this investigating!
That's interesting.. I just did a few tests with a simpler one of my sessions and it turns out that it's in the new String Quartet presets, whenever there's the Spitfire mod table. Not sure that's a m4l device. Anyways, when I take that one out of the chain, the session can be loaded without the log entries in CSS. When I use the mod table device on it's own, or at least not in the context that it's embedded in with the String Quartet instrument, it doesn't create the issue.
I don't really care now though haha, the sessions and scripts work for me :)

JohnC
Forum Admin
JohnC - Tue, 03/23/2021 - 20:49
#15

That's good to know, thanks Annette.
I get the same errors with one of my sessions too. It doesn't have anything from Spitfire in it and I don't think it has any M4L devices in it.
Either way, its clearly not a midi remote script error but Live 11 is reporting it as such, which is confusing for us haha.
I have contacted Ableton again to expand on the issue more, hopefully they can implement a fix (fingers crossed).