This is really a followup to bug #187, which were fixed so that sound (partially) worked with the Ensoniq soundscape vivo 90 soundcard. I cant get midi to work with sndconfig .29.1 and my Ensoniq Soundscape vivo 90 card. I have tried all possible settings for the midi part, but still I get an error message when starting xmidiplay or another midi program, saying that no midi module is available. To make it easier to get the midi settings right when autodetection fails I also suggest that sndconfig is enhanced so that a midi-test tune is played to test the midi settings from sndconfig, in the same way the Linus speach testes sound output.
*** Bug 1256 has been marked as a duplicate of this bug. *** This is really a followup to bug #187, which were fixed so that sound (partially) worked with the Ensoniq soundscape vivo 90 soundcard. I cant get midi to work with sndconfig .29.1 and my Ensoniq Soundscape vivo 90 card. I have tried all possible settings for the midi part, but still I get an error message when starting xmidiplay or another midi program, saying that no midi module is available. To make it easier to get the midi settings right when autodetection fails I also suggest that sndconfig is enhanced so that a midi-test tune is played to test the midi settings from sndconfig, in the same way the Linus speach testes sound output.
AFAIK, the SoundScape VIVO doesn't have a synth that's supported under Linux; there's an MPU401 port that you could concievably hook something up to, but I think that's it. As for midi testing, that's in sndconfig-0.30, available Real Soon Now. It only does it for cards that it's fairly sure have a synth, though (cards with an OPL3, Ad Lib, AWE32/64, TB Multisound Pinnacle, SoundScape (original), and GUS) ------- Email Received From "ArcadePreserv Center" <arcadepreserv> 02/25/99 12:54 ------- ------- Email Received From "ArcadePreserv Center" <arcadepreserv> 03/07/99 04:58 -------