Is the sound card used in the section https://wiki.archlinux.org/index.php/JACK_Audio_Connection_Kit#Playing_nice_with_ALSA supposed to use...

ctl.mixer0 {
 type hw
 card 0
}

...instead of

ctl.mixer0 {
 type hw
 card 1
}

I've tried both in my system and I don't notice anything changing because of it. I've left mine at "card 0" because that's my default sound card.

Saultdon (talk) 01:24, 6 July 2013 (UTC)

Wouldn't it make sense to put the other parameters such as sample rate before starting the server? As best I understand it, the other parameters don't even need to be in the startup scripts, since the settings don't get reverted with each restart.

To7m (talk) 21:31, 28 December 2016 (UTC)

Yep, this script actually starts jack with the previously used settings, then changes the setting that will be used on the next start. A better version might look something like this:

start_jack.sh

#!/bin/bash

jack_control stop
jack_control ds alsa
jack_control dps device hw:USB
jack_control dps rate 48000
jack_control dps nperiods 3
jack_control dps period 64
jack_control start

Basically, you stop jack before changing the settings, then restart it with the new settings. If you wanted to do this properly, you would set every option explicitly in the script.

Barabas (talk) 07:28, 25 May 2020 (UTC)

alsa-plugins-1.17 Added '/etc/alsa/conf.d/50-jack.conf' which defines a system 'pcm.jack' port.

See relevant report on alsa-plugins's mailing list: https://mailman.alsa-project.org/pipermail/alsa-devel/2018-October/141213.html

The .asoundrc section in the article should use a different name (like pcm.jack2) or use the bundled pcm.jack port from 50-jack.conf as its default pcm.

—This unsigned comment is by Teteros (talk) 2019-03-12T01:59:35. Please sign your posts with ~~~~!

I experienced that using `jack_control dps device hw:XXX` is not enough to change the audio device. In fact, the same device has to be set for the `capture` and `playback` parameter as well. Maybe you have a system with at least two audio devices and can confirm that switching with only `jack_control dps device ...` is not sufficient.

I propose the following changes to make this clear:

start_jack.sh

#!/bin/bash

jack_control stop
jack_control ds alsa
jack_control dps device hw:USB
jack_control dps capture hw:USB
jack_control dps playback hw:USB
jack_control dps rate 48000
jack_control dps nperiods 3
jack_control dps period 64
jack_control start

—This unsigned comment is by Chr (talk) 2022-10-01T16:43:56. Please sign your posts with ~~~~!

In the installation chapter, it is written : "For an alternative ALSA MIDI support in jack2 install a2jmidid."

Do we have to add `pipewire-jack` that provides a built in MIDI ?

--Jujudusud (talk) 09:53, 2 February 2023 (UTC)

In the fourth chapter, comparison of JACK implementation, It is written that PipeWire Support ALSA FireWire interfaces. There is now a "native support of libffado. The package is called pipewire-ffado.

Do we have to add libffado in the Pipewire's firewire support?

Jujudusud (talk) 23:01, 25 August 2023 (UTC)