Re: CF: client/server sound status?

To: Raphael.Quinet@eed.ericsson.se
Subject: Re: CF: client/server sound status?
From: Philip Brown <philb@csua.berkeley.edu>
Date: Thu, 13 Nov 1997 23:46:40 -0800 (PST)
Cc: crossfire@ifi.uio.no
In-Reply-To: <199711101430.PAA05591@chapelle.eed.ericsson.se> from "Raphael.Quinet@eed.ericsson.se" at Nov 10, 97 03:30:44 pm
Sender: owner-crossfire@ifi.uio.no

>>>>[From Raphael.Quinet@eed.ericsson.se]
    
    ....
    I have a few questions, though.  For instance, what would you think
    about using .wav files by default?  The current code was originally
    designed for rplay, using Sun's .au files.  Now it is possible to use
    different drivers for playing sounds, and they support a variety of
    sound formats (.au, .wav, and others).  ...

    Then comes the
    question of what format these files should be in, especially if
    non-UNIX clients are being developped.  Although the .wav files are
    horrible, they are a de facto standard and are now supported by most
    systems.  So would it be wrong if crossfire was using that by default?

Well, not being biased or anything, but I think .au should still be the
default. 

[Java only supports 8-bit 8000mhz .au format, still. :-)
 The java client is mostly likely going to be THE "non-UNIX" client,
 and possibly even the UNIX client too, in my not-so-humble estimation]

[to unsubscribe etc., send mail to crossfire-request@ifi.uio.no]

Prev by Date: CF: The server refuses login.
Next by Date: CF: traffic on this list (time waster :-)
Prev by thread: CF: traffic on this list (time waster :-)
Next by thread: CF: The server refuses login.
Index(es):
- Main
- Thread