(old thread from Jan 2011) GM.DLS on Windows XP 64 bit edition...

PG Music Home

(XP Pro , M-Audio Delta 2496 card)

Previously everything ran fine and stable with BIAB 2009 and sound canvas installed.

Upgraded to 2011 using Everythingpak's "install everything onto my main HDD" option.

Now BIAB startup immediately produces an eror message: "Can't find sound font file GM.DLS". If I click OK through this error, and load any song, more errors then freeze. Basically BIAB simply does not work. Bad news since my normal activity relies on this app every day.

Indeed, there is no GM.DLS in my C:\Windows\System32\Drivers, where I understand it is supposed to be, or anywhere else for that matter. A Windows Registry key "HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/DirectMusic" which is supposed to point to GM.DLS is also empty.

I have no idea whether the file was in there before this upgrade, but the bottom line is, everything worked fine before, and after what should have been a standard 2-3 click upgrade process, everything is now broken

.

Tried running the separate install exe for the Roland synths, (tried both the dxi and the vst) but this did not solve the problem.

Googling has turned up nothing really useful and an email to PGMusic support has not been responded to.

I could probably find the standard M$ GM.DLS from my old XP install disk and copy this into the driver folder, but I believe it is supposed to be replaced with the superior sound fonts which come with the Roland synths. No sign of anything named GM.DLS on the BIAB install HDD either.

Not sure what to do. Can anyone here offer guidance?

TIA

Hi Merk,

Welcome to the forums. Sorry to hear about your problem.

Some questions spring to mind ...

1) When you installed BIAB 2011, did you simply install it your present directory; that is, overwrite the existing directory?

2) Have you tried going to the \bb directory and running BBW.EXE directly from that directory rather than using a shortcut? (I also suggest that you right-click on BBW.EXE and look at the properties to see what date the file was created. This might provide useful information.)

When I've updated BIAB, I've always simply installed the new version over existing files in the \bb directory and I've gone from update to update for a few years now without any hitches whatsoever.

The only GM.DLS on my system is a file dated 2006 (I currently use 2011) in "C:\Windows\System32\Drivers". I find myself wondering if this file is actually the problem because if 2011 used the file, I would expect a more recent date.

Regards,
Noel

Noel,

Good ideas. Turns out I have ended up with two installs, and they are apparently coexisting badly.

The 2011 install created C:\BB\BBW.exe, and the old 2007 version is in C:\Program Files\BB\BBW.exe .

Naturally, the two respective \BB folders are otherwise full of all sorts of stuff, as is normal with BIAB installs, especially since I usually purchase all the extra goodies.

When I did the recent 2011 install from HDD, as I recall, I merely pressed Next>Next>Next... all the way through the install wizard. Thus I assumed it would sort out of all the old-versus-new file locations issues.

I have been starting the 2011 version from its newly added desktop shortcut. Your idea to run directly from the exe produces the same error, and the new shortcut points to the correct (new) exe. I have not tried running the old version now that I have discovered its exe is still in there - afraid that might confuse things even more.

A search produces no copy of the GM.DSL file anywhere on the C: partition, or anywhere else for that matter. I suspect the muddled dual installs have led to muddled registry settings which are needed to help everything work together. But somewhere, I presume I still need to have a copy of GM.DSL, at a minimum the original old M$ version, or preferably a replacement built from the bundled Roland synths.

Probably, the best approach is to thoroughly uninstall both, and re-install only the new one. It is not clear whether this will sort out the missing driver problem, but if it doesn't, I suspect is would be easier to resolve after untangling the two installs.

However, I see three problems with this: 1) How to go about doing the uninstalls. Do I need to do some registry cleanups as well? 2) I paid an upgrade price for the 2011 - will my copy still install and run OK if I first purge all traces of the 2007 version? 3) I need to dig into the old file structure and find all my old songs and whatnot, and any other goodies I want to keep. Aside from being a PIA, I wonder where best to put those old files so as not to confuse the new install.

Finally, assuming this is the way to proceed, wonder whether the same GM.DSL issue will still be there?

Any thoughts on this, Noel or anyone?

Thanks

