GiSWiG wrote:I got a Y-Cable just for that purpose but it does not work. According to some wiring diagrams, I don't thing the MIDI pins are p […]
Show full quote
95DosBox wrote:So you're using the SB AWE64 for Sound Effects and the Dreamblaster mounted on the AWE64 for MIDI is that right?
If you wanted to use they joystick and have midi there was a Y cable that plugged into the game port so you could hook the joystick and the MIDI output simultaneously. I never tried this back in the day since I didn't have a MT-32 at the time so I can't comment if this actually worked giving you joystick support, MIDI support to like a MT-32 and SB AWE64 playing your digitized effects. But I would assume if this all worked this would be how it was done back in the day to get the best sound effects, MIDI, and joystick gaming. Let me know if this works for you.
I got a Y-Cable just for that purpose but it does not work. According to some wiring diagrams, I don't thing the MIDI pins are present on either port.
95DosBox wrote:How does this DreamBlaster Midi sound vs MT-32?
Well specifically it is the S2 that I have. I don't have a MT-32 or any other external MIDI module. The only way I can get MT-32 music is via MUNT which doesn't work in Win9x so that restricts you to DOSBox under WinXP or later (works under Win7 and Win10). At least for King's Quest 5, its the only game that almost requires it to sound the way it should. For example, bird chirps sound as they should using MUNT as they use MIDI/MT-32. They sound like beeps under Sound Blaster anything and weird horns under General MIDI. Interesting how General MIDI works ok for everything else. The Dreamblaster S2 cannot load sound fonts but the X2 can. PhilsComputerLab on YouTube has a long video that covers it with about an hour of sound samples and also compares the S1 to an MT-32 and a Yamaha.
Hmm, I thought the purpose of that Gameport Y connector was to keep the joystick working and also let you adapt the Gameport to MIDI output cable to it to the MT-32. Because originally if you needed to use the game port and lose MIDI to the MT-32 that would blow. But I supposed you could install another Sound card and hooked up the MIDI to that game port and just made sure the IRQ and addresses didn't conflict between the two sound cards. You'd need at least two ISA slots to try this test out.
I found a video from PCL which shows the Gameport to MIDI and gameport break out cable and his explanation seems to also confirm it should work? You could then use a Gameport splitter on the extended game port cable to get two joysticks working and the MIDI In/Out should still work with this breakout cable.
At 1min 2 seconds start on this video you can see the types of cables.
https://www.youtube.com/watch?v=kXb3gNj--yo
I know that in XP the AWE64 worked for connecting my to the MT-32 real hardware using the Gameport in DOSBOX. But how necessary is needing that joystick? If you can still use the AWE64 GOLD and MT-32 MIDI output the keyboard wasn't a bad input control device for gaming. Maybe you would need it for X-wing or Wing Commander but not for most of the old school Sierra Quest type games.
I was always used to the original 8-bit Sound Blaster and most games I had not tried it with the AWE64 SB since I got that many years later after I had already beaten the games. But when I did test the MT-32 with those older games it was almost like playing a new game with the same graphics but it certainly elevated the experience. Some of the much older games before I had a Sound Blaster like King's Quest 3 had only the internal PC speaker beeping which was pathetic. Other computer versions of KQ3 were superior like the Tandy. One day when I get a chance I will a review of some of these older games showing how the audio and video compared on each computer platform.
As for your thoughts which of the MIDI options between the Yamaha, S1, and MT-32 did sound the best to you and in what ranking order?