From: Mark Meyer <mark@ofosos.org>
To: Drew C <me@drewc.ca>
Cc: help-guix@gnu.org
Subject: Re: How to use jack and qjackctl on GuixSD?
Date: Tue, 11 Apr 2017 23:06:07 +0200 [thread overview]
Message-ID: <878tn6bqo0.fsf@ofosos.org> (raw)
In-Reply-To: <CAPySywYhGUSLMESveGJW-AYdTBHDqcOdiXtkfkrkYTjmKMrG=w@mail.gmail.com> (Drew C.'s message of "Tue, 11 Apr 2017 13:33:20 -0700")
Hi Drew!
>>>>> "Drew" == Drew C <me@drewc.ca> writes:
Drew> On most of the other distros I've tried, installing and
Drew> running qjackctl is enough. On GuixSD it will not seem to
Drew> work. It does seem to start it as there is a PID, but cannot
Drew> connect to the socket, does not run in real-time, etc.
I think this did connect for me, but didn't run as realtime
out-of-the-box.
Drew> Any direction on where to go? I am a software developer as
Drew> well and do not mind getting my hands dirty at all, so let me
Drew> know.
qjackctl should have a log, can you post this? It should say something
about adding stuff to limits for the realtime issue and I'd be
interested in the message about the socket.
Do you run a Desktop Environment? I run with bare xmonad, which doesn't
start any sound servers, but if I log into XFCE I'll have a connection
problem. Even when you don't start any programs that use it, some applet
may start PulseAudio (for example).
Cheers, Mark
--
Mark Meyer
mark@ofosos.org
next prev parent reply other threads:[~2017-04-11 21:06 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 [this message]
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
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=878tn6bqo0.fsf@ofosos.org \
--to=mark@ofosos.org \
--cc=help-guix@gnu.org \
--cc=me@drewc.ca \
/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).