merk,

If I was in this situation, before doing an uninstall of version 2009, what I'd do is ...

Delete "c:\bb" created by version 2011. It's not working properly anyway so there's nothing to lose.
Rename "c:\program files\bb" to "c:\bb" (or preferably copy of "c:\program files\bb" if you have the hard drive space) so that all your 2009 and earlier files are still on the computer. Personally, I would aim to keep a copy of "c:\program files\bb" so that I could go back to it if need be.
Install version 2011 to "c:\bb" directly over the top of the 2009 version that now resides in "c:\bb"
See what happens when BIAB is installed.

What I also suggest is that you don't race into doing the above. Give it a day or so because I am sure that some BIAB channel experts with much more knowledge than I have will also give an opinion. My feeling is that the gm.dsl file is not the problem.

Good luck,
Noel

all good advice. will do this, including waiting a day or two in hopes this thread attracts more varied opinions and advice.

meanwhile, to add more clues, if I do go ahead and click through the startup no GM.DSL error and load a song, after clicking "Play" the next error I get is "Beat Map Stretcher unable to load wav file". This is presumably because the wavs which were supposed to be supplied by the GM.DLS map are not available. After this, BIAB freezes and can only be quit with task manager.

hopefully someone can offer advice on my concerns 1) and 2) in my last post.

thanks again

As to PG music not responding to emails I doubt on Sunday early in the morning anyone is home.

You don't mention what O/S you are running.

Could be user account problems, do you have Vista maybe?

Error messages are often bogus. Microsoft never really has had that down pat, so you send a command and it tells you some BS about this or that and it's just wrong.

I would have run the old version to see what happened. They can co-exist.

To my mind there is nothing in the new version you cannot run off the external drive, nor is there any reason you cannot run the old version out of the old directory. bbw.exe or oldbbw.exe, any of those should actually run.

There have been so many people on so many systems that there are only 2 logical reasons for this.

1. Something you misinterpreted on installation. OR
2. The hard drive has something wrong with the actual bbw.exe file.

Other considerations.

It's best to shut off stuff like Virus protection programs before installing anything.
If running Vista or Win7 turn off User Account Control.

I would use the search function in the operating system to find all instances of bbw, looking for exe files.

Hi again, merk,

I wasn't thinking clearly when I wrote the above reply. By far the easier option is to keep "c:\program files\bb" as your working directory as all pointers to Realtracks and Realdrums are present.

All you really need to do is to delete ver. 2011 and reinstall it. When you do, make sure that you insert the path "c:\program files\bb" wherever you see "c:\bb" in the install options. I guess Realband will be "c:\program files\realband".

While my previous solutions would work, this solution is simpler.

Regards,
Noel

@John: Just to clarify, my initial post notes that I run XP. I run only a single user, admin, and no anti-virus on that box. I run it on my home LAN behind a strict linux firewall/router and I download nothing to it and install nothing except from "trusted sources" or if downloaded and scanned on a separate machine. It is a very clean music-only setup with barely five or six apps on it, and has run two older versions of BIAB for years without problems. (I use a Mac or two other XP boxes for all other uses including email and internet browsing.)

It is true, the "Everythingpak" HDD install options were several, but I chose the one to install "everything" to my own, main HDD because I prefer not to have additional devices attached if I don't need it. The install thereafter was "Next, Next, Next..." as far as I can recall, although you are right, I may have selected something along the line which helped create this problem. Also, I have done thorough searches for the file that the error refers to. Finally, as I mentioned, the new version simply does not play songs, it crashes. I am a great fan of BIAB, have used it for years in simple ways on a regular basis. But simple, crystal clear user interfaces and tight, fool-proof documentation I don't consider as among the program's greatest strengths. Finally, the email to BIAB support was a week to ten days ago. I am really not trying to complain, just looking for help to get running again ASAP. Thanks for any suggestions.

@Noel: I understood your meaning anyway. Thanks

BIAB & RB do not write anything to the registry. Just delete everything the bb folder and the RealBand folderand start fresh.

@silvertones - good to know. thanks!

