Newsgroups: rec.arts.int-fiction
Path: news.duke.edu!newsgate.duke.edu!news-hog.berkeley.edu!ucberkeley!sunqbc.risq.qc.ca!nntp.abs.net!uunet!dca.uu.net!ash.uu.net!world!not-for-mail
From: buzzard@TheWorld.com (Sean T Barrett)
Subject: Re: [Glulx] Problem with WinGlulxe and sound
Sender: news@world.std.com (Mr Usenet Himself)
Message-ID: <GxMs2A.3H1@world.std.com>
Date: Thu, 13 Jun 2002 06:15:45 GMT
References: <b5b859fd.0206121603.70444ed4@posting.google.com> <ae9179$np3$1@foobar.cs.jhu.edu> <nBVN8.5919$Vr2.1431336@news20.bellglobal.com>
Nntp-Posting-Host: shell01.theworld.com
Organization: The World Public Access UNIX, Brookline, MA
X-Newsreader: trn 4.0-test72 (19 April 1999)
Lines: 15
Xref: news.duke.edu rec.arts.int-fiction:104960

Kent Tessman <kent@remove-to-reply.generalcoffee.com> wrote:
>(That's why it's preferable to use
>the DS driver in something like WinAmp as opposed to waveOut--so that other
>DS-based audio can play back at the same time.  There is however a greater
>chance of a performance hit/sound glitching under DS, at least in my
>experience.)  Failure to initialize DirectSound is more likely due to a
>COM-level failure, and is therefore much more likely on a pre-NT Windows
>(i.e., 9x or ME).

I would have expected an app with the low system requirements
of winglulxe (or Hugo or any other IF terp, for that matter)
to provide WaveOut support as a fallback so people wouldn't
need to install DirectX just for sound support.

SeanB
