VOGONS


First post, by Linoleum

User metadata
Rank Member
Rank
Member

I’m running into a strange issue with a Sound Blaster 16 CT2230. Whenever I plug a joystick into the gameport, all MIDI output from the card stops—both from the internal MIDI header and from the gameport using an SB MIDI splitter cable.

Before anyone asks: yes, I’ve tried multiple gamepads that work perfectly on my other systems. The jumpers are correctly set, MPU‑401 is enabled, and the port is set to 330. If I swap the card for my other SB16 (CT2970), everything works flawlessly with the exact same MIDI devices and the same joystick.

Has anyone seen this behavior before or know what might be causing it?

P3 866, V3, SB Audigy2
P2 400, TNT, V2, SB Audigy2 ZS
P233 MMX, Mystique220, V1, AWE64
P166, S3 Virge, SB32, PicoGus
486DX4 100, CLGD5424, SB32
Prolinea 4/50, ET4000, SB16
SC386SX 25, TVGA8900D, Audician32
286 10, ATI VGA, Forte16
PS2 30/286, SBP

Reply 1 of 8, by moturimi1

User metadata
Rank Member
Rank
Member

I owned a CT1750 in the 1990s with attached Wavetable daughterboard.
I experienced also the lack of midi music when I had my flightstick attached to the gameport. It took me some time to figure out that the attached joystick was the root cause of the missing midi music.
So at least for the CT1750 this phenomena is well known. I don't know if later versions of SB16 were fixed.

Reply 2 of 8, by Linoleum

User metadata
Rank Member
Rank
Member
moturimi1 wrote on 2026-01-27, 14:51:

I owned a CT1750 in the 1990s with attached Wavetable daughterboard.
I experienced also the lack of midi music when I had my flightstick attached to the gameport. It took me some time to figure out that the attached joystick was the root cause of the missing midi music.
So at least for the CT1750 this phenomena is well known. I don't know if later versions of SB16 were fixed.

Yeah it has a very similar design and some versions share the same DSP (4.11 like mine)... Interesting!

P3 866, V3, SB Audigy2
P2 400, TNT, V2, SB Audigy2 ZS
P233 MMX, Mystique220, V1, AWE64
P166, S3 Virge, SB32, PicoGus
486DX4 100, CLGD5424, SB32
Prolinea 4/50, ET4000, SB16
SC386SX 25, TVGA8900D, Audician32
286 10, ATI VGA, Forte16
PS2 30/286, SBP

Reply 3 of 8, by Linoleum

User metadata
Rank Member
Rank
Member

I did try a few gamepads in my first tests, but all three were Gravis Gamepad (classic) models. I pulled out a few more controllers today, and everything works properly when using a Gravis GamePad Pro or a no‑name gamepad.

First time I’ve ever encountered that kind of problem with any of the 10+ Sound Blaster cards I’ve owned, or the bazillion Gravis gamepads I’ve used over the years.

P3 866, V3, SB Audigy2
P2 400, TNT, V2, SB Audigy2 ZS
P233 MMX, Mystique220, V1, AWE64
P166, S3 Virge, SB32, PicoGus
486DX4 100, CLGD5424, SB32
Prolinea 4/50, ET4000, SB16
SC386SX 25, TVGA8900D, Audician32
286 10, ATI VGA, Forte16
PS2 30/286, SBP

Reply 4 of 8, by maxtherabbit

User metadata
Rank l33t
Rank
l33t

Perhaps the 5V supply at the joystick port is insufficient to drive the transistors in the gamepad and the optoisolators in the midi adapter at the same time?

Reply 5 of 8, by NeoG_

User metadata
Rank Member
Rank
Member

I think you'd need a scope on pins 12 and 13 of the joystick port to see what is happening to the MIDI signal lines when the gamepad is connected

98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer

Reply 6 of 8, by Linoleum

User metadata
Rank Member
Rank
Member
NeoG_ wrote on 2026-01-28, 01:14:

I think you'd need a scope on pins 12 and 13 of the joystick port to see what is happening to the MIDI signal lines when the gamepad is connected

You mean pins 12 and 15?
computer_midi_game_port_by_mad_king_corduroy-d7xfbct.gif

P3 866, V3, SB Audigy2
P2 400, TNT, V2, SB Audigy2 ZS
P233 MMX, Mystique220, V1, AWE64
P166, S3 Virge, SB32, PicoGus
486DX4 100, CLGD5424, SB32
Prolinea 4/50, ET4000, SB16
SC386SX 25, TVGA8900D, Audician32
286 10, ATI VGA, Forte16
PS2 30/286, SBP

Reply 7 of 8, by NeoG_

User metadata
Rank Member
Rank
Member
Linoleum wrote on 2026-01-28, 02:47:
You mean pins 12 and 15? https://fc09.deviantart.net/fs70/f/2014/243/8/e/computer_midi_game_port_by_mad_king_corduroy-d7xfbct.gi […]
Show full quote

You mean pins 12 and 15?
computer_midi_game_port_by_mad_king_corduroy-d7xfbct.gif

Yes, apologies it was a typo

98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer

Reply 8 of 8, by Linoleum

User metadata
Rank Member
Rank
Member
maxtherabbit wrote on 2026-01-28, 01:11:

Perhaps the 5V supply at the joystick port is insufficient to drive the transistors in the gamepad and the optoisolators in the midi adapter at the same time?

Somehow, gamepads are making the big difference, so first checked there. I noticed a huge difference between Classic Gravis Gamepads and the other between pins 5 (ground) and 8 (5v). I measured a 12k resistance on the Classic Gravis Gamepad and between 1k-4k for the other gamepads.

P3 866, V3, SB Audigy2
P2 400, TNT, V2, SB Audigy2 ZS
P233 MMX, Mystique220, V1, AWE64
P166, S3 Virge, SB32, PicoGus
486DX4 100, CLGD5424, SB32
Prolinea 4/50, ET4000, SB16
SC386SX 25, TVGA8900D, Audician32
286 10, ATI VGA, Forte16
PS2 30/286, SBP