Talk:JACK Audio Connection Kit

From ArchWiki
Jump to: navigation, search

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

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)

Misleading script using schedtool for non-audio processes

I would just remove the examples setting up realtime scheduling of GUI application.

If JACK is running with higher priority, the whole chain of audio processes will have the same priority.

The script suggests that elevating GUI application priorities with schedtool will increase the priority of their audio processes, but in fact this is *not* necessary.

What will happen is that the user will increase the priority of non-audio processes (GUI etc), which will have the same priority of the audio processes. It makes things "worse" because you are decreasing the relative priority of the audio processes when you increase priorities of several non-audio processes.

It is just a misleading procedure as far as I'm concerned: the reader will understand something different then what he/she is actually doing. —This unsigned comment is by Smoge (talk) 12:09, 11 June 2015‎. Please sign your posts with ~~~~!

Note: info removed with [1]. — Kynikos (talk) 13:38, 12 June 2015 (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.

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)

"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)

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)

Needs an intro

This article needs an intro. There's no introduction above the TOC and the first section is the Installation. I'd add it myself, but I don't know how best to describe Jack.