linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Nielsen <ran@krazynet.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Eric Dorland <dorland@lords.com>, Elliot Lee <sopwith@redhat.com>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: esound for PPC
Date: Mon, 11 Oct 1999 20:03:46 -0700	[thread overview]
Message-ID: <19991011200346.A258@gondolin.asf> (raw)
In-Reply-To: <Pine.LNX.4.10.9910111308380.802-100000@opus.bloom.county>; from Tom Rini on Mon, Oct 11, 1999 at 01:09:12 -0700


Tom Rini wrote:
> 
> On Mon, 11 Oct 1999, Eric Dorland wrote:
> 
> > It appears I spoke to soon about sound working perfectly. Whenever esd plays
> > a 16bit wav file, the sound plays at about half speed. Ugg. At least its not
> > static anymore. I'm going to see if I can track down why this is happening
> > (maybe its some on-the-fly endianess swaping slowing it down), but I don't
> > know sound code all that well, so anyone that does, please lend a hand.
> 
> Elliot has the old set of patches ported up to 0.2.15, and hopefully will
> be in 0.2.16 :)

Does this fix the problem Eric wrote about ?
Þere is a bug in dmasound.c that causes sound to be played at 22050 Hz
instead of (usually) 44100 Hz if a beep (from awacs_mksound) is played.

I thought this should happen only if the process is suspended, but I made
beeps with the console while mpg123 was playing.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-10-12  3:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-03  3:48 esound for PPC Eric Dorland
1999-10-03  4:03 ` Elliot Lee
1999-10-03 18:54   ` Eric Dorland
1999-10-03 19:23     ` Tom Rini
1999-10-03 21:46       ` Elliot Lee
1999-10-04  6:27         ` Geert Uytterhoeven
1999-10-04 15:58           ` Elliot Lee
1999-10-05  8:54             ` Benjamin Herrenschmidt
1999-10-05 11:36               ` Elliot Lee
1999-10-06  0:40                 ` Eric Dorland
1999-10-11  6:06                   ` Eric Dorland
1999-10-11 19:43                     ` Eric Dorland
1999-10-11 20:09                       ` Tom Rini
1999-10-12  3:03                         ` Ryan Nielsen [this message]
1999-10-12  3:10                           ` Tom Rini
     [not found]                           ` <19991014193940.A1143@HSE-MTL-ppp4505.qc.sympatico.ca>
     [not found]                             ` <19991017190502.A13068@gondolin.asf>
     [not found]                               ` <19991023152110.A525@HSE-MTL-ppp4445.qc.sympatico.ca>
     [not found]                                 ` <19991023203334.A26715@gondolin.asf>
     [not found]                                   ` <19991024223141.A758@HSE-MTL-ppp4328.qc.sympatico.ca>
1999-10-26  5:29                                     ` Ryan Nielsen
1999-10-26  6:30                                       ` recv programming problem Morningstar
1999-10-26 14:10                                       ` esound for PPC Dan Malek
1999-10-12  3:10                         ` Eric Dorland
1999-10-12  3:20                           ` Tom Rini
1999-10-12  4:26                             ` Eric Dorland
1999-11-02 18:01                           ` Elliot Lee

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=19991011200346.A258@gondolin.asf \
    --to=ran@krazynet.com \
    --cc=dorland@lords.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=sopwith@redhat.com \
    --cc=trini@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).