GUS Programmer's Digest Tue, 7 Sep 93 :07 MDT Volume 4: Issue 6 Today's Topics: GUS tracker MIDI SysEx ID# Standard Info: - Meta-info about the GUS can be found at the end of the Digest. - Before you ask a question, please READ THE FAQ. ---------------------------------------------------------------------- Date: Tue, 7 Sep 1993 12:34:57 +0930 (CST) From: Gavin Subject: Re: GUS tracker Message-ID: <930907123457.15295@hfrd.dsto.gov.au> >On a happier note, my GUS tracker is coming right along. It can more >or less load/play a 4-channel MOD file, though not all (or even many) of >the effects are done yet. It will support up to 32 channels, as well. >Any suggestions for features? Yes, since 4ch MODs cannot be stereo easily but 32 channel ones can, I think you should have features that allow for this. eg. easy duplication of 4 to 8 channels, easy change of track o/p level to allow easing stereo spacing. To do these things with Ultratracker is quite difficult. There are a lot of good MODs out there that could sound better with more channels. And a track delay function might be good too. ------------------------------ Date: Mon, 6 Sep 93 2:31:50 CDT From: chuth@lonestar.utsa.edu (Cornel H. Huth) Subject: MIDI SysEx ID# Message-ID: <9309060731.AA26556@lonestar.utsa.edu> > what representation is this? octal? so it's 0-2 ? or is it 2? (that is used > by Big Briar). And has it been assigned or just used by Gravis? And it still > doesn't answer my question, how can one get a midi id... Vell, it von't be oktal. There are two ways a SysEx ID is done. The first uses a single ID byte, 01 to 7F? The alternate method is that, if the first ID byte is a 00 (rather than 01-7F) then, the SysEx ID is contained in the following word (0000 to 7F7F -- I doubt 0000 is used, though). So, what would that make Gravis's? 00 for the extended and 0002 for the MIDI ID. It's hex. I can't find where this is documented, but I know this is also valid for sequencer-specific meta events. Matter of fact, this S-S metas is what I base the SysEx ID on. Take it at that. As to how to get an assigned number, ask the MIDI committee. And that 00 00 02 is standard MIDI form (00 0200 Intel). Doesn't Gravis know for sure? I'm still trying to get an answer to what port base_port+15 does, since it's not documented (not that I know of) but is used in the SDK201 (init.c). > As for ultramid, the only way i got it to issue a patch change to anything > else than patch 0 and that it plays the new instrument is to send the F8 I use my own MIDI parser code so what Ultramid does/doesn't I really don't know anything about. What you say sounds like a huge problem, but like I said, I know zilch about Ultramid. > avoid that. Also, if i send this realtime message, there will be a divide by > zero error (?!) after a few patch changes...is there a way to avoid using F8? div/0?! No idea. Doesn't Gravis support Ultramid? If not, do they provide the source (nope, I don't think so)? ------------------------------ End of GUS Programmer's Digest V4 #6 ************************************ To post to tomorrow's digest: To (un)subscribe or get help: To contact a human (last resort): FTP sites: archive.epas.utoronto.ca pub/pc/ultrasound wuarchive.wustl.edu systems/msdos/ultrasound Hints: - Get the FAQ from the FTP sites or the request server. - Mail to for info about other GUS related mailing lists (UNIX, OS/2, GUS-MIDI, etc.)