Reply-To: "Kent Tessman" <kent@remove-to-reply.generalcoffee.com>
From: "Kent Tessman" <kent@remove-to-reply.generalcoffee.com>
Newsgroups: rec.arts.int-fiction
References: <b5b859fd.0206121603.70444ed4@posting.google.com> <ae9179$np3$1@foobar.cs.jhu.edu> <nBVN8.5919$Vr2.1431336@news20.bellglobal.com>
Subject: Re: [Glulx] Problem with WinGlulxe and sound
Lines: 43
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID: <WPVN8.5920$Vr2.1436529@news20.bellglobal.com>
Date: Thu, 13 Jun 2002 01:11:27 -0400
NNTP-Posting-Host: 64.231.200.141
X-Complaints-To: abuse@sympatico.ca
X-Trace: news20.bellglobal.com 1023945078 64.231.200.141 (Thu, 13 Jun 2002 01:11:18 EDT)
NNTP-Posting-Date: Thu, 13 Jun 2002 01:11:18 EDT
Organization: Bell Sympatico
Path: news.duke.edu!newsgate.duke.edu!nntp-out.monmouth.com!newspeer.monmouth.com!news.xnet.com!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!sunqbc.risq.qc.ca!torn!webster!nf1.bellglobal.com!nf2.bellglobal.com!news20.bellglobal.com.POSTED!not-for-mail
Xref: news.duke.edu rec.arts.int-fiction:104954

Actually, now that I think about it, I may have lied, slightly.

A DirectSound initialize call (specifically CreateSoundBuffer(), I think)
can fail if both it and a previously playing sound buffer have demanded a
hardware mixing buffer, so that either the hardware and/or a mixing channel
for the buffer are unavailable.  But if a program is doing this when it's
not necessary, it's being (in my opinion) a Bad DirectSound Citizen.

"Kent Tessman" <kent@remove-to-reply.generalcoffee.com> wrote in message
news:nBVN8.5919$Vr2.1431336@news20.bellglobal.com...
> "L. Ross Raszewski" <lraszewski@loyola.edu> wrote in message
> news:ae9179$np3$1@foobar.cs.jhu.edu...
> > I've had intermittet trouble with winGlk's sound abilities that I
> > think are related to apps not dying properly (after crashing winglulxe
> > during various GWindows tests, Glulxe refused to produce sounds untill
> > the next reboot).  The error you give sounds like it's linked to some
> > other program having control of DirectSound when Glulxe starts. Make
> > sure you're not running anything else that uses sound (Like Windows
> > Media Player, Winamp, or a sound-providing web browser plug-in when
> > you start Glulxe.
>
> Actually, one of the pluses of DirectSound is that no single program
> controls it, unlike the older Windows multimedia subsystem.  Any number of
> DirectSound-using programs should be able to play back sound at a given
> time--no one program owns the device.  (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).  Not that this helps directly, but it may give an idea
of
> where to start looking.
>
> I've had more than a few (dozen) headaches dealing with
DirectSound/DirectX
> crashes/failures/freezes/etc. on 9x.
>
>
>


