home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!news!benton.prepress.com!crash!malloy
- From: malloy@crash.cts.com (Sean Malloy)
- Newsgroups: comp.sys.ibm.pc.games
- Subject: Re: Roland Scc-1
- Message-ID: <1992Aug30.195945.23559@crash>
- Date: 31 Aug 92 02:59:45 GMT
- References: <1992Aug28.034339.1500@midway.uchicago.edu> <1992Aug28.034812.1797@midway.uchicago.edu> <EBU.92Aug28101006@vipunen.hut.fi>
- Organization: CTS Network Services (crash, ctsnet), El Cajon, CA
- Lines: 37
-
- In article <EBU.92Aug28101006@vipunen.hut.fi> ebu@vipunen.hut.fi (Erik Bunn) writes:
- >I'll second this as another proud owner of the card.
- >It seems to me that not much added effort is required to support the
- >SCC-1, if MT32 or LAPC support is made anyway. The only difference
- >would be in remapping the sound effects.
- >
- >Does anyone here know something about the format of sound drivers? It
- >seems to me that this remapping bitty could even be done by yourself
- >with relative ease - grab an existing MT32 driver and shake it up a
- >bit to give the correct mappings. Or is it more complicated than that?
-
- It's a great deal more complicated than that. Almost every MT-32 sound
- driver for games doesn't actually _use_ the MT-32's sounds, except for
- music; the drivers actually upload sound patches to the MT-32, replacing
- voices in the sound module. The SC-55 and SCC-1 emulate the MT-32's
- _voices_; their sound patch format is _completely_ different (aside from
- their both being loaded through MIDI SysEx commands). This is why, when you
- try to play, say, Wing Commander II configured to use an MT-32 for sound
- effects when you actually have an SCC-1, you get lots of different musical
- instruments for sound effects, rather than explosions, whooshes, and zaps --
- the SCC-1 _ignores_ all of the commands that load the special effects
- sounds into a _real_ MT-32, and you get the voices that normally occupy
- the output channels.
-
- And until the game companies put together a driver specific to the SCC-1,
- that's what you're going to get. Now, the difference isn't that much -- the
- header on the SysEx command is different, and the actual _patches_ are
- completely different -- but the basic driver _code_ can be lifted wholesale
- from the MT-32 driver. Personally, I'm surprised that we haven't seen a
- driver for the SCC-1 before now.
-
- --
- Random sig #21:
- Sean Malloy Navy Personnel R&D Center |
- San Diego, CA 92152-6800 | CUTE KILLS
- malloy@nprdc.navy.mil < different |
- crash!malloy@nosc.navy.mil < systems |
-