borgie83 wrote:

You can use any external module you like as external modules will not suffer from the hanging note bug.

When you use a multimeter to compare the joystick connector midi signal path with the one to the daughterboard header, you will find that these use the exact same signal. So I have to disagree.

After doing some further research it appears that you're right about a midi module being affected via the gameport as well. I was led to believe it wasn't from certain threads I've read in the past. My MT-32 and SC-55MKII have only ever been connected via a SCC-1A and MPU-401/AT so I've never been able to test the bug via an external module myself. I have tested several sound blasters though with a SCB-7, SCB-55 and DB50XG and besides the CT1740, CT1750, CT2230, CT2760 and CT3900, all had the bug. Haven't tested any Vibras though. Now I won't purchase any SB16 or AWE32 models besides these.

On that note, I just received my CT2760 and ran it through the usual tests and whilst a great card, it does not sound as good as my CT3900.

borgie83 wrote:

King_Corduroy wrote:

if you use the SB16 CT2230 or Awe32 CT2760 (Not Rev 3)/CT3900/CT3980 you won't have to worry about the bug either

I do not remember that being true, from the "hanging bug" topic.
Any AWE32 can be touched AFAIK.

sunaiac wrote:

I do not remember that being true, from the "hanging bug" topic.
Any AWE32 can be touched AFAIK.

Not those with the CT1747 chip

vetz wrote:

sunaiac wrote:

I do not remember that being true, from the "hanging bug" topic.
Any AWE32 can be touched AFAIK.

Not those with the CT1747 chip

This /\

My CT2230,CT2760 and CT3900 contain the CT1747 chip.

For those interested, this is an interesting read:

http://nerdlypleasures.blogspot.com.au/2012/0 … ations.html?m=1

vetz wrote:

sunaiac wrote:

I do not remember that being true, from the "hanging bug" topic.
Any AWE32 can be touched AFAIK.

Not those with the CT1747 chip

Oh, I'll have to check mine then.
I have 2 2670 and one 3900, and I think I had the bug playing doom on the 3900 🙁

gerwin wrote:

No, cornered between the crystals and the main chip we find the CQM chip. The OPL3-L area is empty. A quick search on ebay.com […]
Show full quote

No, cornered between the crystals and the main chip we find the CQM chip.
The OPL3-L area is empty.
A quick search on ebay.com gives me no CT2940 or 2950 with OPL3-L.
This image shows the OPL3-L area filled:

I remember having a discussion with my friend about the CT2940s. Since the solder pads are still present on cards that "lack" it, I wonder if it would become active once they are soldered on. It wouldn't be too hard to get spare chips to solder on either (I have a bunch of dead 701C thinkpad audio boards which feature the same chip and DAC).

Certainly wouldn't be that difficult...

sunaiac wrote:

Oh, I'll have to check mine then.
I have 2 2670 and one 3900, and I think I had the bug playing doom on the 3900 🙁

My CT3900 has CT1747.
I must have imagined the bug.
How come CT1747 eqipped cards are not touched ?

sunaiac wrote:

I have 2 2670 and one 3900, and I think I had the bug playing doom on the 3900 🙁

Look here for more info. Cards with the CT1747 chip are still affected by a bug, but it occurs very rarely (Type 2: "Legitimate" hanging notes). When talking about the hanging note bug, this variant is often ignored, because it is difficult to reproduce it.
Long story short: If you want a proper MIDI interface, don't rely on a Soundblaster card. 😉

Sorry, but I do not believe that info on type2 to be correct. I have not seen anyone give any real documentation of this problem and no user (including myself) I have been able to find here on Vogons have reported problems with Soundblasters with CT1747 chips like the CT2230. If someone wants to give proof of this problem, please provide a recording.

I don't know about "bug type 2". I do know that when there is too much throughput any SB16/AWE will cause slowdowns/stutters. As can be tested with Duke Nukem 3D with high sample rate setting + General midi, or by running TIE Fighter with FX+General midi.
Any SB16/AWE includes both the CT2290(=CT2230) and AWE64 Gold.

vetz wrote:

Sorry, but I do not believe that info on type2 to be correct. I have not seen anyone give any real documentation of this problem and no user (including myself) I have been able to find here on Vogons have reported problems with Soundblasters with CT1747 chips like the CT2230. If someone wants to give proof of this problem, please provide a recording.

Here are just a few references:

http://queststudios.com/smf/index.php/topic,2 … 3.html#msg24793
SB16 vs DBs (hanging / stuck / wrong notes in MIDI)
Re: Hanging note problems with SB16 and DBs

But I'll make a recording just for you, willful ignoramus.

I've experienced the "type 2 bug" on a CT3900 (which seems to be more susceptible) and a CT3980 (where I heard it once, after hours of testing).

However, I am not entirely sure about the Build engine games being type 1 though. There are hanging notes in Build games with models affected by type 1 of the bug, but they don't sound like type 1 (no high-pitched screeches, and they don't seem to occur randomly, like type 1 usually does).

5u3 wrote:

sunaiac wrote:

I have 2 2670 and one 3900, and I think I had the bug playing doom on the 3900 🙁

Look here for more info. Cards with the CT1747 chip are still affected by a bug, but it occurs very rarely (Type 2: "Legitimate" hanging notes). When talking about the hanging note bug, this variant is often ignored, because it is difficult to reproduce it.
Long story short: If you want a proper MIDI interface, don't rely on a Soundblaster card. 😉

I thought I heard it in the doom shareware, when you finish the game and the text scrolls in that dark room where you end up killed.
But I'm not sure anymore, i'll have to try again.