For what its worth, I don't have the GM.DLS file on my computer anywhere either and 2011 UltraPlus Pak runs great (Vista HP). Perhaps try running from the usb drive and see what happens. If that doesn't work I'd be looking into getting the HDD from PG Music replaced.

Does the everything install include the VSC? If not you might want to install that again.

Good luck.

Hello Merk,

GM.DLS is the default General MIDI sound file included with Windows. It is associated with the GS Wavetable, and is used by the Coyote Wavetable DXi synth. A quick fix for you is to go to Opt. | MIDI Driver Setup in Band-in-a-Box, click on [DXi Synth Settings], and select the Roland VSC-DXi.

This doesn't solve the problem of your missing GM.DLS, but you should be able to find out how to replace that file - perhaps on Microsoft's knowledge base. You could probably copy it from another Windows XP computer. It should be in C:\Windows\system32\drivers.

It is ok if you have both version 2011 and 2009 installed on your computer, in different folders. That won't affect the operation of Band-in-a-Box. Some people keep a backup of their older versions that way. Noel's suggestion is good, make a copy of your BB2009 folder to C:\bb, then install version 2011 from your hard drive to this folder.

OK, Thanks everyone for the various suggestions and advice.

I will try these and report results back here.

OK. Progress (maybe) but problem not resolved yet. Here is what I have done thus far:

1) Deleted entire folder C:\BB This was the install folder of new 2011 version, as that's were the 2011 exe was so this delete is to to prepare for a reinstall.

2) Copied entire 2009 version folder C:\Program Files\BB to D:\BB, as a backup, mainly to b/u its associated files. In fact, I don't care to retain runnable copies of both versions, so in due course I will delete all but my own compositions and other goodies in here. However, I will only do this after the new 2001 install issues are sorted.

3) Copied entire 2009 version folder C:\Program Files\BB to C:\BB putting the 2009 version and all its allied goodies to where 2011 seems to want to install.

4) Deleted folders C:\Program Files\Coyote and C:\Program Files\Roland. I wanted the 2011 to put its versions of these synths where it wants them to be, without potential conflicts.

5) Ran Control Panel>Add/Remove Programs and removed a Roland DX synths app (which were probably now merely registry entries pointing to stuff in the folders I deleted in step 4).

6) Also in the Add/Remove Programs list was an entry for BIAB 2011. Probably should have looked in here first. To be safe, I renamed my new instance of C:\BB (which is now 2009, but was 2011) to C:\BB temp, and double checked that the BIAB HDD was not connected, then hit remove for the 2011 BIAB app. After it did its thing, I renamed the directory back to C:\BB.

7) Also in the Add/Remove Programs list was an entry for something called Band in a Box Server. This BIAB server entry indicated a file size of 40Gb, so it clearly pointed to the HDD holding the new 2011 version, even though this was not now connected. I decided it best to to leave that alone.

8) I ran some searches in C:\ on "Band" and "Roland" and "BB". Aside from the some unimportant stuff and the 2009 stuff in C:\BB which I intended to retain, I found a few things in C:\Documents and Settings\All Users\Star Menu\Programs and deleted these.

9) OK, just to be safe, I then did a restart of the system, this time with the 2011 HDD plugged back in, and started the "Band In A Box Setup" exe on the 2011 HDD. I chose "everything", the third option.

Seeing this again, I recall that the last time, I chose the fourth option, "Custom" but once in there, I selected everything again. When the wizard got to the file locations, I let it option to C:\BB, the default. The difference this time is that that is where my old stuff now lies. The installer's file copy is then off and running.

10) The install process ran on for 40 minutes or so, the when the progress bar reached the end and the final update announcement came up ("Installing Coyote Wave Table") and a second window opened, with its own progress bar. When the Coyote install reached the end and its final update announcement came up ("Registering Files"), all of a sudden up popped an error message, my old friend: "Can't find sound font file GM.DLS"

!?!

11) I clicked OK through this error box, and the coyote install window closed itself, and the original BIAB install window announced its completion and offered a "Launch Band in a Box" tick box, which I ticked, then hit "Finish".

12) The 2001 version does then launch, and does not display the GM.DLS error immediately on launch as before.

