From: Ricardo Wurmus <rekado@elephly.net>
To: Kei Kebreau <kei@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add gxtuner.
Date: Mon, 10 Oct 2016 07:30:18 +0200 [thread overview]
Message-ID: <87r37og49h.fsf@elephly.net> (raw)
In-Reply-To: <87k2dhjl8m.fsf@openmailbox.org>
Kei Kebreau <kei@openmailbox.org> writes:
> This package is reproducible and clears the linting process on my
> end. Sadly I'm not skilled enough with JACK to check the functionality
> of the package. :-/
Using JACK on GuixSD effectively requires a little additional effort. I
have this in my system configuration to be able to use JACK’s realtime
mode:
(users (list (user-account
(name "rekado")
(comment "rekado")
(group "rekado")
(supplementary-groups '(… "realtime"))
(home-directory "/home/rekado"))))
(groups (cons* (user-group (name "rekado") (id 1000))
(user-group (name "realtime"))
%base-groups))
…
(services (cons* (pam-limits-service
(list
(pam-limits-entry "@realtime" 'both 'rtprio 99)
(pam-limits-entry "@realtime" 'both 'memlock 'unlimited)))
…))
This means: add my user account to a new group “realtime” and then
raise the realtime priority for this group. Also drop memory
restrictions for members of this group.
Then you close all applications that might currently be using the audio
interface directly. Make sure pulseaudio is not running. Then run the
JACK daemon with the ALSA backend:
jackd -d alsa
At this point you can start any application that needs JACK. To connect
wires between JACK applications and the audio interface ports I
recommend using “patchage”, a graphical patcher that shows you all audio
ports on all JACK appplications and lets you draw connections between
them.
Hope this helps!
~~ Ricardo
next prev parent reply other threads:[~2016-10-10 5:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 18:10 [PATCH] gnu: Add gxtuner Ricardo Wurmus
2016-10-09 20:55 ` Kei Kebreau
2016-10-10 5:30 ` Ricardo Wurmus [this message]
2016-10-10 12:18 ` Kei Kebreau
2016-10-09 21:49 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r37og49h.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=kei@openmailbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.