PG Music Home
Out of no where, I am getting the error message when starting up BIAB 2019 that says " Can't find sound file GM.DLS", and then BIAB crashes with another message saying "Access Violation at address:0000xxxxxxxxxxxxx in module 'CoyoteWT.dll'. Write of address 000000000000000018 something.

I can't run BIAB now. Please help.

OS: Windows 10 Pro
BIAB version: Band in a Box UltraPak

Please help.
Thanks
Hi quekou,

Go to your \bb folder using Windows Explorer and find the following two files... intrface.bbw and MySetup.DK -- notice that "intrface.bbw" does not have an "e" between the "t" and "r".

Once you've found the files, rename them to and intrface.bbw.old and MySetup.DK.old

I cannot remember BIAB 2019 exactly. These files might be in the \bb folder or in the \bb\Preferences folder.

Once you're renamed the files, try starting BIAB.

Renaming them as above, returns BIAB to factory settings by stopping BIAB from seeing the set-up files. BIAB will create new versions of these files when it is next started.

Regards,
Noel
Thank you for your detail instruction. I did follow through but unfortunately, it didn't work. I renamed those files and BIAB did seem to be reset when I restarted it but it still shows the "can't find sound file GM.DLS message" and then crashes without the access violation error message it previously displayed before renaming the two files. I also noticed that the right lower corner, there is a pop message says something like " your audio input and out rates should match or something..."

I am totally at loss. I reinstalled BIAB but the same issue still persists.

I haven't run biab in probably for 3 weeks since my last project. I was really caught off guard by this today.

frown
The 'GM' in the name probably relates to General MIDI, and the error relating to Coyote Wave Table might be a good hint as to what might be causing the issue.

Can you try uninstalling and reinstalling Coyote. Search your x:\bb\ folder for a file with the name "SetupCoyoteWT*". You hopefully will find a file named SetupCoyoteWTnn.exe where nn may be a number. If so, run the program and then see if this goes some way to resolve.
I just checked the 2019 BiaB manual and found the following on page 402 of the manual:
"The CoyoteWT can be installed automatically when you install Band-in-a-Box, or you can install it at a later date by running the file SetupCoyoteWT.exe from the C:\bb\Data\Installers folder."
Further to Audiotrack's excellent advice...

It seems that GM.DLS is an older driver and is associated with the Microsoft GS Wavetable Synth.

http://jonlervold.com/microsoft-gs-wavetable-synth-gm-dls-exploring-sounds-beyond-main-bank/

I'd try this and see if it helps...

1. Start BIAB

2. Go into the MIDI driver setup

3. Have a look at the image below. Where I have MS GS Wavetable synth selected (#2 on the image), set this to "No MIDI sound output" (it's the top option).

This may well stop BIAB looking for GM.DLS. Having "No MIDI sound output" is fine if a soft synth such as Coyote WT is used.

4. Now make sure that #3, #4, #5 on the image are set exactly as I have them. Doing this will route your MIDI sounds through Coyote WT.

Regards,
Noel

Attached picture coyote WT default setup.JPG
My understanding is that GM.DLS is essentially the "soundfont" file used by the Microsoft GS Wavetable Synth. On my Windows 10 computer, it is located "c:\Windows\SysWOW64\Drivers" and also in "c:\Windows\System32\Drivers".

Since all Coyote WT does is "wrap" the Microsoft GS Wavetable Synth to present it to BIAB (or any DAW for that matter) as a DXi synth, it relies on the GS Wavetable Synth working properly first. I would test by using the GS Wavetable (not using DXi or VSTi) first to see if you get any sound.
Originally Posted By: AudioTrack
The 'GM' in the name probably relates to General MIDI, and the error relating to Coyote Wave Table might be a good hint as to what might be causing the issue.

Can you try uninstalling and reinstalling Coyote. Search your x:\bb\ folder for a file with the name "SetupCoyoteWT*". You hopefully will find a file named SetupCoyoteWTnn.exe where nn may be a number. If so, run the program and then see if this goes some way to resolve.

thank you. I see there are 4 SetupCoyoteWI files in the x:\bb\data SetupCoyoteWI10, 11, 12, 13. They are the same length, I assume there are the same files. I ran one of the, it ran initially as a normal set up would do but it shows DM.DLS file not found message at the end of the set up. So it failed.

Thanks.
Shawn
Originally Posted By: Noel96
Further to Audiotrack's excellent advice...

It seems that GM.DLS is an older driver and is associated with the Microsoft GS Wavetable Synth.

http://jonlervold.com/microsoft-gs-wavetable-synth-gm-dls-exploring-sounds-beyond-main-bank/

I'd try this and see if it helps...

1. Start BIAB

2. Go into the MIDI driver setup

3. Have a look at the image below. Where I have MS GS Wavetable synth selected (#2 on the image), set this to "No MIDI sound output" (it's the top option).

This may well stop BIAB looking for GM.DLS. Having "No MIDI sound output" is fine if a soft synth such as Coyote WT is used.

4. Now make sure that #3, #4, #5 on the image are set exactly as I have them. Doing this will route your MIDI sounds through Coyote WT.

Regards,
Noel

Thanks again for the suggestion. I followed it through and the 32 version of the biab works now. I can start it up and generate tracks. The 64 version can start as well but it still gives me the gm.dls not found error and the program appears to be wonky and unstable. Some menue or description box not showing up etc.

well at least the 32 version is working so i can finish a project but the gm.dls mystery still remain unresolved.

Thanks
Shawn
Originally Posted By: jford
My understanding is that GM.DLS is essentially the "soundfont" file used by the Microsoft GS Wavetable Synth. On my Windows 10 computer, it is located "c:\Windows\SysWOW64\Drivers" and also in "c:\Windows\System32\Drivers".

Since all Coyote WT does is "wrap" the Microsoft GS Wavetable Synth to present it to BIAB (or any DAW for that matter) as a DXi synth, it relies on the GS Wavetable Synth working properly first. I would test by using the GS Wavetable (not using DXi or VSTi) first to see if you get any sound.


Thanks, I tried to play a midifile using windows media player, no sound comes out of it.....
Maybe you could try updating the driver for the Wavetable Synth?

Attached picture MS GS Wavetable Synth.jpg
If you have the 32-bit version of BiaB working but not the 64-bit, you may just be able to copy over the file.

There are gn.dls files as follows:

C:/Windows/System32/drivers/gm.dls
C:/Windows/SysWOW64/drivers/gm.dls

and the two copies are identical.
If the 32-bit version is working andf the gm.dls file is present in C:/Windows/System32, try copying that file into the C:/Windows/SysWOW64 folder.
Originally Posted By: Gordon Scott
If you have the 32-bit version of BiaB working but not the 64-bit, you may just be able to copy over the file.

There are gn.dls files as follows:

C:/Windows/System32/drivers/gm.dls
C:/Windows/SysWOW64/drivers/gm.dls

and the two copies are identical.
If the 32-bit version is working andf the gm.dls file is present in C:/Windows/System32, try copying that file into the C:/Windows/SysWOW64 folder.



Thanks folks. I followed the directory and found the file gm.dls is named as gm.dls.old. I changed it back to gm.dls and now everything backs to normal. No idea why my gm.dls file was changted to dm.dls.old. doesn't matter matter. BIAB works again!
Thanks for letting us know that you were able to correct the problem and for marking it as resolved. This can assist others in the future. BTW, there is a button available on your original post that automatically marks the thread as [Resolved] wink
© PG Music Forums