13) Next, before trying to play anything, I look at the MIDI/Audio Drivers Setup under Opt. menu. Choices under output drivers are three: Microsoft MIDI Mapper, Microsoft GM Wavetable SW Synth and Delta AP MIDI (my midi/audio card). No sign here of Roland or Coyote. When I try the Driver Wizard, the only alternative shown for internal sounds is again the Microsoft GM Wavetable SW Synth.

It appears no new synths have successfully installed, although no error massage warned my of this during the "Install Everything" from HDD run.

14) Just to test, I select the MS GM Wavetable, and the try loading a demo song from the new 2011 style demos. This loads, but when I push play, I get "Beat Map Stretcher was unable to load in the Wav file" error, which presumably is linked to the lack of wav files. This is probably because the MS GM SW Synth needs GM.DLS to run.

Conclusions thus far:

Apparently, in a standard Windows install, the OS supplies GM.DLS, and that's what MS GM Wavetable SW Synth uses.

One BIAB user a few posts back checked and said his system did not have this file either but runs OK. My best guess is that when alternative soft synths are installed, GM.DLS is replaced with something else, pointers to it (pointers either in BIAB or somewhere in Windows itself - registry?) are modified.

However, in my case when the BIAB 2011 synth installers try to put their own substitute wavetable files in place, they did not find the "original equipment" GM.DLS because mine had already been replaced by my 2009 BIAB install.

However, neither can they find any alternative wavetables for one of two reasons: the first time around my old install was not in the same directory and the new installers couldn't find pointers to the alternative wavetable files; and the second time around I had deleted something. If this is what's going on, I have probably inadvertently muddled things worse by deleting old Coyote and Roland folders in my attempt to clear the decks for a clean reinstall.

whew... what a wearying mess.

OK, here's what I think I ought to do now:

I. Get a copy of GM.DLS and put it in its proper location. (It's probably in a CAB file somewhere on the original Windows XP install disk.)

II. Try again to install Roland or Coyote from the 2011 HDD.

The one thing which worries me with this plan is what pointers to GM.DLS need to be set and where. In an earlier post I mentioned that I had seen something about a registry entry pointing to GM.DLS. I'll try to find out more on that.

Before going ahead and doing this, I thought it better post my results thus far, and then see what advice I get from the helpful expert panel following this thread. In particular, if my plan is the correct way forward, which of Roland or Coyote should I use (or both) and specifically how best to go about installing?

Thanks again to all. Sorry for lengthy post - hopefully this thread will help some one else, should anyone be unlucky enough to stumble into the same problem. (Assuming we can get it sorted !

)

Hi Merk,

Here's something else to try (following on from Andrew's post above).

Start up BIAB, open Opt | Midi/Audio Driver Setup and try setting the drivers as shown by the yellow highlighting in the image below. This works on my computer.

Regards,
Noel

Noel,

Hmmm. May be narrowing in on it.

If I setup Midi/Audio Driver Setup exactly as you show, then load and play a song, some songs work partially, some not at all.

It appears that midi parts (yellow in the top of the synth window) are now playing (!) but RealTracks (green) will not. If I load any song with Realtracks parts, I get the "Beat Map Stretcher was unable to load in the wave file" error. Only the midi parts will play (usually a drum part).

A cursory inspection of the folders and files in C:\BB\Realtracks appears to be rether less than in the 2011 HDD folder of the same name. I will copy all I can from the 2001 HDD to C:\BB\Realtracks and try again.

__________________

OK. Copied from the PG music HDD ..\BB\Realtracks into C:\BB\Realtracks until I my C: capacity maxed out. Still I am trying many demo songs and virtually no Realtracks parts will play. Only midi parts and once or twice a Realtrack drum part seems to work.

There are now over 49Gb of files in C:\BB/Realtracks, and only 30+ Gb in EverythingPak F:\BB\Realtracks. But still, on hitting play on most demo songs, I get the "Beat Map Stretcher was unable to load in the wave file" error, and none or almost none of the parts will play.

What am I doing wrong here?

TIA

Quote:

