Silanda wrote:Awesome! […]
Show full quote
KainXVIII wrote:Silanda wrote:You could try what I posted here to alleviate the stuttering: Dark Seed 2 will not play cut scenes.
Missed last answer (and it helps!)
Awesome!
As to the OP's question. It might be worth messing with the MIDI Mapper settings in Windows 3.11 (Main - Control Panel - MIDI Mapper). Try making sure that the active map is mapping all 16 MIDI channels to the synth. IIRC not all channels are mapped by default. Also, you might be able to select from there whether Windows 3.11 uses the emulated OPL3 or passes it to an external MIDI device (whatever DOSBox is set up to use, which is the built in synth by default on Windows). You can certainly do that with the SB16's drivers, and as crap as the built in Windows MIDI synth is, it will sound a hell of a lot better than the emulated Soundblaster. If it had been using that it might explain why it sounded better before.
Assuming that the emulated Soundblaster was always being used, it could also just be that the General MIDI to OPL3 patch library that the SB Pro uses is worse than the one used by the SB16, but I really have no idea about that.
Thanks great suggestion. When I've played midi music on any other game on sbpro it seems exactly the same as sb16, only when in dark seed 2 through win3.11 it isn't.
I think the midi mapper is just built into windows 3.11, when I installed sb16 and sbpro, the midi mapper stays in the list. I don't think sb16 drivers affect the midi mapper driver. sbpro loads 3 extra drivers and all of those just have base address/IRQ/interrupt settings, that's all. OK I found all the settings for midi mapper now
The attachment IMG_20190107_141127_1546884758345.jpg is no longer available
The attachment IMG_20190107_141107_1546884776709.jpg is no longer available