From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0000798]: Make alsaconf optinal able to create an asound.conf
Date: Wed, 19 Jan 2005 16:48:29 +0100 [thread overview]
Message-ID: <fbc628e14b78fdb9fb6284ccd0b434bf@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=798>
======================================================================
Reported By: christeck
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 798
Category: alsaconf
Reproducibility: always
Severity: feature
Priority: normal
Status: new
======================================================================
Date Submitted: 01-09-2005 22:05 CET
Last Modified: 01-19-2005 16:48 CET
======================================================================
Summary: Make alsaconf optinal able to create an asound.conf
Description:
An asound.conf is difficult to create manually due to its difficult to
understand syntax. Would be great if alsaconf could optional create it, so
the user can
* Define in which order the cards appear (e.g., internal AC97, Modem,
USB-Audio and an USB MIDI card)
* Define some dmix devices
* Else? Not familiar enough with dmix, I do not use it :)
======================================================================
----------------------------------------------------------------------
jdthood - 01-19-05 15:29
----------------------------------------------------------------------
A nice idea, but it would be better to write a separate program
to generate asound.conf. alsaconf writes configuration files for
the ALSA drivers whereas asound.conf is a configuration file for the
ALSA library.
----------------------------------------------------------------------
tiwai - 01-19-05 16:48
----------------------------------------------------------------------
Agreed. Both issues described are above the scope of alsaconf.
dmix will be default in alsa-lib without any special configuration for
most of mobo drivers in the next version (I hope).
The order of card is not the problem of asound.conf but rather index
module option. Since alsaconf supports only a single card, this is also
out or its target. The hack to move modem to the secondary card (by
James) will be added in the next rext version, too.
Issue History
Date Modified Username Field Change
======================================================================
01-09-05 22:05 christeck New Issue
01-19-05 15:29 jdthood Note Added: 0003287
01-19-05 16:48 tiwai Note Added: 0003293
======================================================================
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next reply other threads:[~2005-01-19 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 15:48 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-08 8:35 [ALSA - utils 0000798]: Make alsaconf optinal able to create an asound.conf bugtrack
2005-01-19 17:38 bugtrack
2005-01-19 17:33 bugtrack
2005-01-19 15:56 bugtrack
2005-01-19 15:54 bugtrack
2005-01-19 14:29 bugtrack
2005-01-09 21:05 bugtrack
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=fbc628e14b78fdb9fb6284ccd0b434bf@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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.
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.