OK. Copied from the PG music HDD ..\BB\Realtracks into C:\BB\Realtracks until I my C: capacity maxed out. ..... What am I doing wrong here?

Sounds like you are trying to put more on your C: disk than it has the capacity to hold.

What is your C: drive size and how much freespace does it currently show (rightclick on the disk icon and choose "properties").

--Mac

Quote:

Sounds like you are trying to put more on your C: disk than it has the capacity to hold.

well, obviously. This is not the problem. I can always find some things on C: to trash or increase the C: partition size.

But that's not the point.

I already have put a ton of Real Tracks files in place in C:\BB\Realtracks, already apparently 10 gigs more than the 30 plus gigs provided with the 2011 HDD EverythingPak. (I presume there are more because there must many different ones leftover from the earlier install.)

The real question is, why won't any of these Real Tracks play? I have tried many different demo songs; certainly some of these songs must use some of the 40Gb of Realtracks I already have in place.

It seems either I have some settings wrong somewhere, or for some other reason my bbw.exe can't find its way to the RealTracks files, even though I believe I have them in the default location.

Anybody?

Well, if the install stalled due to running out of disk space, then to me it *obviously* is very likely to have those Realtracks that it did install fragmented all over the drive and that can make for problems when BB attempts to load them.

I have personally experienced the need to defragment a drive after installing BB and Realtracks on it, to prevent dropouts and inability to find and load certain selected realtracks - and that was on a disk that was only half full or so. But was a bit fragmented after the big realtracks installation. Windows reported the same old, "you do not need to defragment at this time" it always does when doing a diskcheck, they did not have streaming audio in mind when they wrote that code. So as for defragmenting the disk, I just routinely do it anymore and my music plays well.

So the disk size and amount of freespace left after the install can be VERY important.

--Mac

Quote:

Quote:

Sounds like you are trying to put more on your C: disk than it has the capacity to hold.

well, obviously. This is not the problem. I can always find some things on C: to trash or increase the C: partition size.

But that's not the point.

I already have put a ton of Real Tracks files in place in C:\BB\Realtracks, already apparently 10 gigs more than the 30 plus gigs provided with the 2011 HDD EverythingPak. (I presume there are more because there must many different ones leftover from the earlier install.)

The real question is, why won't any of these Real Tracks play? I have tried many different demo songs; certainly some of these songs must use some of the 40Gb of Realtracks I already have in place.

It seems either I have some settings wrong somewhere, or for some other reason my bbw.exe can't find its way to the RealTracks files, even though I believe I have them in the default location.

Anybody?

I'll respond.It's crazy to even attempt to trouble shoot something that hasn't even been installed properly due to HD space limitations.Go back and delete the bb folder & the RB folder. DO NOT INSTALL THE PROGRAM AGAIN.Hook up the PG external drive & try running the program right from there.Report back.

Without a good clean swap space so the songs can render I figure you are snookered.

The software is using Real stuff to start with, then it writes a bunch of sound files for your song. I've never explored how much, but maybe some guru named Mac can figure that out. Is it one .wav file per instrument or 1 mp3 file per instrument, or 1 big wav file or...

I don't know.

But if you can change the volumes of instruments after the song is rendered, then there are multiple files ....

However it the file to start with is picked up 'all over the drive' due to fragmentation as previously mentioned, AND then the rendered file is all over the drive...well top that off with limited real memory and a slow processor, the result is not going to be good.

Have you installed/reinstalled and/or updated the drivers for your midi sound module (M-Audio I think it was)?

I was wondering if you are a Windows XP X64bit user?

On a 64bit system you should find GM.DLS in the following directory "C:\WINDOWS\system32\drivers\etc\gm.dls"

- If you do not find it
I would also recommend re-applying your latest service pack for Windows and downloading the newest version of Direct X for Windows XP.

Hello,

Quote:

It appears that midi parts (yellow in the top of the synth window) are now playing (!) but RealTracks (green) will not

Right, the MIDI tracks now work fine because the Roland VSC-DXi doesn't use GM.DLS. I don't know why your audio tracks aren't working - that may be an entirely different problem. Could you try opening the file Listen.MGU and see if both the MIDI and audio parts play? You should find this file in the '\bb\Tutorial - Audio Harmonies' folder.

