Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Brian Alexander Todd <bat5@po.cwru.edu>
To: linux-sound@vger.kernel.org
Subject: Re: motherboard/cpu combo for sound
Date: Thu, 24 Feb 2000 15:57:40 +0000	[thread overview]
Message-ID: <marc-linux-sound-95141259620911@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-95131303730224@msgid-missing>

I should note that I have a BP6 and while it is great while
its working (for days on end) its bios is known to be flakey
and can cause problems for some people (who feel that stability
is on the month time scale).  I don't want to go on and on 
since this is a sound mailer but check www.bp6.com before you
buy a bp6.  There's a mailing list too.


At 03:09 PM 2/23/00 -0500, Peter Leif Rasmussen wrote:
>If price wasn't a problem for sure I would go with an SMP system, and with
>the AbitBP6(?) motherboard you can even get an economic dual Celeron system.
>Linux 2.4 will have a vastly improved SMP functionality and stability and
>without knowing particular details I would expect multiple CPUs to handle
>time critical pieces better than one CPU that must deal with everything, eg.
>sound recording.
>
>Otherwise I agree that an Athlon system now is the way to go, and I would
>rather go with that than a single CPU Celeron. In any case, when you have
>set your budget and found out how much you want to spend on the mobo+CPU
>subsystem, if comparing Celeron and Athlon, the Athlon is faster for the
>same CPU-speed and I don't know of any issues with regard to sound (the
>Athlon has/had some issues with some video-cards as far as I remember).
>
>In any case, anything but Celeron and Athlon should be avoided due to both
>pure performance and price/performance issues.
>
>Peter
>
>Paco wrote:
>> 
>> On 23 Feb 2000, Laura Conrad wrote:
>> 
>> >
>> > I'm going to be upgrading my machine soon.  I wondered if there's
>> > anyone here who follows the hardware market better than I do, and has
>> > an opinion about what's a good buy at the moment.
>> >
>> > I'd also be interested in what people would get if price were no
>> > object, although that isn't exactly the case with me.  And in
>> > predictions about how much better a machine I can get for less in 6
>> > months.
>> 
>> Well... if price is not an object then I'd load up with a nice fat 1GHz
>> Athlon.  (You'll need to wait about a month or so to get one.)  As far as
>> waiting goes, you'll be able to pick up a 800MHz Athlon in about a month
>> for less than I paid for my 550MHz one month ago.
>> 
>> But... if price *is* an object, and you're looking for bang-for-the-buck,
>> I'd suggest a celeron (although I despise Intel) or an AMD K6-II or
>> K6-III.  I previously used a K6-II-350 and it worked GREAT for hard disk
>> recording.  Midi?  I don;t know anything about that.  I never use it.
>> 
>> regards,
>> -Paco
>
>
>
Brian Todd
email:   bat5@po.cwru.edu
home:    (216) 791-2407
office:  (216) 368-4209
fax:     (216) 368-4969

  parent reply	other threads:[~2000-02-24 15:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-23 12:59 motherboard/cpu combo for sound Laura Conrad
2000-02-23 18:53 ` Paco
2000-02-23 20:09 ` Peter Leif Rasmussen
2000-02-24 15:57 ` Brian Alexander Todd [this message]
2000-04-17 17:36 ` Laura Conrad

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=marc-linux-sound-95141259620911@msgid-missing \
    --to=bat5@po.cwru.edu \
    --cc=linux-sound@vger.kernel.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