Reply 2560 of 2564, by stanwebber
i'm having a problem in win98se that i think i've isolated to midiplayer6. first, i use midiplayer6 extensively with midiyoke/midiox and roland/yamaha serial drivers as a central hub for all my midi interconnections as well as being my defacto vst/sf2 engine. i've never had a problem except when it comes to connecting 2 softsynths: invision cybersynth 3.0 and seer systems reality v1.55 (vsc, s-yxg50/100, munt, timidity, sw-10, wingroove, wavecube, websynth d77, fpd98 all give no issues).
seer systems reality is probably the easier of the 2 to tackle. it publishes its own entry in the windows midi mapper and also can be configured to accept input on a midi-in port. when i try to play a mid file in midiplayer6 using reality all i get is a smeared mess of gibberish for output. it doesn't matter if i connect using the windows midi mapper or via midiyoke.
here is the interesting part...if i use dosbox to connect to reality using the windows midi mapper or via midiyoke--playback is normal. additionally, i can use vdmsound for win9x and get the same normal playback i get in dosbox. when i go back to midiplayer6 it's unintelligible. so that's 2 independent midi clients that can interface successfully with reality.
midiplayer6 is very well authored. with all the use cases i throw at it i can't imagine it's doing something non-standard protocol-wise. i surmise that reality is expecting input that adheres to a non-conventional format that apparently dosbox and vdmsound are able to squeak by with. there is next to nothing to re-configure in reality...what can i try to fix this from the midiplayer6 end of things?