Also, if you could try running Band-in-a-Box directly from the PG Music hard drive and see if everything works fine there... that would be very helpful. Remember to select the Roland VSC-DXi before attempting to play a song, since BB will select the Coyote WT by default.

OK. Since my last post, I have done this:

1) Using Remove Programs - removed every app connected with BIAB, including Coyote and Roland stuff.

2) Deleted all related folders and files, both old install and new. Only exception to this is I put my old compositions into renamed folder on a separate drive, for archive. Also, I checked - with all this deleted it leaves well over 70 Gb of free space on C: partition. My HDs are defragged weekly automatically, but I ran a check, and fragmentation was less than 0.01%.

3) Searched further with google, and located a copy of GM.DLS. Copied it into C:\Windows\System32\Drivers. Updated by hand the registry entry which is supposed to point to this file's location.

4) Then I tried a clean install. Ran the setup program on the 2011 HDD, selected option 3 (everything) and otherwise selected defaults all the way through. On this install, I did not get the "Can't find sound font file GM/DLS" error at end of install or on launch of BIAB, as before.

5) Adjusted Midi/Audio Drivers setup. Load and play any song with Real Tracks or Real Drums parts. Get error message "Beat Map Stretcher was unable to Load in the wav file". If I click through this message, the Real Tracks parts are generated, but Play only produces sound from midi parts (yellow). On most demo songs this is drums and count-in click only, on a few songs there are other midi instruments which play. No real tracks parts (green) or real drum parts produce any sound.

6) Tried John's suggestion next. delete BB and RB folders. Run BIAB from the 2011 HDD. Double checked Setup Midi/Audio Drivers setup. Load demo songs, and try to play. Same error: "Beat Map Stretcher was unable to Load in the wav file". Same play results as above, no real tracks or real drums, but midi works.
___________

So, to summarize the events so far, here is how I have got to this situation.

1)Had an older version of BIAB running fine for years. Received the 2011 HDD EverythingPAK.

2)Without changing anything on my existing install, I ran the 2011 HDD setup program, selecting the Install everything onto my HDD option, and selected (to the best of my memory) default on file location.

3)First install apparently went to a different directory from existing install, which according to some posters should not necessarily be a problem. Attempts to play produced two errors "Can't find sound font file GM/DLS" on program launch, and "Beat Map Stretcher was unable to Load in the wav file" on play.

4) Made some settings changes in Midi/Audio Drivers Setup (thanks Noel) and got midi to play, but no real tracks.

5) Next, I made one or two attempts like this: remove and, after moving old install files to same location as new install default, re-install. Same errors and lack of real tracks.

6) (as in this post) Attempted to purge my system of all traces of old install, added copy of GM.DLS to drivers folder, and tried running from 2011 HDD. Then tried another install of BIAB, again using everything option, default location. Both of these produces same result. "GM/DLS" error is gone, but "Beat Map Stretcher" error remains and real tracks /real drums parts do not play though midi parts do.

I think the root cause must either a parameter setting in some file somewhere or a entire file in the wrong place or missing somewhere. Thinking logically, since the malfunction is the same now running from 2011 HDD or onboard drive, then the problem is either somewhere in my XP setup, or it is somewhere in the BIAB files so it manifests on both HDD play and installed play.

I really want to avoid having to clean-install my OS just to get my BIAB upgrade to work.

Anybody have any more ideas as to what could be causing the "Beat Map Stretcher" error and lack of realtracks play?

Thanks

Quote:

Anybody have any more ideas as to what could be causing the "Beat Map Stretcher" error and lack of realtracks play?

Just scanning the last few posts, so forgive if this has been covered, but re. the lack of RT sound, have you followed Andrew's suggestion to play Listen.mgu? (It has a factory installed audio part associated with it.) I think his notion is to distinguish whether the issue is really with RTs or whether you have a general audio issue. (Does another audio app produce sound?) You're using the 2496 ASIO driver, right? Try playing Listen with all midi parts muted, and the 2496 interface open. The mixer shows a signal, right? If not, there's your starting point for troubleshooting. If yes, then try a song with a RT soloed. If the mixer now shows no signal, at least you've narrowed troubleshooting from a general audio issue to the RTs themselves. (What happens if you double click on one of the raw .wma RT files and your default audio player fires up - does it sound?)

