Ok, then because of bug #1 in my other mail I would say that no one should ever use .DownloadSoundData or .UnloadSoundData repeatedly since they can easily get to a state where memory is not released (At least according to Task Manager). That's a shame, that feature was going to help my music sound a lot better....Luckily, I think my total DLS usage was still barely within limits. -Scott Morgan http://Morganstudios.com ----- Original Message ----- From: "Scott Selfon" <scottsel@xxxxxxxxxxxxx> To: <directmusic@xxxxxxxxxxxxx> Sent: Monday, September 09, 2002 10:42 AM Subject: [directmusic] Re: Can Scripts leak sounddata? > > As I understand it, downloading via a script is equivalent to > downloading (to whatever audiopath is specified) programmatically. If > you close the script, that data is still downloaded. I think the > philosophy was that the developer might still need that data, or it > could be shared (in which case unloading wouldn't be desired). Moral is > unload whatever you download. I tend to just have the developer manage > that, as they know what footprint they need to maintain. > -Scott > > -----Original Message----- > From: Scott Morgan [mailto:scott@xxxxxxxxxxxxxxxxx]=20 > Sent: Friday, September 06, 2002 10:54 AM > To: directmusic@xxxxxxxxxxxxx > Subject: [directmusic] Can Scripts leak sounddata? > > If a script doens't automatically download data, loads data using > segment.DownloadSoundData, and doesn't unload it, does it leak when the > script is closed? > > -Scott Morgan > http://Morganstudios.com > > > >