Jack troubleshooting

Optimize your system for ultimate performance.

Moderators: MattKingUSA, khz

Post Reply
dl6mee
Established Member
Posts: 9
Joined: Wed Aug 31, 2022 3:43 pm

Jack troubleshooting

Post by dl6mee »

Hi, everyone :D

after installing the audio and lowlatency part of the Ubuntu Studio with the Studio Installer on my brandnew Xubuntu 22.04.1 I wanted to get JACK to work - by use of Studio Set Up Utility 2.3.1
But it doesn't work!

On the console with the dummy backend JACK works. I can start Guitarix and Rakarrack.

Something is wrong in the configuration, but where to start the troubleshooting?

I'm grateful for any help!
Natelok
Established Member
Posts: 58
Joined: Fri Feb 08, 2019 7:18 pm
Location: Donnybrook Western Australia
Has thanked: 78 times
Been thanked: 14 times

Re: Jack troubleshooting

Post by Natelok »

Can you tell us the audio device (brand, model and version of you can) you're using, and also a screenshot of the jack configuration you're trying to use, preferably from qjackctl.

Also, go and grab realtimeconfigquickscan (or rather, it's most recent version rtcqs), run the script and follow it's advice. If you're still having trouble, the output from this script can help us help you. You'll find it on GitHub.

Looking forward to hearing back from you with more info.

Nate
Nate!

Music Nerd, Guitarist, Fixer of Things, DJ, currently employed by Donnybrook Balingup Community Radio (Station Manager & Drive Time DJ, Recording Engineer for a small attached studio for local artists)

DAW: Mixbus at home, Mixbus32C at work
dl6mee
Established Member
Posts: 9
Joined: Wed Aug 31, 2022 3:43 pm

Re: Jack troubleshooting

Post by dl6mee »

Hello Nate ... and many thanks for your reply!!!

Audio hardware

dl6mee@Xubuntu:~$ aplay -l
**** Liste der Hardware-Geräte (PLAYBACK) ****
Karte 0: NVidia_1 [HDA NVidia], Gerät 0: VT1705 Analog [VT1705 Analog]
Sub-Geräte: 0/1
Sub-Gerät #0: subdevice #0
Karte 0: NVidia_1 [HDA NVidia], Gerät 2: VT1705 Alt Analog [VT1705 Alt Analog]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 1: NVidia [HDA NVidia], Gerät 3: HDMI 0 [HDMI 0]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 1: NVidia [HDA NVidia], Gerät 7: HDMI 0 [HDMI 0]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 1: NVidia [HDA NVidia], Gerät 8: HDMI 0 [HDMI 0]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 1: NVidia [HDA NVidia], Gerät 9: HDMI 0 [HDMI 0]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 2: S51 [SB X-Fi Surround 5.1], Gerät 0: USB Audio [USB Audio]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
Karte 2: S51 [SB X-Fi Surround 5.1], Gerät 1: USB Audio [USB Audio #1]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0


hw0, hw1 on-board; hw2 Creative Labs SB1090 USB

Configuration

JACK

<?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.
-->
<!-- Thu Sep 1 12:54:47 2022 -->
<jack>
<engine>
<option name="driver">alsa</option>
</engine>
<drivers>
<driver name="net">
</driver>
<driver name="dummy">
</driver>
<driver name="firewire">
</driver>
<driver name="alsarawmidi">
</driver>
<driver name="loopback">
</driver>
<driver name="alsa">
<option name="device">hw:NVidia_1,0,0</option>
<option name="rate">44100</option>
<option name="period">128</option>
<option name="nperiods">2</option>
<option name="input-latency">0</option>
<option name="output-latency">0</option>
</driver>
<driver name="netone">
</driver>
<driver name="proxy">
</driver>
</drivers>
<internals>
<internal name="netadapter">
</internal>
<internal name="netmanager">
</internal>
<internal name="audioadapter">
</internal>
<internal name="profiler">
</internal>
</internals>
</jack>

autojack

{
"version": "2.3.1",
"log-level": "7",
"jack": {
"on": true,
"driver": "alsa",
"chan-in": 1,
"chan-out": 1,
"rate": 44100,
"frame": 128,
"period": 2,
"connect-mode": "n",
"dev": "NVidia_1,0,0",
"usbdev": "none",
"cap-latency": 0,
"play-latency": 0
},
"extra": {
"a2j": true,
"usbauto": true,
"usb-single": false,
"monitor": "system:playback_1",
"phone-action": "switch",
"phone-device": "NVidia_1,0,0",
"usbnext": 2,
"a2j_u": false
},
"pulse": {
"inputs": {
"pulse_in": {
"connection": "system:capture_1",
"count": 2
}
},
"outputs": {
"pulse_out": {
"connection": "monitor",
"count": 2
}
}
},
"devices": {
"NVidia_1": {
"number": 0,
"usb": false,
"internal": true,
"hdmi": false,
"firewire": false,
"rates": [
"44100",
"48000",
"88200",
"96000",
"192000"
],
"min_latency": 128,
"id": "none",
"bus": "none",
"sub": {
"0": {
"name": "NVidia_1,0,0",
"playback": true,
"capture": true,
"rate": 44100,
"frame": 128,
"nperiods": 2,
"hide": false,
"cap-latency": 0,
"play-latency": 0,
"play-chan": 100,
"cap-chan": 100,
"play-pid": 0,
"cap-pid": 0
},
"2": {
"playback": true,
"capture": false,
"play-chan": 0,
"cap-chan": 0,
"rate": 48000,
"frame": 1024,
"nperiods": 2,
"hide": true,
"name": "NVidia_1,2,0",
"cap-latency": 0,
"play-latency": 0,
"play-pid": 0,
"cap-pid": 0
}
},
"raw": "NVidia_1"
},
"NVidia": {
"number": 1,
"usb": false,
"internal": true,
"hdmi": true,
"firewire": false,
"min_latency": 4096,
"rates": [
"32000",
"44100",
"48000",
"88200",
"96000",
"176400",
"192000"
],
"raw": "NVidia",
"id": "none",
"bus": "none",
"sub": {
"3": {
"playback": true,
"capture": false,
"play-chan": 0,
"cap-chan": 0,
"rate": 48000,
"frame": 4096,
"nperiods": 2,
"hide": true,
"name": "NVidia,3,0",
"cap-latency": 0,
"play-latency": 0,
"play-pid": 0,
"cap-pid": 0
},
"7": {
"playback": true,
"capture": false,
"play-chan": 0,
"cap-chan": 0,
"rate": 48000,
"frame": 4096,
"nperiods": 2,
"hide": true,
"name": "NVidia,7,0",
"cap-latency": 0,
"play-latency": 0,
"play-pid": 0,
"cap-pid": 0
},
"8": {
"playback": true,
"capture": false,
"play-chan": 0,
"cap-chan": 0,
"rate": 48000,
"frame": 4096,
"nperiods": 2,
"hide": true,
"name": "NVidia,8,0",
"cap-latency": 0,
"play-latency": 0,
"play-pid": 0,
"cap-pid": 0
},
"9": {
"playback": true,
"capture": false,
"play-chan": 0,
"cap-chan": 0,
"rate": 48000,
"frame": 4096,
"nperiods": 2,
"hide": true,
"name": "NVidia,9,0",
"cap-latency": 0,
"play-latency": 0,
"play-pid": 0,
"cap-pid": 0
}
}
},
"USB1": {
"number": -1,
"usb": true,
"internal": false,
"hdmi": false,
"firewire": false,
"min_latency": 32,
"rates": [
"48000",
"96000"
],
"raw": "S51",
"id": "041e:3042",
"bus": "002",
"sub": {
"0": {
"playback": true,
"capture": true,
"play-chan": 100,
"cap-chan": 100,
"rate": 48000,
"frame": 1024,
"nperiods": 2,
"hide": true,
"name": "USB1,0,0",
"cap-latency": 0,
"play-latency": 0,
"play-pid": 0,
"cap-pid": 0
},
"1": {
"playback": true,
"capture": false,
"play-chan": 100,
"cap-chan": 100,
"rate": 48000,
"frame": 1024,
"nperiods": 2,
"hide": true,
"name": "USB1,1,0",
"cap-latency": 0,
"play-latency": 0,
"play-pid": 0,
"cap-pid": 0
}
}
}
},
"znet": {},
"mnet": {
"type": "jack",
"count": 0
}
}


Output of realtimeconfigquickscan

dl6mee@Xubuntu:~/Software/realtimeconfigquickscan-master$ export SOUND_CARD_IRQ=22
dl6mee@Xubuntu:~/Software/realtimeconfigquickscan-master$ perl ./realTimeConfigQuickScan.pl
== GUI-enabled checks ==
Checking if you are root... no - good
Checking filesystem 'noatime' parameter... 5.15.0 kernel - good
(relatime is default since 2.6.30)
Checking CPU Governors... CPU 0: 'performance' CPU 1: 'performance' CPU 2: 'performance' CPU 3: 'performance' - good
Checking swappiness... 10 - good
Checking for resource-intensive background processes... none found - good
Checking checking sysctl inotify max_user_watches... >= 524288 - good
Checking whether you're in the 'audio' group... yes - good
Checking for multiple 'audio' groups... no - good
Checking the ability to prioritize processes with chrt... yes - good
Checking kernel support for high resolution timers... found - good
Kernel with Real-Time Preemption... 'threadirqs' kernel parameter - good
Checking if kernel system timer is high-resolution... found - good
Checking kernel support for tickless timer... found - good
== Other checks ==
Checking filesystem types... ok.
Checking for devices at IRQ 22... found multiple. not ok.


(rtcqs is not possible, because I cannot install pip. The system wants to read from CD2, but I have only an USB-stick)

Output of jackdbus.log

JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
Driver is not running
Cannot open client name = dbusapi
failed to create dbusapi jack client
Unknown request 4294967295
CheckSize error size = 0 Size() = 12
CheckRead error


THANKS FOR YOUR EFFORT!!!!!

Karl
User avatar
LAM
Established Member
Posts: 992
Joined: Thu Oct 08, 2020 3:16 pm
Has thanked: 141 times
Been thanked: 348 times

Re: Jack troubleshooting

Post by LAM »

Hi @dl6mee,
are you launching JACK with the right device?

I see many Nvidia HDMI devices and a S51 [SB X-Fi Surround 5.1] USB audio.

in mix, nobody can hear your screen

dl6mee
Established Member
Posts: 9
Joined: Wed Aug 31, 2022 3:43 pm

Re: Jack troubleshooting

Post by dl6mee »

Hello LAM :D

Tried both devices with capture and playback ... hw:0,0 and hw:2,0
User avatar
LAM
Established Member
Posts: 992
Joined: Thu Oct 08, 2020 3:16 pm
Has thanked: 141 times
Been thanked: 348 times

Re: Jack troubleshooting

Post by LAM »

dl6mee wrote: Thu Sep 01, 2022 12:06 pm Hello LAM :D

Tried both devices with capture and playback ... hw:0,0 and hw:2,0
What happens if you launch JACK from terminal like this:

Code: Select all

jackd -dalsa -dhw:S51 -r44100 -p512 -n2
?

in mix, nobody can hear your screen

dl6mee
Established Member
Posts: 9
Joined: Wed Aug 31, 2022 3:43 pm

Re: Jack troubleshooting

Post by dl6mee »

dl6mee@Xubuntu:~$ jackd -dalsa -dhw:S51 -r44100 -p512 -n2
jackdmp 1.9.20
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2021 Filipe Coelho.
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
`default' server already active
Failed to open server


jackd vs. autojack/jackbus? After killing all relevant processes:

dl6mee@Xubuntu:~$ jackd -dalsa -dhw:S51 -r44100 -p512 -n2
jackdmp 1.9.20
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2021 Filipe Coelho.
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 Audio1
creating alsa driver ... hw:S51|hw:S51|512|2|44100|0|0|nomon|swmeter|-|32bit
configuring for 44100Hz, period = 512 frames (11.6 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 Audio1
audio_reservation_finish
dl6mee
Established Member
Posts: 9
Joined: Wed Aug 31, 2022 3:43 pm

Re: Jack troubleshooting

Post by dl6mee »

I think I'll try the Behringer GUITAR 2 USB Interface too ...
User avatar
Linuxmusician01
Established Member
Posts: 1543
Joined: Mon Feb 23, 2015 2:38 pm
Location: Holland (Europe)
Has thanked: 774 times
Been thanked: 143 times

Re: Jack troubleshooting

Post by Linuxmusician01 »

dl6mee wrote: Thu Sep 01, 2022 5:03 pm I think I'll try the Behringer GUITAR 2 USB Interface too ...
Does Jack work with the on-board audio card?
dl6mee
Established Member
Posts: 9
Joined: Wed Aug 31, 2022 3:43 pm

Re: Jack troubleshooting

Post by dl6mee »

dl6mee wrote: Thu Sep 01, 2022 5:03 pm I think I'll try the Behringer GUITAR 2 USB Interface too ...
Indeed, JACK is running now with this device. It was a hardware problem.

[SOLVED]
Post Reply