Open michelemaroni opened 5 days ago
It looks like the Jogg USB device is slow to appear. Maybe it has its own boot period which is slower than most, simple USB devices.
The jack2 service is configured to restart on failure every second. This quickly excedes the restarts permitted in the default period (5 in 5s). Once jack2 service has exceded this limit it stops attempting to restart. Zynthian is dependant on jack2 service, so it cannot operate. Extending the restart time to 2s does not significantly impact availability (zynthian's restart is 5s) and seems to resolve this issue because, when the USB device is available, jack2 finds it and starts then zynthian's next restart works. This may add a few seconds to startup if zynthian fails to start initially because of its 5s restart cycle. (We could probably reduce this to 2s.)
Try changing RestartSec=1
to RestartSec=2
in /etc/systemd/system/jack2.service
then reboot.
I emulated the problem by depowering a USB attached audio card (UMC1820) during boot then powering after zynthian error screen shows. This seems to work.
Please report if this fixes the problem, or at least works around it. If so we could make these changes to the system so that your (cornercase) scenario is resolved.
Describe the issue
HOTONE Jogg Audio interface not available on startup
To Reproduce
Steps to reproduce the behavior:
aplay -l
norlsusb
show the device in the list.jackd -P 70 -s -S -d alsa -d hw:Audio -r 48000 -p 256 -n 2 -X raw
Expected behaviour
The device should be detected, initialized, and activated on startup.
Actual behaviour
The device is not deteced and prevents zynthian-ui and serice from starting.
Screenshots
On startup:
After replugging:
Manually configuring the device as audio interface with
jackd
command after replugging:Additional info
This behavior does not occurs using modep . The device properly starts once configured in the first login wizard.
Configuration
Hardware
System
MIDI & UI
Software