CSS not monitoring MIDI signals in case DAW is opened. Log.txt busy or locked

1.78K viewsCSS Bugs
0
0 Comments

Hello,

I’m experiencing a really anoying problem for which I saw only 1 topic but without any answers –
https://remotify.io/community/question/midi-monitor-doesnt-work-when-abl…

So basically only 1 application can receive MIDI signals from a device (I have both LPD8 and Beatstep) and if another app is opened it would throw an error that the device is already in use.
This prevents me from logging signals from Ableton to CSS and also when making any script changes I have to close CSS first, then open Ableton, then close Ableton and open CSS again.
By watching the vides there is no need to close any app but just reload the Ableton session. But not working for me.

The behavior is the same for any MIDI device and any app – Ableton, CSS, Midi Control Center, MidiView.
Only 1 app can use the device at certain point…

CSS log throws the following error if Ableton is opened first and then CSS

An error occurred creating the file:EBUSY: resource busy or locked, open …..AppDataRoamingAbletonLive 11.0.12PreferencesLog.txt

Windows 10
Ableton 11
CSS 2.6.3


:2: DeprecationWarning: Live.Track.Track.current_output_sub_routing is deprecated since Live 9.7. Please use Live.Track.Track.output_routing_channel instead.
:2: DeprecationWarning: Live.Track.Track.current_output_routing is deprecated since Live 9.7. Please use Live.Track.Track.output_routing_type instead.
:2: DeprecationWarning: Live.Track.Track.current_input_sub_routing is deprecated since Live 9.7. Please use Live.Track.Track.input_routing_channel instead.
:2: DeprecationWarning: Live.Track.Track.current_input_routing is deprecated since Live 9.7. Please use Live.Track.Track.input_routing_type instead.
Traceback (most recent call last):
File "......outputLivewin_64_staticReleasepython-bundleMIDI Remote Scripts_MxDCoreMxDCore.py", line 1320, in update_observer_listener
File "......outputLivewin_64_staticReleasepython-bundleMIDI Remote Scripts_MxDCoreMxDCore.py", line 1343, in _observer_update_listener
File "......outputLivewin_64_staticReleasepython-bundleMIDI Remote Scripts_MxDCoreMxDCore.py", line 1373, in _observer_install_listener
RuntimeError
:
Master-, Group- and Sendtracks have no arrangement clips
Traceback (most recent call last):
File "......outputLivewin_64_staticReleasepython-bundleMIDI Remote Scripts_MxDCoreMxDCore.py", line 1320, in update_observer_listener
File "......outputLivewin_64_staticReleasepython-bundleMIDI Remote Scripts_MxDCoreMxDCore.py", line 1343, in _observer_update_listener
File "......outputLivewin_64_staticReleasepython-bundleMIDI Remote Scripts_MxDCoreMxDCore.py", line 1373, in _observer_install_listener
RuntimeError

admin Changed status to publish
Attached Files:

5 Answers

0
admin 0 Comments

You’re welcome!

I don’t understand the second part of your sentence: ‘So It is normal that only 1 application at time is able to receive MIDI signals from the device and if another one is opened it would receive?

First part: I think it is normal behavior, it makes sense to me that only one software at a time can use the midi port of that device; Or Ableton is using the midi port of your device, or CSS is using the midi port of that device.

Second part: can you explain what you mean by ‘and if another one is opened it would receive’ (if another one of what is opened, it would receive what?)

What script do you mean? Is it ‘selected parameter control’? There is a very good tutorial of that one: https://www.youtube.com/watch?v=-4jT5RRg5Wc

When I read the log file you have sent, I can see:
Live.Track.Track.current_output_sub_routing is deprecated since Live 9.7. Please use Live.Track.Track.output_routing_channel instead.
I am guessing that is your culprit. Since you are using Ableton 11; swap out the deprecated code in your script with the new one.

Good luck!

admin Changed status to publish
Attached Files:
You are viewing 1 out of 5 answers, click here to view all answers.

Categories