Error Code in CSS Log

1.57K viewsCSS QuestionsCSS Error
0
0 Comments

Hey Folks,

I get this error code when I load my live set.

I do not get the error code when I open a new or a different set in Ableton which seems strange.

”

Traceback (most recent call last):

File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py”, line 1494, in install_observer_listener

File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py”, line 1526, in _observer_install_listener

File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py”, line 1650, in _observer_id_callback

File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py”, line 291, in _get_object_path

File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py”, line 267, in __init__

File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py”, line 335, in _calculate_path

File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py”, line 276, in _find_root_object_path

File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py”, line 1131, in get_root_prop

File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py”, line 1125, in

RuntimeError

:

Can’t obtain live set at this time

Buster_Delmonico Answered question

3 Answers

0
JohnC 2 Comments

The errors appear to be originating from “_MxDCore”, not a script created by CSS.

JohnC Posted new comment
R. commented

So I have deleted the _MxdCore Midi remote script and the error is now a lot shorter.

Traceback (most recent call last):
File “”, line 1, in
ModuleNotFoundError
:

I’m wondering how I can get rid of the ‘Traceback’ what ever that is?
JohnC commented

I wouldn’t recommend deleting the _mxdcore script as other midi remote scripts use this.
0
toneyvecchio 1 Comment

Original poster, did you ever get further along on this? I am getting nearly the same errors and can’t figure it out.

I just did a complete reinstall of Ableton, dropped nearly all my CSS scripts and similar, can’t figure out its origins. Also having lots of other strange behavior, so trying to figure out if this is at root of it.

JohnC Posted new comment
JohnC commented

in the OP’s errors, there’s nothing pointing to a CSS script.
It could be an issue with Ableton itself. The following message sounds like this could be the case:
“Can’t obtain Live set at this time”
0
Buster_Delmonico 1 Comment

This error is definitely not CSS script related, I see it in Live’s log file when certain Live sets load from disk regardless of whether a CSS, DIY, or No custom “remote script” is configured in Live’s midi options.  This thread helped me figure that out. (and seems to be the only “valid” hit my Google search bubbled up to the top results page)

In my experience, this error only seems to get logged when the .als file loading from disk has “Max 4 Live” devices saved in it, maybe DIY M4L devices, maybe “user library” presets for DIY M4L devices, I haven’t tried hunting much further.  But, for example, different sets containing the same DIY M4L device preset(s) don’t cause the same error logs when they load from disk. So, YMMV.

The logged error also seems to resolve itself before the Live set finishes loading completely, because remote scripts seem to operate normally after Live hands control to the user.  I think that’s what “at this time” in the error message implies, I haven’t seen “related follow-on issues” otherwise.

I also agree that deleting the _MxDCore “script” is a bad idea, other “Live functionality” definitely depends on its content.

JohnC Posted new comment
JohnC commented

Agreed.
Something is loading before the Live set and causing the error.
You could right about it being a Max4Live device.

Categories