On Thu, April 13, 2023 1:34 pm, Bill Purvis wrote: > However, When it came to setting up the audio side, I wanted to run > Jack(D2/DBUS) and use Qjackctl > for initial setting up. I'm hoping to dispense with Qjackctl once its > all working, though the patchbay > might keep it in. I want a system that comes up headless (normally) so > the organist just switches on, > waits for a couple of minutes for it to start, then starts playing. If the system is going to be headless, I would recommend going straight to CLI programs for manipulating connections, so you don't get sucked into relying on a GUI tool that will then make it much more difficult to go truly headless. Break your problem down into bite size pieces. First make sure that jackd or jackdbus is starting correctly. That implies someway to log output from jackd, since presumably the final configuration will be starting jackd from a script of some kind (systemd unit file, autostart script, init script, ...). > I'm having great difficulty in getting Qjackctl and Jack to start > reliably, I've tried jackd2 and jackdbus > (from the standard Ubuntu repositories) and Qjackctl nearly always fails > with messages saying it can't > contact jack: 'Server communications error, plesae check the message > window for more info'. > The window then says 'Cannot read socket fd = 36 err = Success' which > seems contradictory! How are you starting jackd or jackdbus? Is it possible that jackd is just not finished initializing before you started qjackctl? > If anyone can help I'd like opinions on whether I should be pushing for > jackd2 or jackdbus. That depends on whether you would like to use dbus to control the jack server. If you are not using some kind of dbus control program to manipulate the jack server I do not think it will matter which you use. > The idea is to have a startup script which starts jack, then qjackctl, > then the organ software (GrandOrgue). > So far it's a mess. In the archives are some threads about starting jackd automatically when the system starts up, but I think that was using systemd unit files, not using an automatically logged in standard user account. Getting jackd to run without a user account logged in is an additional level of complication you don't want to deal with. It is not obvious from your description if you are using a script already to start jack server, or if you started by hand, if there was already an existing sound server running (PulseAudio or Wireplumber). More details including output of jackd when started would help. -- Chris _______________________________________________ Linux-audio-user mailing list -- linux-audio-user@xxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to linux-audio-user-leave@xxxxxxxxxxxxxxxxxxxx
