JackAudio September 2020

jackaudio@lists.linuxaudio.org

8 participants
6 discussions

Is it possible to connect two usb input devices to jack (linux)? (neophyte question)

by Barnet Wagman

I have two usb audio input devices that I'd like to mix and connect to Jamulus, an application that uses jack (not pulseaudio). I'm trying to find out if this is possible. I'm running jack2 on a debian 10 system. There's one audio card (chip, actually) that's listed as HDA Intel. FYI The usb input devices are a Shure MV5 microphone and a Scarlett Solo audio interface. I can connect either of these devices to jack by specify one from qjackctl setup: Settings -> Advanced -> Input device. I don't see how to capture and mix the input from both devices. I haven't found any documentation that explains how to do this or if it's possible. Thanks

3 years, 2 months

JACK/ALC1220 issues

by Mike Uchima

Hey, new subscriber here. I've been using JACK for several years but know just enough about it to get it to work (usually). I've hit a couple of issues with a new system build that have me stumped. Specifics of the system: Ryzen 3700X; Asus Prime X470 Pro motherboard; using (or at least attempting to use) the on-board audio, which is an ALC1220. OS is Ubuntu 20.04 LTS; JACK is configured to run with realtime priority. Issue #1: Can't get any output from the digital (S/PDIF) port. I've made sure S/PDIF is unmuted in alsamixer, and the S/PDIF output works fine with PulseAudio. I've tried outputting to all of the system ports that show in the JACK connection manager, and none of them produce any output on the S/PDIF port. Issue #2: If I run with the default number of output channels (6), JACK stutters horribly with constant XRUNs. Already tried changing the --period option; if I increase it JACK fails to start, and if I decrease it the stuttering gets worse. Also tried changing --nperiods; increasing it prevents JACK from starting. If I disable the last 2 channels (i.e. run in 4 channel mode) the stuttering goes away. I can live with #2 (don't really need the last 2 channels), but if I can't get #1 resolved I'll be looking at a 3rd party soundcard (internal or external) for this system. Any thoughts/insights would be welcome. Thanks!

3 years, 2 months

Can't start with laptop speakers on Thinkpad Carbon X1 7th Gen and Ubuntu 20.04

by Dan Zink

