Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!cs.utexas.edu!rice!uw-beaver!fluke!moriarty
From: moriarty@tc.fluke.COM (Jeff Meyer)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Sound bug
Message-ID: <12498@fluke.COM>
Date: 15 Nov 89 21:10:48 GMT
References: <20903@ut-emx.UUCP>
Sender: news@tc.fluke.COM
Reply-To: moriarty@tc.fluke.COM (Jeff Meyer)
Organization: The John Fluke Mfg. Co., Inc., Everett, WA
Lines: 25

In article <20903@ut-emx.UUCP> ben@ut-emx.UUCP (Benjamin J. Sloan) writes:
>Here's what appears to be a bug.  I've a stack with a command to play a
>digitized sound in it.  If I open the stack and hit the button, the sound
>plays, as planned.  If however, I proceed to use the stack for a while, moving
>around, running button scripts, etc., the sound won't play.  The button for the
>sound does the other things it is supposed to do, but the sound does not come
>out.  The sound won't come back until I re-open the stack.
>
>Could this be memory limited? (I use 1 meg).  It's a small sound (<30K).
>What's going on?

Any chance that you're using SoundMaster?  I've noticed similar situations
(admittedly under MultiFinder) when using SoundMaster with various
applications, where the sound goes out on the application after the first time.

                           "A born-again Christian, Mr. [Rupert] Murdoch
                            claimed that his newspapers -- including the
                            evangelising SUN -- are aids to a moral revival."
                                           -- The Economist, 10/21/89
---
                                        Moriarty, aka Jeff Meyer
INTERNET:     moriarty@tc.fluke.COM
Manual UUCP:  {uw-beaver, sun, microsoft, hplsla, uiucuxc}!fluke!moriarty
CREDO:        You gotta be Cruel to be Kind...
<*> DISCLAIMER: Do what you want with me, but leave my employers alone! <*>