BTW, when troubleshooting ASIO, it's best to refrain from having more than one audio app open. (Especially true for ASIO4ALL, since it doesn't like to be shared - not an issue here). Also, in the Audio Drivers Dialog, there's an ASIO Always on toggle. It shouldn't matter here, but you might try toggling it just in case.

-Ron

Find another computer and try BIAB from the usb drive it came on and see what you get. What about RealBand?
Good luck.

Quote:

have you followed Andrew's suggestion to play Listen.mgu?

The audio plays fine from this file. Looking inside shows that the audio file connected with Listen.mgu is a wav, rather than an wma like all the regular RT files. Another clue!

Quote:

You're using the 2496 ASIO driver, right? Try playing Listen with all midi parts muted, and the 2496 interface open. The mixer shows a signal, right?

I normally use ASIO, and yes, the 2496 mixer shows a signal playing Listen.

Quote:

What happens if you double click on one of the raw .wma RT files and your default audio player fires up - does it sound?

Aha! Default audio player is MediaMonkey. Although wma is selected as one of my MediaMonkey filetype associations, turns out the RT wma's won't play here either. Looking like a codec problem.

I then discover that the RT wma's play fine with VLC, and with Media Player Classic, both of which which I also have installed but never use. A little googling suggests that the codecs for wma's have many versions and some seem to be application-specific.

I try re-installing Media Player Classic, as it was developed originally as a direct Windows Media Player subsititute, figuring that this might sort out the driver/codec issues.

Retry BIAB and load a song with RT parts. BINGO!

Conclusion - somehow between old BIAB install and new one, access to the proper codec or driver for wma's was broken. This problem may or may not have been connected with difficulties with missing GM.DLS or my early efforts to fix that. At any rate, back in business.

Thanks to everyone who offered ideas and help here!

Glad you got it sorted. Obviously something happened to your computer if GM.DLS disappeared; maybe your WMA CODEC got messed up at the same time.

I'm glad it's working now.

Sorry for digging out this old thread, but I ran into quite similiar problems on my XP64 box and would like to share the way, I finally got it sorted out:

Any Win32 application will not get access to the Windows\system32 folder which is intended for 64bit applications. Instead it's (transparently) redirected to the Windows\SysWOW64 folder which has the same structure and contains 32bit runtime files.

So my remedy was to get the GM.DLS from "Windows\system32\drivers" and put a copy to "Windows\SysWOW64\drivers\" and additionally to "Windows\SysWOW64\drivers\etc\", just to be sure :-)

After doing so, installation did not complain anymore and the application seems to work properly.

I hope this may help also on other 64bit installations...

>>> So my remedy was to get the GM.DLS from "Windows\system32\drivers" and put a copy to "Windows\SysWOW64\drivers\" and additionally to "Windows\SysWOW64\drivers\etc\", just to be sure :-)

Thanks for the tip.

>> my XP64 box

To be clear, this issue is peculiar to Windows XP 64
( http://technet.microsoft.com/en-us/library/bb457053.aspx released in 2001)... correct?

>>> my XP64 box

I'm using a cheap onboard soundchip, possibly this might have been a reason, see below..

> To be clear, this issue is peculiar to Windows XP 64

I didn't try installing BIAB on Win7 (and never will on Win8...) but I think that it's common for all 64bit Windows versions: Microsoft are sharing most of the code (some people swear that there is still 16bit code from Windows 3.x inside) between their versions and I din't see any differences between XP64 and Win7 concerning the handling of 32bit applications.

But anyway, the main point is not the OS but the driver setup procedure for the sound hardware: If the driver setup is not aware of the "specialities" of a 64bit system, it just puts the files into system32 but not into the folders for the 32bt sandbox.

It strongly depends of the sound hardware manufacuters. But maybe your setups could care about? :-)