CSS not monitoring MIDI signals in case DAW is opened. Log.txt busy or locked
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
Hello peterpavlov,
You can find some ‘good to know’ info about Ableton 11 and CSS at https://remotify.io/community/question/script-reload-fails-ableton-live-11
I guess there is a misunderstanding about ‘midi monitoring’;
You mention: ‘This prevents me from logging signals from Ableton to CSS’
That is not the purpose of ‘midi monitoring’. Ableton does not send midi to CSS. Your midi controller (LPD8 or Beatstep) sends MIDI info to Ableton and the script you create with CSS translates those MIDI signals into code Ableton understands.
About CSS ‘midi monitoring’; if you want to monitor what your midi controller does, you should indeed close Ableton, that is true. (for Windows at least, I don’t know about Apple)
I guess it kind of makes sense that if Ableton is using the midi port of your midi controller, it is not available for another program.
In practice, till now, I have only used/needed ‘midi monitoring’ when setting up a controller template. And since you only do that once for each controller, I don’t mind that so much. There is no need for Ableton to run at that time anyway 😉
I hope you got some worthwhile info.
Enjoy Remotify!
Sign up
User registration is currently not allowed.