Hello all, Sometimes I want to use jackd with the laptop speakers or headphones, instead of my audio interface. I can't get it to start on my new laptop (using the audio interface works perfectly, thanks community :) ). I've successfully and mostly painlessly gotten jackd working on a few different machines, but this one has me stumped. I'm going to try to document as much as I can here so please forgive me if I miss something. I'm using this version of jackd $jackd -V jackdmp version 1.9.12 tmpdir /dev/shm protocol 8 and this version of Ubuntu: $uname -a Linux daniel-ThinkPad-X1-Carbon-7th 5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Starting up selecting the first device under `aplay` throws this error (using -R instead of -r doesn't seem to affect very much): $jackd --verbose -r -P 80 -d alsa -d hw:sofhdadsp,0 jackdmp 1.9.12 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2017 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 non-realtime mode self-connect-mode is "Don't restrict self connect requests" Jack: JackPosixThread::StartImp : create non RT thread Jack: JackPosixThread::ThreadHandler : start Jack: playback device hw:sofhdadsp,0 Jack: capture device hw:sofhdadsp,0 Jack: JackDriver::Open capture_driver_name = hw:sofhdadsp,0 Jack: JackDriver::Open playback_driver_name = hw:sofhdadsp,0 Jack: Check protocol client = 8 server = 8 Jack: JackEngine::ClientInternalOpen: name = system Jack: JackEngine::AllocateRefNum ref = 0 Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val = 0 Jack: JackEngine::NotifyAddClient: name = system Jack: JackGraphManager::SetBufferSize size = 1024 Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 Jack: JackDriver::SetupDriverSync driver sem in flush mode audio_reservation_init Acquire audio card Audio0 creating alsa driver ... hw:sofhdadsp,0|hw:sofhdadsp,0|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 32bit integer little-endian ALSA: cannot set period size to 1024 frames for capture ALSA: cannot configure capture channel Jack: JackDriver::Close Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0 Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 Jack: JackEngine::ClientInternalClose ref = 0 Jack: JackEngine::ClientCloseAux ref = 0 Jack: JackGraphManager::RemoveAllPorts ref = 0 Released audio card Audio0 audio_reservation_finish Jack: ~JackDriver Cannot initialize driver Jack: no message buffer overruns Jack: JackPosixThread::Stop Jack: JackPosixThread::ThreadHandler : exit JackServer::Open failed with -1 Jack: Succeeded in unlocking 82280346 byte memory area Jack: JackShmMem::delete size = 0 index = 0 Jack: ~JackDriver Jack: Succeeded in unlocking 1187 byte memory area Jack: JackShmMem::delete size = 0 index = 1 Jack: Cleaning up shared memory Jack: Cleaning up files Jack: Unregistering server `default' Failed to open server Using a dummy server succeeds: $jackd -r -P 80 -d dummy jackdmp 1.9.12 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2017 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 non-realtime mode self-connect-mode is "Don't restrict self connect requests" When I list my devices (with the interface unplugged), with aplay -l I get: $aplay -l **** List of PLAYBACK Hardware Devices **** card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 here's the relevant lsmod: $lsmod | grep snd snd_seq_dummy 16384 0 snd_usb_audio 266240 0 snd_usbmidi_lib 36864 1 snd_usb_audio snd_seq_midi 20480 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_seq 69632 3 snd_seq_midi,snd_seq_midi_event,snd_seq_dummy snd_rawmidi 36864 2 snd_seq_midi,snd_usbmidi_lib snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi snd_hda_intel 53248 0 mc 53248 5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common snd_soc_skl_hda_dsp 24576 6 snd_hda_codec_hdmi 61440 1 snd_soc_hdac_hdmi 36864 1 snd_soc_skl_hda_dsp snd_hda_codec_realtek 126976 1 snd_hda_codec_generic 81920 1 snd_hda_codec_realtek snd_soc_dmic 16384 1 snd_sof_pci 20480 2 snd_sof_intel_hda_common 69632 1 snd_sof_pci snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common snd_sof_intel_hda 20480 1 snd_sof_intel_hda_common snd_sof_intel_byt 20480 1 snd_sof_pci snd_sof_intel_ipc 20480 1 snd_sof_intel_byt snd_sof 106496 4 snd_sof_pci,snd_sof_intel_hda_common,snd_sof_intel_byt,snd_sof_intel_ipc snd_sof_xtensa_dsp 16384 1 snd_sof_pci snd_hda_ext_core 28672 4 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_soc_acpi_intel_match 32768 2 snd_sof_pci,snd_sof_intel_hda_common snd_soc_acpi 16384 2 snd_sof_pci,snd_soc_acpi_intel_match snd_soc_core 245760 6 snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_soc_dmic,snd_soc_skl_hda_dsp snd_compress 24576 1 snd_soc_core ac97_bus 16384 1 snd_soc_core snd_pcm_dmaengine 16384 1 snd_soc_core snd_intel_dspcfg 24576 3 snd_hda_intel,snd_sof_pci,snd_sof_intel_hda_common snd_hda_codec 131072 6 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda,snd_soc_skl_hda_dsp snd_hda_core 90112 11 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda,snd_soc_skl_hda_dsp snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec snd_pcm 106496 11 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_core,snd_hda_core,snd_pcm_dmaengine ledtrig_audio 16384 4 snd_hda_codec_generic,snd_hda_codec_realtek,snd_sof,thinkpad_acpi snd_timer 36864 2 snd_seq,snd_pcm snd 90112 28 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,thinkpad_acpi,snd_soc_core,snd_pcm,snd_soc_skl_hda_dsp,snd_rawmidi soundcore 16384 1 snd And finally, the lspci $sudo lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 11) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 11) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 11) 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 11) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 11) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 11) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 11) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f1) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 11) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 11) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 11) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (6) I219-V (rev 11) 03:00.0 Non-Volatile memory controller: Sandisk Corp WD Black 2018/PC SN720 NVMe SSD Has anyone else succeeded in getting jackd running with this particular hardware? Thanks!

3 years, 2 months

Downloads Windows and MacOS.

by Kjetil Matheussen

Hi, Can you please put back link to downloads for windows and macos? Now people get the wrong impression (at least one person have expressed this opinion to me) that the downloads are gone because jack is unstable on those two platforms, which they are not. (qjackctl is though, but not jack itself).

3 years, 2 months

[ANN] KillJack V2020-08-08

by Kjetil Matheussen

Source code and binaries for linux/windows/osx here: https://github.com/kmatheussen/KillJack BACKGROUND ---------- The Jack server sometimes crashes/freezes in ways which make users restart the computer in order to use Jack again. Users don't really have to restart the computer, but googling the problem and finding a solution could take more time than restarting. This is not very user friendly. The problem exists on all platforms. It's not a bug in Jack per se, it's how the program reacts when a client misbehave in certain ways. ABOUT ----- This program kills Jack unconditionally. Executables for Linux, MacOS, and Windows are provided. I strongly recommend that all programs using Jack includes a program like this. A better solution would be if Jack ran a watchdog, but it currently doesn't. You are allowed to distribute this program any way you want. [1] [1] Note that there might be copyright issues with the icon and the quotes from the movie.

3 years, 2 months

Cross compiling JACK

by piegames

Hi, a few days ago, I ran into < https://github.com/NixOS/nixpkgs/issues/96548>. I'm trying to cross- compile JACK on x86-64 for ARMv7 and it fails. But I'm not 100% sure if this is a NixOS packaging problem or if JACK can be cross compiled at all. So please have a quick look at it and tell me if I should open an issue on JACK itself instead. Regards, piegames

3 years, 2 months

2023

2022

2021

2020

2019

2018

2017

2016

2015

JackAudio September 2020