Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Maintaining sound card at a specific frequency
Date: Wed, 19 Jan 2005 11:59:56 -0800	[thread overview]
Message-ID: <5bdc1c8b05011911596ebc3144@mail.gmail.com> (raw)
In-Reply-To: <1105938846.41eb499ec3527@www3.webhosting.cx>

On Mon, 17 Jan 2005 06:14:06 +0100, Patrick Shirkey
<pshirkey@boosthardware.com> wrote:
> Quoting Mark Knecht <markknecht@gmail.com>:
> 
> >
> > I guess I'm wondering if there isn't some .asoundrc magic that could
> > be done in my Linux account on this machine that would tell all
> > applications (other than Jack for now) to use some virtual device that
> > handles all frequencies. If that virtual device was the default and
> > the resampling (for Mozilla/games/whatever) was done in software and
> > the sound cards frequency was never changed then I think things would
> > work much better.
> >
> 
> I think you can use default as the device name in .asoundrc and it will be used
> as the default device for all apps.
> 
> Then just give it a plughw instead of hw
> 
> ex.
> 
> pcm.default {
>         type plughw
>         card card1
>         device 0
> }
> 
> ctl.default {
>         type hw
>         card 0
> }
> 

Patrick,
   This was interesting. With this file in place the card was locked
into 48KHz and the controls in hdspconfig wouldn't change it. I wonder
why? Did this allow Alsa to lock up the card so that even hdspconf
couldn't get to it? If so that's going a bit too far I think.

   As soon as I removed the file hdspconf worked again...

   Thansk for the ideas. I think they may be part of the solution eventually.

- Mark


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

  parent reply	other threads:[~2005-01-19 19:59 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
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 [this message]
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=5bdc1c8b05011911596ebc3144@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --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