public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Pawel Worach" <pworach@mysun.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: i810_audio broken?
Date: Tue, 24 Apr 2001 00:30:04 +0200	[thread overview]
Message-ID: <386e136930.36930386e1@mysun.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]

It sounds like when you play music very loud with bad speakers
and it's kind of slow. It's kind of "clinking", describing sound via
e-mail can be very hard.

what value shall i put for the clocking parameter?
is it trial-and-error or is there some formula?

And no, the cut off output does not mean that it worked. :(
xmms says this:
Audio device open for 44.1Khz, stereo, 8bit failed
Trying 48Khz, 16bit stereo.
But it still sounds strange.


----- Original Message -----
From: Jeff Garzik <jgarzik@mandrakesoft.com>
Date: Tuesday, April 24, 2001 0:07 am
Subject: Re: i810_audio broken?

> Pawel Worach wrote:
> > sorry the kernel version is 2.4.3-ac12, so it's kind of latest...
> > 
> > I was using mpg123 (xmms and c/o does exactly the same)
> > if I run it like this Moby sounds very stupid... :)
> 
> "very stupid" means "broken" obviously, but can you be more 
> specific? 
> music is faster? slower?  garbled?
> 
> > [root@whyami mp3]# mpg123 -r 48000 Moby_01.wav.mp3
> > unsupported playback rate: 44100
> > Audio device open for 44.1Khz, stereo, 16bit failed
> > Trying 44.1Khz, 8bit stereo.
> > unsupported sound format: 32
> > Audio device open for 44.1Khz, stereo, 8bit failed
> > Trying 48Khz, 16bit stereo.
> 
> so, since you provided no more output than this, I assume that
> 48Khz/16bit succeeded, which appears perfectly normal for a locked-
> ratecodec.
> 
> You may need the 'clocking' module option, not sure...
> 
> -- 
> Jeff Garzik      | The difference between America and England is that
> Building 1024    | the English think 100 miles is a long distance and
> MandrakeSoft     | the Americans think 100 years is a long time.
>                 |      (random fortune)
> 

[-- Attachment #2: Card for <pworach@mysun.com> --]
[-- Type: text/x-vcard, Size: 103 bytes --]

begin:vcard
n:Worach;Pawel
fn:Pawel Worach
version:2.1
email;internet:pawel.worach@mysun.com
end:vcard

             reply	other threads:[~2001-04-23 22:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-23 22:30 Pawel Worach [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-23 23:04 i810_audio broken? Pawel Worach
2001-04-23 22:56 Pawel Worach
2001-04-23 22:39 Pawel Worach
2001-04-23 22:59 ` Jeff Garzik
2001-04-23 23:08 ` David Woodhouse
2001-04-23 23:17 ` Alan Cox
2001-04-23 21:48 Pawel Worach
2001-04-23 22:07 ` Jeff Garzik
2001-04-23 23:02 ` Alan Cox
2001-04-23 23:34 ` Chmouel Boudjnah
2001-04-24  2:44   ` Doug Ledford
2001-04-23 18:15 Pawel Worach
2001-04-23 19:53 ` Alan Cox

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=386e136930.36930386e1@mysun.com \
    --to=pworach@mysun.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pawel.worach@mysun.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