downloading sysex data

[dnewhous]

I'm trying to download the sysex file for Space Quest IV to my CM-32L.  I would really like to use Ginosoft's LA-syth ed/lib to do this since it can read the Windows MIDI mapper (otherwise I will have to use an icky DOS utility from within DOSbox).  Anyway, it didn't have any effect.  Does anyone know the default Device ID and Model ID for a CM-32L?  This information is not in the manual.  It just gives a range of valid values.

[Laust]

Device ID and Model ID are the same as for the MT-32. You don't need to worry about those since they're already part fo the SysEx, however.

Can you see any activity on the CM-32L's activity LED when you send the SysEx file? If not, then the problem is the connection. Check that the MIDI mapper is using your MIDI port as output.

There's a SysEx transfer utility for Windows called WSysEx. It's not pretty, but it gets the job done. I'm fairly certain it's available from Tom's "MT-32 Resource Center" (in the same zip as the "dump" utility for DOS). You can also find it here:

http://www.harmony-central.com/Software/Windows/wsysex.html

In general, anything capable of sending SysEx will do (even Media Player - although it would need to be embedded in a MIDI file of course). The CM-32L isn't picky or prone to buffer overflows like the MT-32 so you don't have to choose a program that will send SysEx messages with pauses to slow down the transfer.

[Kaminari]

I was looking for a WSysEx replacement (its Windows 3.1 GUI was driving me nuts), and found those neat alternatives. Most people must know them by now, but perhaps Tom could link them on his MT-32 Utilities page for everyone's convenience:

MIDI-OX (Windows 95/98/ME/NT/2K/XP)
SysEx Universal (MacOS 7.x to 9.x)
SysEx Librarian (MacOS X)

[Tom]

Thanks, Kaminari!  I used to use MidiOx a lot back in the old DOS days; it was always very dependable for SysEx work.  Since most sequencers these days have at least some limited SysEx editing capabilities, I've forgotten all about MidiOx.  I'll post v7 on my Utilities page.

[Fancia]

It might also be helpful to put up a note for Linux (and other *nix users? I don't know if it transfers to other OSs) that there's no need for extra software, and to just "cat file.syx >/dev/midi00" or whatever the raw MIDI device used to be. It took me awhile to find that out myself, so it might be helpful for other people trying to figure it out in Linux, too.

[Tom]

I will, but you have to tell me what "cat file.syx >/dev/midi00" means.   :smt100

[Fancia]

"cat" is a command that concatenates data, or copies the contents of a file. > /dev/midi00 means that it should send it to the raw MIDI port. (On my computer, the raw MIDI port is /dev/midi00. It might be a different one on someone else's, depending on how it's set up.) So "cat file.syx >/dev/midi00" sends the contents of file.syx to whatever's connected to the MIDI port.

[Zemus]

And Linux people say Linux is sooo great and easy to use...

[Fancia]

And Linux people say Linux is sooo great and easy to use...

:b Well, this *is* commandline junk. Windows is just as bad when you do something on the commandline instead of in the GUI, neh? Back to the DOS days, whee!

[apeman]

"cat" is a command that concatenates data, or copies the contents of a file.

Basically, the equivalent to "type" in DOS.

[apeman]

MIDI-OX (Windows 95/98/ME/NT/2K/XP)
SysEx Universal (MacOS 7.x to 9.x)
SysEx Librarian (MacOS X)

Can I also recommend the following program:

SendSX

It's perfect for sending and receiving SysEx data under Windows. I emailed the author with a little suggestion, which he implemented right away! Basically all you have to do is double-click on a SYX file and it will be sent to your MIDI device if you wish. Very convenient, especially for those Sierra game MIDI files with their own SysEx patches.

Cheers, Mike

[Fancia]

"cat" is a command that concatenates data, or copies the contents of a file.

Basically, the equivalent to "type" in DOS.

Pretty much, except that you can't do some of the weird things with "type" that you can with "cat." ;3

[Kaminari]

Apeman, thanks for the suggestion about SendSX. However, I can't seem to be able to make it run the way you describe (double-click on *.syx). If I assign *.syx files to SendSX, the best it does is simply to launch itself without even loading the patch, let alone transmitting it automatically. I didn't find any relevant option in the settings. I could use some help

[apeman]

Apeman, thanks for the suggestion about SendSX. However, I can't seem to be able to make it run the way you describe (double-click on *.syx). If I assign *.syx files to SendSX, the best it does is simply to launch itself without even loading the patch, let alone transmitting it automatically. I didn't find any relevant option in the settings. I could use some help

First of all, what OS are you using?
Also, it just occurred to me that maybe, the author didn't put the updated version up on his homepage.... seems unlikely though, doesn't it. Well, anyway,
here is the version he emailed me, back in June. Do you have any more luck with it?

Oh, and my turn to ask a favour - who's the chick in your avatar?

Mike

[Kaminari]

Thanks Mike, it did the trick. The version available on Florian's site is 1.21.52 while your build is 1.21.53. (I'm using Win2K.)

Why, the lady is the 'professional escort' hanging at Ho's bar in Heart of China ;o)

[apeman]

Ah, Heart of China, of course! I thought she looked familiar

Anyway, glad to hear you got SendSX working in the end.

Cheers, Mike