Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wjhardaker@ucdavis.edu>
Cc: ding@gnus.org
Subject: Re: need advice from the master
Date: 19 Oct 1998 21:17:09 -700	[thread overview]
Message-ID: <x767dfeuka.fsf@des.castles.com> (raw)
In-Reply-To: Norman Walsh's message of "Mon, 19 Oct 1998 22:40:52 -0400"

>>>>> On Mon, 19 Oct 1998 22:40:52 -0400, Norman Walsh <ndw@nwalsh.com> said:

Norman> I held out as long as I could.

You did better than me...  Really...

Norman> Is it just me, or does everyone suffer from really horrific
Norman> drop-outs and noise whenever their machine does anything other
Norman> than play MP3 files?  I woulda thunk a 250Mhz Pentium II was
Norman> enough.  Silly me.

It's just you?  I have a 233 P-II, and right now I am playing on mp3,
encoding another, typing this message, and I've done compilations at
the same time in the past as well.

I *occasionally* got a break in the song when doing the compilation as 
well.  But really, it took a load average of at least 2 in order to
get a break in performance on decoding mp3s.  In fact, playing an mp3
does almost nothing to my load average (a slight change, but nothing
drastic) (using xaudio, till I find something better).

So, I'm not sure what your problem is...  I wonder if MMX has anything 
to do with it?  Isn't it supposed to have MPEG stuff built into it?
If so, though, I wouldn't think my linux side would ever take
advantage of it.  In fact, I'd be shocked if it did.  Especially since 
I think xaudio would have to add support for it as well as the kernel, 
and I don't think either does...

(the most annoying thing is the slower compilations when I'm doing
encoding...)

(by the way, you know mp3.com has a whole bunch of downloadable free
stuff, though I havn't listened to any of it yet)
-- 
"Ninjas aren't dangerous.  They're more afraid of you than you are of them."


  reply	other threads:[~1998-10-20  4:17 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-16 21:14 Wes Hardaker
1998-10-17 21:53 ` Lars Magne Ingebrigtsen
1998-10-19  3:21   ` Wes Hardaker
1998-10-19 15:58     ` Wes Hardaker
1998-10-19 19:13     ` Lars Magne Ingebrigtsen
1998-10-19 20:14       ` William M. Perry
1998-10-19 20:53         ` Lars Magne Ingebrigtsen
1998-10-19 21:20           ` Wes Hardaker
1998-10-19 22:30             ` Lars Magne Ingebrigtsen
1998-10-19 23:16               ` Wes Hardaker
1998-10-19 23:21                 ` Wes Hardaker
1998-10-19 23:29                 ` Lars Magne Ingebrigtsen
1998-10-20  0:03                   ` Wes Hardaker
1998-10-20  0:13                     ` Lars Magne Ingebrigtsen
1998-10-20  0:41                       ` proff
1998-10-20  0:49                       ` Wes Hardaker
1998-10-20  2:40                         ` Norman Walsh
1998-10-20  4:17                           ` Wes Hardaker [this message]
1998-10-20  9:41                           ` Robert Bihlmeyer
1998-10-20  2:59                     ` David Hedbor
1998-10-20  0:28                   ` Chris Tessone
1998-10-19 23:07             ` William M. Perry
1998-10-19 23:11               ` Wes Hardaker
1998-10-19 16:01   ` Robert Bihlmeyer
1998-10-19 17:05     ` Chris Tessone
1998-10-19 17:27       ` Robert Bihlmeyer
1998-10-19 19:30         ` Lars Magne Ingebrigtsen
1998-10-19 21:21           ` William M. Perry
1998-10-19 23:20             ` Lars Magne Ingebrigtsen
1998-10-20  0:17   ` Stephen Zander

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=x767dfeuka.fsf@des.castles.com \
    --to=wjhardaker@ucdavis.edu \
    --cc=ding@gnus.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).