Delay headless Rpi QLC startup after bluetoothd
Posted: Thu Jun 08, 2023 1:02 pm
Hello,
I have two midi controllers set up for headless Rpi QLC, one wired (keyboard) and the other bluetooth (stomp box page turner).
The only way I have found for QLC to see the wireless device when the wired device is connected is to restart the service via crontab some tens of seconds after boot. It seems that QLC is starting before the page turner has become available after pairing.
The drawback with the crontab solution is that, apart from being clunky, the gui through a wired screen is lost, which is useful for editing.
I've been poking around around the systems documentation but I can't find a qlcplus.service Unit file to edit which would be the most elegant way of starting QLC once bluetooth is up and running.
Any suggestions?
Thanks in advance,
PV
I have two midi controllers set up for headless Rpi QLC, one wired (keyboard) and the other bluetooth (stomp box page turner).
The only way I have found for QLC to see the wireless device when the wired device is connected is to restart the service via crontab some tens of seconds after boot. It seems that QLC is starting before the page turner has become available after pairing.
The drawback with the crontab solution is that, apart from being clunky, the gui through a wired screen is lost, which is useful for editing.
I've been poking around around the systems documentation but I can't find a qlcplus.service Unit file to edit which would be the most elegant way of starting QLC once bluetooth is up and running.
Any suggestions?
Thanks in advance,
PV