Pioneer DDJ-SX3 vu meters -ERRORS USING REACTIONS
Hi,
I’m trying to map the meters on my Pioneer DDJ-SX3, with no results. I have already read the articles in this forum, and tried to use the script provided, still nothing.
Maybe it’s the controller’s template, I have used the DDJ-RX template provided in this site, changing midi values, but the meters still not working. The MIDI implementation chart of my device is very poor, it says only MIDI OUT – Bn 02 hh, I suppose that n is the channel and hh is the velocity, but who knows?
Can you help me? Thank in advance
UPDATE: to make a test, I have set up a reaction that sends the value of a knob to the meter, adjusting the ranges. Logging the reaction, I have a lot of red messages saying python errors:
Traceback (most recent call last):
File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py”, line 1565, in install_observer_listener
File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py”, line 1606, in _observer_install_listener
File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py”, line 1730, in _observer_id_callback
File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/MxDCore.py”, line 294, in _get_object_path
File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py”, line 263, in __init__
File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py”, line 330, in _calculate_path
File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomUtils.py”, line 272, in _find_root_object_path
File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py”, line 1261, in get_root_prop
File “output/Live/mac_universal_64_static/Release/python-bundle/MIDI Remote Scripts/_MxDCore/LomTypes.py”, line 1255, in
RuntimeError
Hello all,
I did a test. I create a very simple control surface (with only one button) and created a script that soloes a track. Nothing else.
Opening Live (without activate any script) I get the following errors. And, the key is not working. It mutes track 3, but I have selected track 1 solo (not relative to session box, folded tracks included)
Bug or installation problems?
I can’t use the software in this way, please help!
You can ignore those 3 messages, they are not related to anything you have setup in your script.
Ableton 12 started complaining about using ‘is’ and ‘is not’. Although its in red and looks like an error, it doesn’t break the script.
I have news, good news, I hope! Tonight I haven’t my SX3, I can do a real test only tomorrow.
But tonight I have noted that the error messages were displayed only opening my (very complicated) liveset, opening a new one gave no errors. So I have started to delete tracks, saving liveset and restart Live, until I have found which track had the problem! I have continued to remove devices, until I have found the source of the problem.
As you can see in the picture, the problem were a original Ableton LFO (turned off!). Deleting it and saving the set, no more error messages!
Tomorrow I will make a real test with my controller, but I am confident that it will work!
I’ll keep you informed
Sign up
User registration is currently not allowed.
You have caused an error at the “_MxDcore” level. This is a level deeper into Live from your midi remote script which your script uses to communicate with the Live Object Model.
Unfortunately it doesn’t tell us what the actual problem is 🙁