From: Drew C <me@drewc.ca>
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: Mark Meyer <mark@ofosos.org>, help-guix@gnu.org
Subject: Re: How to use jack and qjackctl on GuixSD?
Date: Wed, 12 Apr 2017 15:31:26 -0700 [thread overview]
Message-ID: <CAPySywY9ZWYwhtu5T-NrtG7Sz7JbekKnK2_iWO+Sw_PNWmPx3A@mail.gmail.com> (raw)
In-Reply-To: <20170412.080814.926849858842682330.post@thomasdanckaert.be>
[-- Attachment #1: Type: text/plain, Size: 899 bytes --]
Hey All,
Thanks a lot! Though I still do not have qjackctl working, Ricardo
Wurmus's help was a big plus. Now, `jackd -d alsa` works at the command
line, so things are starting to move up.
Will hopefully have more to report as working shortly.
Cheers,
Drew Crampsie
On Tue, Apr 11, 2017 at 11:08 PM, Thomas Danckaert <post@thomasdanckaert.be>
wrote:
> Hi Drew,
>
> hope this helps:
>
> - jack 0.124.1 wouldn't work for me either. It was updated to 0.125
> 2 days ago, and the upgrade fixed that for me.
>
> - about the realtime/limits.conf issue: I added the following service to
> my system configuration's services list:
>
> (pam-limits-service
> (list
> (pam-limits-entry "@realtime" 'both 'rtprio 99)
> (pam-limits-entry "@realtime" 'both 'memlock 'unlimited)))
>
> all of this courtesy of Ricardo Wurmus actually :)
>
> Thomas
>
[-- Attachment #2: Type: text/html, Size: 1494 bytes --]
next prev parent reply other threads:[~2017-04-12 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 20:33 How to use jack and qjackctl on GuixSD? Drew C
2017-04-11 21:06 ` Mark Meyer
2017-04-11 21:47 ` Drew C
2017-04-11 22:24 ` qjackctl wrong jack version (was: Re: How to use jack and qjackctl on GuixSD?) Mark Meyer
2017-04-12 6:08 ` How to use jack and qjackctl on GuixSD? Thomas Danckaert
2017-04-12 22:31 ` Drew C [this message]
2017-04-12 1:04 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPySywY9ZWYwhtu5T-NrtG7Sz7JbekKnK2_iWO+Sw_PNWmPx3A@mail.gmail.com \
--to=me@drewc.ca \
--cc=help-guix@gnu.org \
--cc=mark@ofosos.org \
--cc=post@thomasdanckaert.be \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).