I agree, it does appear that something has grabbed the sound card before Jack has grabbed it, quite possibly CAED.
Also, I'm not sure what build of Linux you're running, but I know for the Debian builds you need to ensure that the user that you're running Jack under is also a member of the audio group. > > > Pedro, > > not sure if this will help, but make sure caed is not running (sudo killall > caed) and then try starting jack from qjackctl. If you get the same > results, then try from qjackctl with the dummy interface. Let us know if it > starts with the dummy interface but not with the sound card. > > all the best, > > drew > > On Mon, Mar 20, 2017 at 10:40 PM, Pedro Picoto <pedro.pic...@gmail.com> > wrote: > > > Sorry for polluting with the topic... > > > > I'm having issues regarding Jack on my fresh RD instalation (I know that > > most of you is agains't Jack but I need it for the versatility it gives me). > > > > Here's what I get on the messages: > > > > "02:34:19.775 Statistics reset. > > > > 02:34:25.806 ALSA connection change. > > > > 02:34:25.811 D-BUS: Service is available (org.jackaudio.service aka > > jackdbus). > > > > connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Ficheiro > > ou directoria inexistente) > > > > attempt to connect to server failed > > > > 02:34:25.901 ALSA connection graph change. > > > > 02:34:34.563 D-BUS: JACK server could not be started. Sorry > > > > connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Ficheiro > > ou directoria inexistente) > > > > attempt to connect to server failed > > > > Tue Mar 21 02:34:34 2017: Starting jack server... > > > > Tue Mar 21 02:34:34 2017: JACK server starting in realtime mode with > > priority 10 > > > > Tue Mar 21 02:34:34 2017: self-connect-mode is "Don't restrict self > > connect requests" > > > > Tue Mar 21 02:34:34 2017: ERROR: Can't load > > "/usr/lib/x86_64-linux-gnu/jack/jack_alsa.so": > > /usr/lib/x86_64-linux-gnu/jack/jack_alsa.so: undefined symbol: > > jack_driver_nt_init > > > > Tue Mar 21 02:34:34 2017: ERROR: Cannot initialize driver > > > > Tue Mar 21 02:34:34 2017: ERROR: JackServer::Open failed with -1 > > > > Tue Mar 21 02:34:34 2017: ERROR: Failed to open server > > > > Tue Mar 21 02:34:35 2017: Saving settings to > > "/home/rivendell/.config/jack/conf.xml" > > ... > > > > 02:34:50.726 Could not connect to JACK server as client. - Overall > > operation failed. - Unable to connect to server. Please check the messages > > window for more info. > > > > connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=Ficheiro > > ou directoria inexistente) > > > > attempt to connect to server failed"" > > > > > > I've searched (a lot) with no suitable solution... > > > > > > Sorry for taking your time with this matter... > > > > > > _______________________________________________ > > Rivendell-dev mailing list > > Rivendell-dev@lists.rivendellaudio.org > > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > > > > > > > -- > Bahamain Or Nuttin - http://www.bahamianornuttin.com > <http://www.bahamianornuttin.com/><hr>_______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
