DownloadSoundData has never worked for me in DMP. I always get an error message, even if I unload everything. It works fine in DMDemo though. This is one of the Downloading bugs I was complaining about in an email a month or so ago. -Scott Morgan http://Morganstudios.com ----- Original Message ----- From: "James Dooley" <jdooley@xxxxxxxxxxxxx> To: <directmusic@xxxxxxxxxxxxx> Sent: Friday, November 01, 2002 2:50 PM Subject: [directmusic] Re: Allright, now I'm REALLY stumped > > There's a little bit of fudge factor, where it may work if your total > number of PChannels is less than an even multiple of 16. If you defined > PChannels 1-4 and 101-104, you'll find that you can successfully > download to PChannels 1-16, but 17 and higher won't work. > > FYI, it works fine in DirectMusic Producer because it manually downloads > all opened DLS collections to all ports in the default audiopath. It > fails in Scott's DMDemo application, because he lets the DirectMusic > performance engine do the downloading. You can do this manually in > DirectMusic Producer by setting the "Download Status" in the > "MIDI/Performance Options" to "Unload" for all DLS sets, then calling > Segment.DownloadSoundData in a script to download the segment. > > -james > > This posting is provided "AS IS" with no warranties, and confers no > rights. > > -----Original Message----- > From: Scott Morgan [mailto:scott@xxxxxxxxxxxxxxxxx]=20 > Sent: Friday, November 01, 2002 9:19 AM > To: directmusic@xxxxxxxxxxxxx > Subject: [directmusic] Re: Allright, now I'm REALLY stumped > > > > James the rule isn't absolute though. I did it with out P-channel 95 > and it worked. Isn't that weird!? > > > -Scott Morgan > http://Morganstudios.com > > > ----- Original Message ----- > From: "James Dooley" <jdooley@xxxxxxxxxxxxx> > To: <directmusic@xxxxxxxxxxxxx> > Sent: Friday, November 01, 2002 12:46 PM > Subject: [directmusic] Re: Allright, now I'm REALLY stumped > > > > > > This is a bug in DirectMusic. You do need to add all the intermediate > > > PChannels to the audiopath to make it work. Basically, downloading=20 > > instruments to a performance with a default audiopath that has "holes" > > > in its PChannel assignments may not work correctly (it depends on the=20 > > size of the "holes" and the total number of PChannels assigned in the=20 > > audiopath). You need to fill in all the "holes" to make the downloads > > > always work right (this includes holes that start at PChannel 1). The > > > reason it worked for me was because I added the instrument to the band > > > at PChannel 13 (which wasn't used in the main segment). If I had=20 > > added it to PChannel 33 or higher, it would not have worked. > > > > -james > > > > This posting is provided "AS IS" with no warranties, and confers no=20 > > rights. > > > > -----Original Message----- > > From: Saul Bottcher [mailto:saul.bottcher@xxxxxxxxxxxx]=3D20 > > Sent: Friday, November 01, 2002 6:40 AM > > To: directmusic@xxxxxxxxxxxxx > > Subject: [directmusic] Re: Allright, now I'm REALLY stumped > > > > > > > > > When I loaded > > > Bjorn's project into DirectMusic Producer, I got a bunch of=20 > > > errors=3D20 about not being able to find the "DLS calmwave" DLS=20 > > > Collection. > > > > Same here (I looked for "calmwave" but it didn't seem to be part=20 > > of the project)... if it brings up a dialog in Producer, could it not=20 > > cause problems elsewhere? > > > > Also, the solution of adding PChannels seems strange if adding=20 > > 14-94 worked (i.e. when there was still a gap at 95). Could there be=20 > > something more to this? Perhaps adding the PChannels causes some=20 > > side-effect elsewhere, and its the side-effect that's actually solving > > > the problem, not the PChannel addition directly? > > > > Saul. > > > > > > > >