9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Conor Williams" <connorwilliamsie@aol.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] mpg123
Date: Tue, 11 Feb 2003 10:19:36 +0000	[thread overview]
Message-ID: <01fa01c2d1b7$1466ffb0$4d4a800a@will551> (raw)
In-Reply-To: <HOEHIDJJJINMLFPOLFJCIEKPCKAA.nigel@9fs.org>

thanks Nigel
Heard my first plan9 mp3 late last night!
I ended up subtracting 0.001 from that eqation and let
it run the 1 -> 16 loop! doesnt seem to have warped it 2
much!
Russ & co - maybe set the default irq for a sb16 card to
5 as thats what it is out of the box!
l8r
will551

----- Original Message -----
From: "Nigel Roles" <nigel@9fs.org>
To: <9fans@cse.psu.edu>
Sent: Monday, February 10, 2003 2:14 PM
Subject: RE: [9fans] mpg123


> Because it computes (around ine 170 of layer3.c)
>
> 1 - tan(3 * Pi / 4)
>
> which is 0
>
> and then a series of values which involve dividing
> by it.
>
> In my experience, most mp3 code available on
> lunix is full of this kind of stuff.
>
> It's no wonder that if you port an encoder or decoder
> from one platform to another you get a different answer.
>
> It's only because the x86 FPU gives an answer to
> tan(3 * PI / 4)
>
> "that is almost, but not quite, entirely unlike"
>
> -1 that this works at all.
>
> Write out 100 times, "floating point numbers
> are approximate numbers".
>
> I would guess that row 9 of the table is not used,
> so that putting
>
> if (i == 9) continue;
>
> in the loop will fix it.
>
> -----Original Message-----
> From: 9fans-admin@cse.psu.edu [mailto:9fans-admin@cse.psu.edu]On Behalf
> Of Conor Williams
> Sent: 10 February 2003 09:01
> To: 9fans@cse.psu.edu
> Subject: [9fans] mpg123
>
>
> ne one use mpg123?
> I got it compiled but now im getting:
> mpg123 107: suicide: sys: fp: division by zero: fppc=0x6389 status=0xb9b4
>     pc=0x00006380
>
> when I try and play anything using the command
> mpg123 -s pc.mp3 > /dev/audio
>
> any one got Tad Hunts email address - thats the guy who
> ported over mpg123 to plan 9?
> tx
> will551
>
>



  parent reply	other threads:[~2003-02-11 10:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-09 10:05 [9fans] what a mess the Unix world has become Aharon Robbins
2003-02-09 19:48 ` Mike Haertel
2003-02-10  9:00 ` [9fans] mpg123 Conor Williams
2003-02-10 12:02   ` Russ Cox
2003-02-10 14:14   ` Nigel Roles
2003-02-10 14:34     ` Fco.J.Ballesteros
2003-02-10 14:53       ` Axel Belinfante
2003-02-10 15:05         ` Fco.J.Ballesteros
2003-02-10 15:53       ` Conor Williams
2003-02-10 16:41         ` Fco.J.Ballesteros
2003-02-11 10:19     ` Conor Williams [this message]
2003-02-11 11:26       ` nigel
2003-02-13  9:02         ` Conor Williams
2003-02-10 18:13   ` Tad Hunt
2003-02-10 10:04 ` [9fans] what a mess the Unix world has become Douglas A. Gwyn
2003-02-10 11:58   ` Russ Cox
2003-02-10 15:20   ` Ronald G. Minnich
2003-02-11  9:29     ` Douglas A. Gwyn
2003-02-11 10:25       ` Geoff Collyer
2005-01-21  4:38 [9fans] mpg123 lucio
2005-01-21  7:32 ` Aki M Nyrhinen
2005-01-21 10:20   ` lucio

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='01fa01c2d1b7$1466ffb0$4d4a800a@will551' \
    --to=connorwilliamsie@aol.com \
    --cc=9fans@cse.psu.edu \
    /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).