6 Aug
2016
6 Aug
'16
11:12 p.m.
I just installed Ubuntu trusty (on crouton on an Acer Chromebook), and am
trying to get sound going (so I can run Super-Collider.)
Upon the advice of various webpages I've come across that discuss
installation of Super-Collider, I've tried:
- removing pulseaudio
- adding myself to the "hwaudio" group
- adding '@audio' entries to /etc/security/limits.conf
But I always get "Could not connect to JACK server as client" when I run
qjackctl.
This is the output I get when I run qjackctl. I've tried changing the
interface to both 'cras' and 'hw:DAISY12S', but neither work.
23:54:23.518 Patchbay deactivated.
23:54:23.585 Statistics reset.
23:54:23.598 ALSA connection change.
23:54:23.643 D-BUS: Service not available (org.jackaudio.service aka
jackdbus).
23:54:23.667 JACK is starting...
23:54:23.668 /usr/bin/jackd -dalsa -dcras -r44100 -p1024 -n2
23:54:23.686 ALSA connection graph change.
jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn
and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... cras|cras|1024|2|44100|0|0|nomon|swmeter|-|32bit
Couldn't connect to cras.
control open "cras" (Operation not permitted)
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: cannot set hardware parameters for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
(qjackctl:13298): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion
'GTK_IS_WIDGET (widget)' failed
(qjackctl:13298): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion
'GTK_IS_WIDGET (widget)' failed
23:54:23.980 JACK was started with PID=13310.
23:54:24.042 JACK was stopped successfully.
My apologies if I'm asking this in the wrong place, or if I'm not giving
enough info. I'll ask elsewhere if that's more appropriate. But any
advice or suggestions would be much appreciated!
6 Aug
6 Aug
11:16 p.m.
[woops, I forgot to add a subject line before hitting Send. *Very* sorry!]
On Sun, Aug 7, 2016 at 12:12 AM, Tom Law <tomlaw(a)bigsphinx.com> wrote:
I just installed Ubuntu trusty (on crouton on an Acer
Chromebook), and am
trying to get sound going (so I can run Super-Collider.)
Upon the advice of various webpages I've come across that discuss
installation of Super-Collider, I've tried:
- removing pulseaudio
- adding myself to the "hwaudio" group
- adding '@audio' entries to /etc/security/limits.conf
But I always get "Could not connect to JACK server as client" when I run
qjackctl.
This is the output I get when I run qjackctl. I've tried changing the
interface to both 'cras' and 'hw:DAISY12S', but neither work.
23:54:23.518 Patchbay deactivated.
23:54:23.585 Statistics reset.
23:54:23.598 ALSA connection change.
23:54:23.643 D-BUS: Service not available (org.jackaudio.service aka
jackdbus).
23:54:23.667 JACK is starting...
23:54:23.668 /usr/bin/jackd -dalsa -dcras -r44100 -p1024 -n2
23:54:23.686 ALSA connection graph change.
jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn
and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... cras|cras|1024|2|44100|0|0|nomon|swmeter|-|32bit
Couldn't connect to cras.
control open "cras" (Operation not permitted)
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: cannot set hardware parameters for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
(qjackctl:13298): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion
'GTK_IS_WIDGET (widget)' failed
(qjackctl:13298): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion
'GTK_IS_WIDGET (widget)' failed
23:54:23.980 JACK was started with PID=13310.
23:54:24.042 JACK was stopped successfully.
My apologies if I'm asking this in the wrong place, or if I'm not giving
enough info. I'll ask elsewhere if that's more appropriate. But any
advice or suggestions would be much appreciated!
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
7 Aug
7 Aug
5:49 a.m.
New subject: [Jack-Devel] Could not connect to JACK server
On Sun, Aug 07, 2016 at 12:12:10AM -0400, Tom Law wrote:
I just installed Ubuntu trusty (on crouton on an Acer
Chromebook), and am
trying to get sound going (so I can run Super-Collider.)
Upon the advice of various webpages I've come across that discuss
installation of Super-Collider, I've tried:
- removing pulseaudio
- adding myself to the "hwaudio" group
- adding '@audio' entries to /etc/security/limits.conf
Don't know if this is the reason for the problem, but '@audio' entries
in /etc/security/limits.conf will only apply to members of "audio"
group, not "hwaudio".
John
9:19 p.m.
New subject: [Jack-Devel] Could not connect to JACK server
- adding
'@audio' entries to /etc/security/limits.conf
Don't know if this is the reason for the problem, but '@audio' entries
in /etc/security/limits.conf will only apply to members of "audio"
group, not "hwaudio". 
6:17 a.m.
On 08/06/2016 11:12 PM, Tom Law wrote:
# removing pulseaudio
#
I can't help you with your jack problem but I can certainly help with
pulseaudio. Removing pulse can be a big problem because so much is tied
into it now. You can break things that don't even appear to be
related. I just upgraded from Kubuntu 14.04 (Trusty) to 16.04 and, of
course, pulseaudio took over my system and caused me all kinds of
problems with jack, riffstation, and a bunch of other things (I've got
an ICE1712 based sound card and external gear). The easiest and safest
way to disable pulseaudio in Ubuntu is to open a konsole and do the
following:
sudo chmod 400 /usr/bin/pulseaudio
then reboot. No more pulse, no broken packages.
Cheers,
Jan
6:42 a.m.
On 08/07/2016 07:17 AM, Jan Depner wrote:
On 08/06/2016 11:12 PM, Tom Law wrote:
> # removing pulseaudio
...
an ICE1712 based sound card and external gear). The
easiest and safest
way to disable pulseaudio in Ubuntu is to open a konsole and do the
following:
sudo chmod 400 /usr/bin/pulseaudio
Or ...
pavucontrol
-> Configuration
Set all devices to "Off" ...
To tie pulse back into the jack graph there are
module-alsa-sink
module-alsa-source
or, what I prefer because it loads/unloads when jack starts/stops is:
module-jackdbus-detect
//
3058
days inactive
3059
days old
jackaudio@lists.linuxaudio.org
5 comments
5 participants
participants (5)
-
David Santamauro -
Jan Depner -
John Rigg -
Tom Law -
tomlaw