All of lore.kernel.org
 help / color / mirror / Atom feed
From: stan <stanl@cox.net>
To: alsa-devel@alsa-project.org
Subject: Re: Install of alsa 1.0.14.final on Fedora 7
Date: Sun, 15 Jul 2007 12:47:00 -0700	[thread overview]
Message-ID: <20070715124700.4d35d20e@localhost.localdomain> (raw)
In-Reply-To: <20070714154121.0f7c834c@localhost.localdomain>

On Sat, 14 Jul 2007 15:41:21 -0700
stan <stanl@cox.net> wrote:
> And the sound is missing from my app whether I use default or
> plughw:0,0 now. The plughw:0,0 seems to setup OK and the app shows
> that it continues to send output, it just doesn't sound. Seems like
> it is just a small glitch somewhere.  Could be leftovers from the
> cleaned up install too.

Couldn't get this to work as long as I was using time based buffer
allocation.  As soon as I switched back to using size based buffer
allocation, sound was working again.  And as a bonus, the original
problem I reported about high data rates not working under 1.0.14.rc3
went away.  I suspect something somewhere got updated with 1.0.14.final
and is still there despite my efforts to remove everything.  And it
works for both plughw:0,0 and default, though there is some speed
degradation using default compared to plughw:0,0.  I can run
plughw:0,0 at 96000 without underruns, but default has a few underruns
at that rate on the test file.

      reply	other threads:[~2007-07-15 19:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-13 19:48 Install of alsa 1.0.14.final on Fedora 7 stan
2007-07-14  7:09 ` tdavis
2007-07-14 14:27   ` stan
2007-07-14 15:15     ` tdavis
2007-07-14 22:41       ` stan
2007-07-15 19:47         ` stan [this message]

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=20070715124700.4d35d20e@localhost.localdomain \
    --to=stanl@cox.net \
    --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.