Talk:JACK Audio Connection Kit

From ArchWiki

Wrong sound card number in "Playing nice with ALSA"?

Is the sound card used in the section 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)

QMidiRoute line needs a sample config or a link to a sample config

Having the QMidiRoute line in the sample configuration is a bit pointless without at least a link to a .qmr file that does what's indicated here. It's a great idea, but not very useful for anyone not familiar with this piece of software.

This statement does not apply to anything in the current article anymore. -- Davezerave (talk) 14:24, 26 January 2022 (UTC)

Running "jack_control start" before other commands?

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:

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)

"python2-dbus" dependancy for "jack_control start"

A couple of people have had problems with jack_control start which is only solved by installing the "python2-dbus" package. As far as I can tell this is neither mentioned on the JACK wiki page nor is it a dependancy in the jack2-dbus package.

—This unsigned comment is by Blue Fang (talk) 4 January 2017. Please sign your posts with ~~~~!

You are right, jack_control requires python2-dbus to work. This is mentioned in the jack2-dbus package however: python2-dbus is listed as an optional dependency:
# pacman -S jack2-dbus
(1/1) installing jack2-dbus
Optional dependencies for jack2-dbus
    python2-dbus: jack_control
I do agree we can list it clearer on this wiki page however, so I have made this edit. If you want to clarify it further, go ahead. Lonaowna (talk) 12:25, 4 January 2017 (UTC)
Python-dbus has been a dependency for jack2-dbus for a long time and the package is mentioned in the installation section. -- Davezerave (talk) 14:15, 26 January 2022 (UTC)

The entire configuration section is based off of information from an article from 2006

Seriously outdated and contains a lot of now incorrect information. Seriously needs a rewrite Actioninja (talk) 05:41, 28 May 2017 (UTC)

I did it myself, a lot of the information was good but some of it was inaccurate and needed to be removed or rewritten. Actioninja (talk) 06:46, 28 May 2017 (UTC)
The section has now been redone. Please focus on the tips and tricks subsections for improvements. -- Davezerave (talk) 14:30, 26 January 2022 (UTC)

Conflicting PCM in "Playing nice with ALSA" ?

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:

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.


I had an issue where my jack_control commands stopped working until i intsalled the jack2-dbus package. Is this a one-off issue where i somehow accidentally uninstalled it or has the structure of the packages changed? I see that the package was rebuilt today, maybe there was some change in dependencies or something? either way, I think it would be nice if somewhere in the article, jack2-dbus was listed as a requirement for using the jack_control command, assuming I'm not misunderstanding how the package works. Jaxter184 (talk) 00:55, 25 January 2021 (UTC)

Looking at the page history, it seems like jack2-dbus was merged into jack2 at some point. Was it unmerged recently? Jaxter184 (talk) 01:01, 25 January 2021 (UTC)
You are right! It seems that jack2-dbus was split a week ago.[1] I've made a quick edit to note this but feel free to take a look at the page yourself and see if it needs more info about the split package. Lonaowna (talk) 06:13, 25 January 2021 (UTC)
Jack2-dbus is now mentioned in the "Installation" section and in the "Starting the graph" section. Further use-cases should be explained in the tips and tricks section -- Davezerave (talk) 14:22, 26 January 2022 (UTC)