From: Felix Lechner via <help-guix@gnu.org>
To: gfp <gfp@posteo.at>
Cc: lesikedelweiss@disroot.org, help-guix@gnu.org
Subject: Re: audio interface for Guix
Date: Fri, 29 Nov 2024 09:41:02 -0800 [thread overview]
Message-ID: <87v7w6ey4x.fsf@lease-up.com> (raw)
In-Reply-To: <d83232d2-693c-454a-91a0-97257ab716f7@posteo.at> (gfp@posteo.at's message of "Fri, 29 Nov 2024 17:21:31 +0000")
Hi Gottfried,
On Fri, Nov 29 2024, gfp wrote:
> How did you manage to use it in Guix?
Lesik will give you a better answer, although "the Komplete Audio 1 is
class-compliant." [1]
You can investigate a lot already with 'lsusb' and then with 'alsamixer"
(from alsa-utils). Alsamixer is a console program that uses Ncurses for
graphics and has some odd keybindings [2] but you may just have to
unmute it.
My understaning is all modern sound daemons such as PulseAudio or
Pipewire are built on top of ALSA, which stands for Advanced Linux Sound
Architecture.
Please send the songs you will records with your new system!
Kind regards
Felix
[1] https://linuxmusicians.com/viewtopic.php?p=153946&sid=6e8deb756edcb3a4679d7e0a6a6ebd47#p153946
[2] https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture#Unmute_with_alsamixer
next prev parent reply other threads:[~2024-11-29 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 17:21 audio interface for Guix gfp
2024-11-29 17:41 ` Felix Lechner via [this message]
2024-12-01 9:37 ` gfp
2024-12-01 10:50 ` Aleksej via
2024-12-01 14:56 ` gfp
2024-12-01 15:11 ` gfp
[not found] ` <58f9f6eb286cc456f20e5110b25aa152@disroot.org>
2024-11-29 21:09 ` gfp
[not found] ` <17F771C9-2C51-4AAB-BEE6-63768D3A8B8F@disroot.org>
2024-11-30 12:52 ` audio interface for Guix - difference Guix and Guix home gfp
-- strict thread matches above, loose matches on Subject: below --
2024-11-27 17:15 Audio Interface for Guix gfp
2024-11-27 18:01 ` Aleksej via
2024-11-27 19:26 ` Daniel Hatton
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=87v7w6ey4x.fsf@lease-up.com \
--to=help-guix@gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=gfp@posteo.at \
--cc=lesikedelweiss@disroot.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.