jack not working says cannot start server
Moderators: MattKingUSA, khz
-
- Established Member
- Posts: 5
- Joined: Thu Apr 02, 2015 4:36 pm
jack not working says cannot start server
Hi. I have a Steinberg MI4 soundcard, and system sees it in command line, and I can hear system sound through it. But when I try to start Jack with ALSA, it says it cannot connect to server. Any help would be appreciated as I am banging my head against the wall getting this to work.
Here is the message:
21:17:26.196 Patchbay deactivated.
21:17:26.242 Statistics reset.
21:17:26.249 ALSA connection change.
21:17:26.260 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
21:17:26.279 ALSA connection graph change.
Here is the message:
21:17:26.196 Patchbay deactivated.
21:17:26.242 Statistics reset.
21:17:26.249 ALSA connection change.
21:17:26.260 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
21:17:26.279 ALSA connection graph change.
-
- Established Member
- Posts: 5
- Joined: Thu Apr 02, 2015 4:36 pm
Re: jack not working says cannot start server
By the way, I have tried this with Ubuntu Studio, but now have the newest KX Studio installed.
Will this work with "dummy" enabled? I think I tried that to no avail.
Will this work with "dummy" enabled? I think I tried that to no avail.
-
- Established Member
- Posts: 5
- Joined: Thu Apr 02, 2015 4:36 pm
Re: jack not working says cannot start server
OK. So if I select soundcard "MI4-HW1" I get this error below. If I select soundcard "MI4-HW-0,1" I get the previously posted error.
21:24:24.899 Patchbay deactivated.
21:24:24.916 Statistics reset.
21:24:24.929 ALSA connection change.
21:24:24.942 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
21:24:24.960 ALSA connection graph change.
21:24:30.713 D-BUS: JACK server could not be started. Sorry
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
Mon Apr 6 21:24:30 2015: Starting jack server...
Mon Apr 6 21:24:30 2015: JACK server starting in realtime mode with priority 10
Mon Apr 6 21:24:30 2015: Acquired audio card Audio1
Mon Apr 6 21:24:30 2015: creating alsa driver ... hw:MI4,0|hw:MI4,0|1024|2|44100|0|0|nomon|swmeter|-|32bit
Mon Apr 6 21:24:30 2015: Using ALSA driver USB-Audio running on card 1 - Steinberg MI4 at usb-0000:00:1d.0-2, full speed
Mon Apr 6 21:24:30 2015: configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
Mon Apr 6 21:24:30 2015: ALSA: final selected sample format for capture: 24bit little-endian
Mon Apr 6 21:24:30 2015: ALSA: use 2 periods for capture
Mon Apr 6 21:24:30 2015: ALSA: final selected sample format for playback: 24bit little-endian
Mon Apr 6 21:24:30 2015: ALSA: use 2 periods for playback
Mon Apr 6 21:24:30 2015: ERROR: ALSA: could not start playback (Broken pipe)
Mon Apr 6 21:24:30 2015: ERROR: Cannot start driver
Mon Apr 6 21:24:30 2015: ERROR: JackServer::Start() failed with -1
Mon Apr 6 21:24:30 2015: ERROR: Failed to start server
Mon Apr 6 21:24:30 2015: Released audio card Audio1
Mon Apr 6 21:24:32 2015: Saving settings to "/home/nathan/.config/jack/conf.xml" ...
21:24:38.591 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
21:24:24.899 Patchbay deactivated.
21:24:24.916 Statistics reset.
21:24:24.929 ALSA connection change.
21:24:24.942 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
21:24:24.960 ALSA connection graph change.
21:24:30.713 D-BUS: JACK server could not be started. Sorry
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
Mon Apr 6 21:24:30 2015: Starting jack server...
Mon Apr 6 21:24:30 2015: JACK server starting in realtime mode with priority 10
Mon Apr 6 21:24:30 2015: Acquired audio card Audio1
Mon Apr 6 21:24:30 2015: creating alsa driver ... hw:MI4,0|hw:MI4,0|1024|2|44100|0|0|nomon|swmeter|-|32bit
Mon Apr 6 21:24:30 2015: Using ALSA driver USB-Audio running on card 1 - Steinberg MI4 at usb-0000:00:1d.0-2, full speed
Mon Apr 6 21:24:30 2015: configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
Mon Apr 6 21:24:30 2015: ALSA: final selected sample format for capture: 24bit little-endian
Mon Apr 6 21:24:30 2015: ALSA: use 2 periods for capture
Mon Apr 6 21:24:30 2015: ALSA: final selected sample format for playback: 24bit little-endian
Mon Apr 6 21:24:30 2015: ALSA: use 2 periods for playback
Mon Apr 6 21:24:30 2015: ERROR: ALSA: could not start playback (Broken pipe)
Mon Apr 6 21:24:30 2015: ERROR: Cannot start driver
Mon Apr 6 21:24:30 2015: ERROR: JackServer::Start() failed with -1
Mon Apr 6 21:24:30 2015: ERROR: Failed to start server
Mon Apr 6 21:24:30 2015: Released audio card Audio1
Mon Apr 6 21:24:32 2015: Saving settings to "/home/nathan/.config/jack/conf.xml" ...
21:24:38.591 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
Re: jack not working says cannot start server
Same for me. qjackctl cannot see the audio connections (connect button -> audio tab, nothing in there? Under the alsa tab I only see midi related input and outputs, also the one of MI4).
However when using 'audio-recorder' I can record using MI4 without problem! There I can select MI4 as input device, same as in my ubuntu audio settings window.
Can anyone recommend a DAW that uses the same underlying technique as audio-recorder and ubuntu sound setup? Or anyone has some magic to make jack work?
Thanks!
Marcel
However when using 'audio-recorder' I can record using MI4 without problem! There I can select MI4 as input device, same as in my ubuntu audio settings window.
Can anyone recommend a DAW that uses the same underlying technique as audio-recorder and ubuntu sound setup? Or anyone has some magic to make jack work?
Thanks!
Marcel
-
- Established Member
- Posts: 29
- Joined: Tue Nov 28, 2017 12:30 pm
Re: jack not working says cannot start server
marcel wrote:qjackctl cannot see the audio connections (connect button -> audio tab, nothing in there?
connections windows in qjackctl wont show anything until the jack server is up running.
Which jack do you have installed..? There are more than one. My distro have 3 different jack packages. http://www.jackaudio.org/downloads/ they're a bit different. it is most likely something in your settings causing the problem. You could screenshot all the tabs in your qjackctl settings, it would be easier for people to see what is going on and help.
Are you a member of the audio group on your system?
Can you start the jack server from commandline? qjackctl is just one of the GUI's (and the one most people heard of), that can control the server, but there are others also, and you can even tell it what to do your self from commandline or homemade scripts. I usually test mine without qjackctl to see if it will start or not, before going further with troubleshooting. 9 out of 10 times for me it is just some setting/human error in qjackctl and the server starts fine on its own when told from commandline.
I have a logfile in ~/.log/jack/
a qjackctl.conf file in ~/.config/rncbc.org/
and a ~/.jackdrc.
They might be placed differently in your distro. Look for them and see what info they can give you.
PS. You have hijacked and necro-bumped an old thread btw.
"Arch/i3-wm/Bitwig/Renoise/Guitarix/Airwave/a couple of winVST's"
"i7-6700K 4ghz, gtx910ti, 16gb ram" + "X201s-i7-640LM 2.13ghz, 8gb ram"
"Presonus 22vsl + Scarlett 2i2 2.gen."
"i7-6700K 4ghz, gtx910ti, 16gb ram" + "X201s-i7-640LM 2.13ghz, 8gb ram"
"Presonus 22vsl + Scarlett 2i2 2.gen."
Re: jack not working says cannot start server
Hi there,
Thank you so much for your reply!
This is the version of jackd:
$ jackd -V
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp 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
no message buffer overruns
no message buffer overruns
no message buffer overruns
jackdmp version 1.9.11 tmpdir /dev/shm protocol 8
Tab 1 under settings: Tab 2 under settings: I am a member of the realtime group, as was suggested by documentation of jack:
http://jackaudio.org/faq/linux_rt_config.html
I have attached the log file jackdbus.log to this thread, here is the link: https://www.linuxmusicians.com/download ... ew&id=1299
Inlined the xml of the conf.xml:
And then the qjackctl.conf file:
This I get when starting jackd from the commandline, looked up a few things of which args to use, standard internal card works, but other device MI4 fails:
Following command gave me why I used -dhw:2,0
Looks like I need to combine the card number and the device number to get to hw:2,0.
Maybe interesting too, when running aplay -L I get this detailed info:
Can you tell me how to run jackd with this input?
Thanks again!
Thank you so much for your reply!
This is the version of jackd:
$ jackd -V
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp 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
no message buffer overruns
no message buffer overruns
no message buffer overruns
jackdmp version 1.9.11 tmpdir /dev/shm protocol 8
Tab 1 under settings: Tab 2 under settings: I am a member of the realtime group, as was suggested by documentation of jack:
http://jackaudio.org/faq/linux_rt_config.html
I have attached the log file jackdbus.log to this thread, here is the link: https://www.linuxmusicians.com/download ... ew&id=1299
Inlined the xml of the conf.xml:
Code: Select all
<?xml version="1.0"?>
<!--
JACK settings, as persisted by D-Bus object.
You probably don't want to edit this because
it will be overwritten next time jackdbus saves.
-->
<!-- Wed Dec 20 22:54:19 2017 -->
<jack>
<engine>
<option name="driver">alsa</option>
<option name="realtime">true</option>
<option name="verbose">false</option>
<option name="client-timeout">500</option>
</engine>
<drivers>
<driver name="alsa">
<option name="device">hw:0</option>
<option name="capture">hw:MI4,0</option>
<option name="playback">hw:MI4,0</option>
<option name="rate">44100</option>
<option name="period">1024</option>
<option name="nperiods">2</option>
<option name="hwmon">false</option>
<option name="hwmeter">false</option>
<option name="duplex">true</option>
<option name="softmode">false</option>
<option name="monitor">false</option>
<option name="dither">n</option>
<option name="shorts">false</option>
</driver>
<driver name="loopback">
</driver>
<driver name="net">
</driver>
<driver name="netone">
</driver>
<driver name="firewire">
</driver>
<driver name="dummy">
</driver>
<driver name="alsarawmidi">
</driver>
</drivers>
<internals>
<internal name="netmanager">
</internal>
<internal name="profiler">
</internal>
<internal name="audioadapter">
</internal>
<internal name="netadapter">
</internal>
</internals>
</jack>
Code: Select all
[Defaults]
ConnectionsTabPage=0
MessagesStatusTabPage=0
PatchbayPath=
SessionSaveVersion=true
[Geometry]
qjackctlConnectionsForm\geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x2\0\0\0\0\b_\0\0\x1\xab\0\0\v)\0\0\x3\x4\0\0\b_\0\0\x1\xab\0\0\v)\0\0\x3\x4\0\0\0\
x1\0\0\0\0\x6@)
qjackctlConnectionsForm\visible=false
qjackctlMainForm\geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x2\0\0\0\0\x3\x9f\0\0\x1\xf8\0\0\x5z\0\0\x2p\0\0\x3\x9f\0\0\x2\r\0\0\x5z\0\0\x2p\0\0\0\0\0
\0\0\0\a\x80)
qjackctlMainForm\visible=true
qjackctlMessagesStatusForm\geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x2\0\0\0\0\x1\xbe\0\0\0\xc8\0\0\x6\x6\0\0\x2\x9e\0\0\x1\xbe\0\0\0\xdd\0\0\x6\x6\
0\0\x2\x9e\0\0\0\0\0\0\0\0\a\x80)
qjackctlMessagesStatusForm\visible=true
qjackctlPatchbayForm\geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x2\0\0\0\0\x1\xf6\0\0\0\xd3\0\0\x4\xef\0\0\x2\x1b\0\0\x1\xf6\0\0\0\xd3\0\0\x4\xef\0\0\
x2\x1b\0\0\0\0\0\0\0\0\a\x80)
qjackctlPatchbayForm\visible=false
qjackctlSessionForm\geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x2\0\0\0\0\x3\a\0\0\x2q\0\0\x5\r\0\0\x4\x17\0\0\x3\a\0\0\x2q\0\0\x5\r\0\0\x4\x17\0\0\0\
0\0\0\0\0\a\x80)
qjackctlSessionForm\visible=false
[History]
MessagesLogPathComboBox\Item1=qjackctl.log
ServerConfigNameComboBox\Item1=.jackdrc
ServerNameComboBox\Item1=(default)
ServerPrefixComboBox\Item1=/usr/bin/jackd
ServerPrefixComboBox\Item2=jackd
ServerPrefixComboBox\Item3=jackdmp
ServerPrefixComboBox\Item4=jackstart
XrunRegexComboBox\Item1=xrun of at least ([0-9|\\.]+) msecs
[Options]
ActivePatchbay=false
ActivePatchbayPath=
ActivePatchbayReset=false
AliasesEditing=false
AliasesEnabled=false
AlsaSeqEnabled=true
BaseFontSize=0
BezierLines=false
ConnectionsFont="Sans Serif,10,-1,5,75,0,0,0,0,0"
ConnectionsIconSize=0
DBusEnabled=true
DisplayBlink=true
DisplayEffect=true
DisplayFont1="Sans Serif,12,-1,5,75,0,0,0,0,0"
DisplayFont2="Sans Serif,6,-1,5,75,0,0,0,0,0"
JackClientPortAlias=0
JackClientPortMetadata=false
JackDBusEnabled=true
KeepOnTop=false
LeftButtons=true
MessagesFont="Monospace,8,-1,5,75,0,0,0,0,0"
MessagesLimit=true
MessagesLimitLines=1000
MessagesLog=false
MessagesLogPath=qjackctl.log
PostShutdownScript=false
PostShutdownScriptShell=
PostStartupScript=false
PostStartupScriptShell=
QueryClose=true
QueryDisconnect=true
QueryShutdown=true
RightButtons=true
ServerConfig=true
ServerConfigName=.jackdrc
ServerConfigTemp=false
ShutdownScript=false
ShutdownScriptShell=
Singleton=true
StartJack=false
StartupScript=false
StartupScriptShell=
StdoutCapture=true
StopJack=true
SystemTray=false
SystemTrayQueryClose=true
TextLabels=true
TimeDisplay=0
TimeFormat=0
TransportButtons=true
XrunRegex=xrun of at least ([0-9|\\.]+) msecs
[Presets]
DefPreset=(default)
Preset1=mi4
[Program]
Version=0.4.2
[Settings]
Audio=0
Chan=0
Dither=0
Driver=alsa
Frames=1024
HWMeter=false
HWMon=false
IgnoreHW=false
InChannels=0
InDevice="hw:MI4,0"
InLatency=0
Interface=
MidiDriver=none
Monitor=false
NoMemLock=false
OutChannels=0
OutDevice="hw:MI4,0"
OutLatency=0
Periods=2
PortMax=256
Priority=5
Realtime=true
SampleRate=44100
Server=/usr/bin/jackd
ServerName=
ServerSuffix=
Shorts=false
SoftMode=false
StartDelay=2
Timeout=500
UnlockMem=false
Verbose=false
Wait=21333
WordLength=16
mi4\Audio=0
mi4\Chan=0
mi4\Dither=0
mi4\Driver=alsa
mi4\Frames=1024
mi4\HWMeter=false
mi4\HWMon=false
mi4\IgnoreHW=false
mi4\InChannels=0
mi4\InDevice=
mi4\InLatency=0
mi4\Interface=hw:MI4
mi4\MidiDriver=none
mi4\Monitor=true
mi4\NoMemLock=true
mi4\OutChannels=0
mi4\OutDevice=
mi4\OutLatency=0
mi4\Periods=3
mi4\PortMax=256
mi4\Priority=5
mi4\Realtime=true
mi4\SampleRate=44100
mi4\Server=/usr/bin/jackd
mi4\ServerName=
mi4\ServerSuffix=
mi4\Shorts=false
mi4\SoftMode=false
mi4\StartDelay=2
mi4\Timeout=500
mi4\UnlockMem=false
mi4\Verbose=false
mi4\Wait=21333
mi4\WordLength=16
[Splitter]
AlsaConnectView\sizes=38, 20, 38
AudioConnectView\sizes=269, 90, 269
InfraClientSplitter\sizes=12, 12
MidiConnectView\sizes=38, 20, 38
PatchbayView\sizes=252, 42, 252
This I get when starting jackd from the commandline, looked up a few things of which args to use, standard internal card works, but other device MI4 fails:
Code: Select all
$ jackd -r -dalsa -dhw:2,0 -r44100
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp 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
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in non-realtime mode
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio2
creating alsa driver ... hw:2,0|hw:2,0|1024|2|44100|0|0|nomon|swmeter|-|32bit
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format
ALSA: use 2 periods for playback
ALSA: could not start playback (Broken pipe)
Cannot start driver
JackServer::Start() failed with -1
Failed to start server
Released audio card Audio2
audio_reservation_finish
Following command gave me why I used -dhw:2,0
Code: Select all
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: MID [HDA Intel MID], device 0: 92HD73C1X5 Analog [92HD73C1X5 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: MI4 [MI4], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
Maybe interesting too, when running aplay -L I get this detailed info:
Code: Select all
default
Playback/recording through the PulseAudio sound server
null
Discard all samples (playback) or generate zero samples (capture)
pulse
PulseAudio Sound Server
sysdefault:CARD=MID
HDA Intel MID, 92HD73C1X5 Analog
Default Audio Device
front:CARD=MID,DEV=0
HDA Intel MID, 92HD73C1X5 Analog
Front speakers
surround21:CARD=MID,DEV=0
HDA Intel MID, 92HD73C1X5 Analog
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=MID,DEV=0
HDA Intel MID, 92HD73C1X5 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=MID,DEV=0
HDA Intel MID, 92HD73C1X5 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=MID,DEV=0
HDA Intel MID, 92HD73C1X5 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=MID,DEV=0
HDA Intel MID, 92HD73C1X5 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=MID,DEV=0
HDA Intel MID, 92HD73C1X5 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
dmix:CARD=MID,DEV=0
HDA Intel MID, 92HD73C1X5 Analog
Direct sample mixing device
dsnoop:CARD=MID,DEV=0
HDA Intel MID, 92HD73C1X5 Analog
Direct sample snooping device
hw:CARD=MID,DEV=0
HDA Intel MID, 92HD73C1X5 Analog
Direct hardware device without any conversions
plughw:CARD=MID,DEV=0
HDA Intel MID, 92HD73C1X5 Analog
Hardware device with all software conversions
hdmi:CARD=HDMI,DEV=0
HDA ATI HDMI, HDMI 0
HDMI Audio Output
dmix:CARD=HDMI,DEV=3
HDA ATI HDMI, HDMI 0
Direct sample mixing device
dsnoop:CARD=HDMI,DEV=3
HDA ATI HDMI, HDMI 0
Direct sample snooping device
hw:CARD=HDMI,DEV=3
HDA ATI HDMI, HDMI 0
Direct hardware device without any conversions
plughw:CARD=HDMI,DEV=3
HDA ATI HDMI, HDMI 0
Hardware device with all software conversions
sysdefault:CARD=MI4
MI4, USB Audio
Default Audio Device
front:CARD=MI4,DEV=0
MI4, USB Audio
Front speakers
surround21:CARD=MI4,DEV=0
MI4, USB Audio
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=MI4,DEV=0
MI4, USB Audio
4.0 Surround output to Front and Rear speakers
surround41:CARD=MI4,DEV=0
MI4, USB Audio
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=MI4,DEV=0
MI4, USB Audio
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=MI4,DEV=0
MI4, USB Audio
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=MI4,DEV=0
MI4, USB Audio
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=MI4,DEV=0
MI4, USB Audio
IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=MI4,DEV=0
MI4, USB Audio
Direct sample mixing device
dsnoop:CARD=MI4,DEV=0
MI4, USB Audio
Direct sample snooping device
hw:CARD=MI4,DEV=0
MI4, USB Audio
Direct hardware device without any conversions
plughw:CARD=MI4,DEV=0
MI4, USB Audio
Hardware device with all software conversions
Thanks again!
- Attachments
-
- jackdbus.log
- (20.11 KiB) Downloaded 108 times
-
- Established Member
- Posts: 381
- Joined: Sun May 28, 2017 3:52 pm
Re: jack not working says cannot start server
Did you try just "-dhw:2" (note the dropped ",0" for the subdevice) or maybe even better "-dhw:MI4" ?
Reaper/KDE/Archlinux. i7-2600k/16GB + i7-4700HQ/16GB, RME Multiface/Babyface, Behringer X32, WA273-EQ, 2 x WA-412, ADL-600, Tegeler TRC, etc For REAPER on Linux information: https://wiki.cockos.com/wiki/index.php/REAPER_for_Linux
-
- Established Member
- Posts: 897
- Joined: Thu Sep 11, 2014 3:04 pm
- Has thanked: 71 times
- Been thanked: 64 times
Re: jack not working says cannot start server
#1 - Has pulseaudio been killed and disabled from respawning? Ensure it is not running, nor respawning, before continuing.
#2 - For the purposes of experimentation to get jack working, back up your existing .asoundrc file and then remove the existing .asoundrc file before continuing.
#3 - You are using a USB soundcard, therefore you probably shouldn't be using period setting of "2", rather try using "3"
#4 - Check whether jackdbus is running, if yes, kill the jackdbus process before continuing.
#5 - Try starting jack from the shell, like this.
You may need to try out some variations on the device name as mentioned in the post above.
With the .asoundrc file removed, you can try running aplay -l again to see what device name or card number it returns.
#2 - For the purposes of experimentation to get jack working, back up your existing .asoundrc file and then remove the existing .asoundrc file before continuing.
#3 - You are using a USB soundcard, therefore you probably shouldn't be using period setting of "2", rather try using "3"
#4 - Check whether jackdbus is running, if yes, kill the jackdbus process before continuing.
#5 - Try starting jack from the shell, like this.
Code: Select all
jackd -dalsa -r44100 -p1024 -n3 -D -Chw:MI4,0 -Phw:MI4,0
With the .asoundrc file removed, you can try running aplay -l again to see what device name or card number it returns.
Some Focal / 20.04 audio packages and resources https://midistudio.groups.io/g/linuxaudio
-
- Established Member
- Posts: 29
- Joined: Tue Nov 28, 2017 12:30 pm
Re: jack not working says cannot start server
You are using the jack called jack2
You can also control it with other commands.
Examples: etc..
Try writing jack_ and hit your tab button (auto-completion) to see how many commands there are.. there is a man page for most of them.
If you do a you should see either a jackdbus or a jack2dbus running. It will usually start the moment you do a jack_control status. The jackdbus will still show up even though you have stopped the jack server.
If you do a it should be removed from your process list.
try deleting your ~/.jackdrc file.. and ~/.config/rncbc.org/QjackCtl.conf.. or move them to a safe place if you wanna keep them. Qjackctl will create a new ones. It's simple way to start over.
My Advanced tab in qjackctl has jackd in the server prefix, and everything else is set to default.. (unless I use both my soundcards at the same time). In my parameters tab I have Drivers=Alsa, Realtime=yes Midi Driver=none and here in this tab I have selected my soundcard I want to use. Don't worry if it shows up twice on the list, just try both.
My Misc tab goes like this Notice I don't like qjackctl to start/stop my server (that way I can kill qjackctl without crashing my jackserver, or quickly switch over to Carla Patchbay instead without closing restarting anything), and I like the D-Bus settings. This is just personal preferences. On some jack installs you only need one of the D-Bus fields checked.
One thing that can usually screw up my jack is when I have unplugged my USB soundcards and forget to tell qjackctl to use the onboard card instead before hitting the start button in qjackctl. Things usually go to hell from there. And I spend 10 minutes screaming and pulling my hair out.
Always remember that qjackctl is just a gui, not the actual jackserver.
You can also control it with other commands.
Examples:
Code: Select all
jack_control status
jack_control start
jack_control stop
Try writing jack_ and hit your tab button (auto-completion) to see how many commands there are.. there is a man page for most of them.
If you do a
Code: Select all
ps -A |grep jack
If you do a
Code: Select all
jack_control exit
try deleting your ~/.jackdrc file.. and ~/.config/rncbc.org/QjackCtl.conf.. or move them to a safe place if you wanna keep them. Qjackctl will create a new ones. It's simple way to start over.
My Advanced tab in qjackctl has jackd in the server prefix, and everything else is set to default.. (unless I use both my soundcards at the same time). In my parameters tab I have Drivers=Alsa, Realtime=yes Midi Driver=none and here in this tab I have selected my soundcard I want to use. Don't worry if it shows up twice on the list, just try both.
My Misc tab goes like this Notice I don't like qjackctl to start/stop my server (that way I can kill qjackctl without crashing my jackserver, or quickly switch over to Carla Patchbay instead without closing restarting anything), and I like the D-Bus settings. This is just personal preferences. On some jack installs you only need one of the D-Bus fields checked.
One thing that can usually screw up my jack is when I have unplugged my USB soundcards and forget to tell qjackctl to use the onboard card instead before hitting the start button in qjackctl. Things usually go to hell from there. And I spend 10 minutes screaming and pulling my hair out.
Always remember that qjackctl is just a gui, not the actual jackserver.
"Arch/i3-wm/Bitwig/Renoise/Guitarix/Airwave/a couple of winVST's"
"i7-6700K 4ghz, gtx910ti, 16gb ram" + "X201s-i7-640LM 2.13ghz, 8gb ram"
"Presonus 22vsl + Scarlett 2i2 2.gen."
"i7-6700K 4ghz, gtx910ti, 16gb ram" + "X201s-i7-640LM 2.13ghz, 8gb ram"
"Presonus 22vsl + Scarlett 2i2 2.gen."
Re: jack not working says cannot start server
It doesn't make a difference. The thing where it fails is pretty consistent:Jack Winter wrote:Did you try just "-dhw:2" (note the dropped ",0" for the subdevice) or maybe even better "-dhw:MI4" ?
Code: Select all
ALSA: use 2 periods for playback
ALSA: could not start playback (Broken pipe)
Cannot start driver
Re: jack not working says cannot start server
=> #1: pulseaudio is running indeed, when killing it after a few seconds it automatically comes up again.asbak wrote:#1 - Has pulseaudio been killed and disabled from respawning? Ensure it is not running, nor respawning, before continuing.
#2 - For the purposes of experimentation to get jack working, back up your existing .asoundrc file and then remove the existing .asoundrc file before continuing.
#3 - You are using a USB soundcard, therefore you probably shouldn't be using period setting of "2", rather try using "3"
#4 - Check whether jackdbus is running, if yes, kill the jackdbus process before continuing.
#5 - Try starting jack from the shell, like this.
You may need to try out some variations on the device name as mentioned in the post above.Code: Select all
jackd -dalsa -r44100 -p1024 -n3 -D -Chw:MI4,0 -Phw:MI4,0
With the .asoundrc file removed, you can try running aplay -l again to see what device name or card number it returns.
=> #2: I don't know where .asoundrc is located. I searched through the complete file system but could not find it. So conclusion: there is no .asoundrc
=> #3: I followed your advice here using -n3 as alsa/jackd parameter, which gives exactly the same error
=> #4: no jackdbus running
=> #5: tried the command as you suggested but it gave exactly the same error:
Code: Select all
$ jackd -dalsa -r44100 -p1024 -n3 -D -Chw:MI4,0 -Phw:MI4,0
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp 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
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio2
creating alsa driver ... hw:MI4,0|hw:MI4,0|1024|3|44100|0|0|nomon|swmeter|-|32bit
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format
ALSA: use 3 periods for playback
ALSA: could not start playback (Broken pipe)
Cannot start driver
JackServer::Start() failed with -1
Failed to start server
Released audio card Audio2
audio_reservation_finish
Re: jack not working says cannot start server
As a reply to last post by Brynildsen:
Calling "jack_control start" and "jack_control exit" indeed starts and stops the "/usr/bin/jackdbus auto" process.
I tried all settings as explained, removed files you said, restarted qjackctl and still the same errors:
Calling "jack_control start" and "jack_control exit" indeed starts and stops the "/usr/bin/jackdbus auto" process.
I tried all settings as explained, removed files you said, restarted qjackctl and still the same errors:
Code: Select all
13:58:28.342 Statistics reset.
13:58:28.357 ALSA connection change.
13:58:28.363 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
13:58:28.442 ALSA connection graph change.
13:58:46.744 D-BUS: JACK server could not be started. Sorry
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
Sun Dec 24 13:58:46 2017: Starting jack server...
Sun Dec 24 13:58:46 2017: JACK server starting in realtime mode with priority 10
Sun Dec 24 13:58:46 2017: self-connect-mode is "Don't restrict self connect requests"
Sun Dec 24 13:58:46 2017: Acquired audio card Audio2
Sun Dec 24 13:58:46 2017: creating alsa driver ... hw:MI4,0|hw:MI4,0|1024|2|44100|0|0|nomon|swmeter|-|32bit
Sun Dec 24 13:58:46 2017: configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
Sun Dec 24 13:58:46 2017: ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format
Sun Dec 24 13:58:46 2017: ALSA: use 2 periods for capture
Sun Dec 24 13:58:46 2017: ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format
Sun Dec 24 13:58:46 2017: ALSA: use 2 periods for playback
Sun Dec 24 13:58:46 2017: ERROR: ALSA: could not start playback (Broken pipe)
Sun Dec 24 13:58:46 2017: ERROR: Cannot start driver
Sun Dec 24 13:58:46 2017: ERROR: JackServer::Start() failed with -1
Sun Dec 24 13:58:46 2017: ERROR: Failed to start server
Sun Dec 24 13:58:46 2017: Released audio card Audio2
Sun Dec 24 13:58:48 2017: Saving settings to "/home/marcel/.config/jack/conf.xml" ...
13:58:53.686 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
Re: jack not working says cannot start server
Another thing, after looking around a bit I found that I have a kernel message:
I found some older posts related to this but it didn't give me any real directions. Just to inform you my computer is a Dell laptop with a good processor i5 CPU M430 and 8 Gbytes of RAM. When starting the MI4 under Windows with its specific MI4 driver and Cubase it works.
Also, to my surprise also audacity on linux works? It takes a bit of clicking around to make the monitoring work etc but then I can record audio and playback audio plus recording new tracks etc.
This is the output of the audacity process when running it from commandline:
When starting audacity I do not have that same error in the kernel log, however I get lines like this:
[ 3580.800292] retire_capture_urb: 12 callbacks suppressed
[ 4095.297761] retire_capture_urb: 36 callbacks suppressed
[ 4104.986729] retire_capture_urb: 93 callbacks suppressed
[ 4119.574671] retire_capture_urb: 35 callbacks suppressed
[ 4144.398538] retire_capture_urb: 12 callbacks suppressed
Code: Select all
usb 2-1.1: cannot submit urb 0, error -28: not enough bandwidth
Also, to my surprise also audacity on linux works? It takes a bit of clicking around to make the monitoring work etc but then I can record audio and playback audio plus recording new tracks etc.
This is the output of the audacity process when running it from commandline:
Code: Select all
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:867:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:867:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:867:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:867:(find_matching_chmap) Found no matching channel map
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4611
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4611
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4611
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4611
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4611
15:32:56: Debug: Unknown accel modifier: 'left'
15:32:56: Debug: Unknown accel modifier: 'click/left'
15:32:56: Debug: Unrecognized accel key 'drag', accel string ignored.
15:32:56: Debug: Unknown accel modifier: 'left'
15:32:56: Debug: Unrecognized accel key 'click', accel string ignored.
15:32:56: Debug: Unknown accel modifier: 'right'
15:32:56: Debug: Unrecognized accel key 'click', accel string ignored.
15:32:56: Debug: Unknown accel modifier: 'left'
15:32:56: Debug: Unknown accel modifier: 'click/left'
15:32:56: Debug: Unrecognized accel key 'drag', accel string ignored.
15:32:56: Debug: Unknown accel modifier: 'left'
15:32:56: Debug: Unrecognized accel key 'click', accel string ignored.
15:32:56: Debug: Unknown accel modifier: 'right'
15:32:56: Debug: Unrecognized accel key 'click', accel string ignored.
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
15:34:47: Debug: Unknown accel modifier: 'left'
15:34:47: Debug: Unknown accel modifier: 'click/left'
15:34:47: Debug: Unrecognized accel key 'drag', accel string ignored.
15:34:47: Debug: Unknown accel modifier: 'left'
15:34:47: Debug: Unrecognized accel key 'click', accel string ignored.
15:34:47: Debug: Unknown accel modifier: 'right'
15:34:47: Debug: Unrecognized accel key 'click', accel string ignored.
15:34:47: Debug: Unknown accel modifier: 'left'
15:34:47: Debug: Unknown accel modifier: 'click/left'
15:34:47: Debug: Unrecognized accel key 'drag', accel string ignored.
15:34:47: Debug: Unknown accel modifier: 'left'
15:34:47: Debug: Unrecognized accel key 'click', accel string ignored.
15:34:47: Debug: Unknown accel modifier: 'right'
15:34:47: Debug: Unrecognized accel key 'click', accel string ignored.
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
15:38:10: Debug: Unknown accel modifier: 'left'
15:38:10: Debug: Unknown accel modifier: 'click/left'
15:38:10: Debug: Unrecognized accel key 'drag', accel string ignored.
15:38:10: Debug: Unknown accel modifier: 'left'
15:38:10: Debug: Unrecognized accel key 'click', accel string ignored.
15:38:10: Debug: Unknown accel modifier: 'right'
15:38:10: Debug: Unrecognized accel key 'click', accel string ignored.
15:38:10: Debug: Unknown accel modifier: 'left'
15:38:10: Debug: Unknown accel modifier: 'click/left'
15:38:10: Debug: Unrecognized accel key 'drag', accel string ignored.
15:38:10: Debug: Unknown accel modifier: 'left'
15:38:10: Debug: Unrecognized accel key 'click', accel string ignored.
15:38:10: Debug: Unknown accel modifier: 'right'
15:38:10: Debug: Unrecognized accel key 'click', accel string ignored.
-1 preload=0
0 preload=240
-1 preload=0
0 preload=240
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
1: »0⋅1/1⋅1/1⋅1/1
; loading "/usr/share/audacity/nyquist/init.lsp"
Set *default-sf-dir* to "/tmp/" in fileio.lsp
AutoNorm feature is on.
Default sound file is marcel-temp.wav.
system.lsp : *RUNTIME-PATH* = /usr/share/audacity/nyquist/
Nyquist -- A Language for Sound Synthesis and Composition
Copyright (c) 1991,1992,1995,2007-2012 by Roger B. Dannenberg
Version 3.09
....
[ 3580.800292] retire_capture_urb: 12 callbacks suppressed
[ 4095.297761] retire_capture_urb: 36 callbacks suppressed
[ 4104.986729] retire_capture_urb: 93 callbacks suppressed
[ 4119.574671] retire_capture_urb: 35 callbacks suppressed
[ 4144.398538] retire_capture_urb: 12 callbacks suppressed
-
- Established Member
- Posts: 897
- Joined: Thu Sep 11, 2014 3:04 pm
- Has thanked: 71 times
- Been thanked: 64 times
Re: jack not working says cannot start server
It's worthwhile reading the System configuration guide.
https://wiki.linuxaudio.org/wiki/system_configuration
In your case I would pay particular attention to the sections including:
limits.conf/audio.conf
audio group
PulseAudio
https://wiki.linuxaudio.org/wiki/system_configuration
In your case I would pay particular attention to the sections including:
limits.conf/audio.conf
audio group
PulseAudio
Some Focal / 20.04 audio packages and resources https://midistudio.groups.io/g/linuxaudio