Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Giuliano Pochini <pochini@denise.shiny.it>
Cc: Patrick Shirkey <pshirkey@boosthardware.com>,
	alsa-devel@lists.sourceforge.net,
	Mark Knecht <markknecht@gmail.com>
Subject: Re: Maintaining sound card at a specific frequency
Date: Tue, 18 Jan 2005 18:40:00 +0100	[thread overview]
Message-ID: <s5hzmz6vdov.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0501181822220.29107@denise.shiny.it>

At Tue, 18 Jan 2005 18:31:28 +0100 (CET),
Giuliano Pochini wrote:
> 
> 
> 
> On Tue, 18 Jan 2005, Takashi Iwai wrote:
> 
> > > IMHO we should think on a good solution for this problem. Some
> > > cards have many channels/voices but the sample rate is common
> > > for all of them. Currently the only clean way to manage it is
> > > a control that locks the sample rate at a given frequency, but
> > > it isn't a nice solution because it requires explicit user
> > > intervention. In the echoaudio driver I implemented a kludge
> > > that automatically locks the sample frequency in order to avoid
> > > unwanted rate changes.
> >
> > You can add a control to lock the sample rate (e.g. ICE1712).
> 
> Yep, I know, but it's not part of the pcm API: applications do not
> lock the sample rate themselves. The user has to do it manually. This is
> why I choosed an alternate solution. If apps were able to lock the rate it
> would be very useful. It may need some help from the driver, though.

I think this is above the PCM API since this influences the whole
system.  It's fine to add a new API call in alsa-lib, just as a
wrapper to toggle such a  control, though...


Takashi


-------------------------------------------------------
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

  reply	other threads:[~2005-01-18 17:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-16 21:05 Maintaining sound card at a specific frequency Mark Knecht
2005-01-17  5:14 ` Patrick Shirkey
2005-01-18 15:50   ` Giuliano Pochini
2005-01-18 16:48     ` Takashi Iwai
2005-01-18 17:01       ` Mark Knecht
2005-01-18 17:08         ` Takashi Iwai
2005-01-18 17:12           ` Mark Knecht
2005-01-18 17:15             ` Takashi Iwai
2005-01-18 17:43               ` Mark Knecht
2005-01-18 17:48           ` Takashi Iwai
2005-01-18 18:04             ` Mark Knecht
2005-01-18 17:31       ` Giuliano Pochini
2005-01-18 17:40         ` Takashi Iwai [this message]
2005-01-19 10:07           ` Giuliano Pochini
2005-01-18 17:45         ` Mark Knecht
2005-01-18 19:51           ` Takashi Iwai
2005-01-18 21:22             ` Mark Knecht
2005-01-18 21:30           ` Lee Revell
2005-01-18 23:16             ` Mark Knecht
2005-01-19 19:59   ` Mark Knecht
2005-01-19  9:07 ` Clemens Ladisch
2005-01-19 10:14   ` Takashi Iwai
2005-01-19 19:49   ` Mark Knecht
2005-01-19 21:09     ` Russ Pridemore
2005-01-19 23:08       ` Mark Knecht

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=s5hzmz6vdov.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=markknecht@gmail.com \
    --cc=pochini@denise.shiny.it \
    --cc=pshirkey@boosthardware.com \
    /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