[sdiy] Midi: "Save Tim's Hair"

[Merlin Zener]

> -----Original Message-----
> From: owner-synth-diy at dropmix.xs4all.nl
> [mailto:owner-synth-diy at dropmix.xs4all.nl]On Behalf Of Scott Gravenhorst
> Sent: Thursday, 3 July 2003 02:40
> To: synth-diy at dropmix.xs4all.nl
> Subject: RE: [sdiy] Midi: "Save Tim's Hair"
>
>
> "Jay Schwichtenberg" <jays at aracnet.com> wrote:
> >Tim,
> >
> >Typically there are two problems. Active sensing or MIDI Time Code (MTC).
> >These can be stuck in the MIDI stream inside other MIDI 'packets'. If you
> >can run two programs at a time or two machines back to back try
> and get a SW
> >MIDI monitor going. Or maybe one of your synths might have a
> MIDI monitor.
> >E! does on my DX7II.
> >
> >Jay
>
> This is precisely what I do.  I have an old slow DOS PC box that has an
> MPU-401 in it.  I wrote a fairly simple program to monitor MIDI data for
> display as while it copies bytes from input to output.  I'll be more than
> happy to give you the source for it, but it's written for DOS, M$
> QuickC ver
> 2.5, _not_ Windoze.
>
> This technique has always revealed what is going on.  It will introduce a
> small delay, but once the problem is found and corrected, this piece is
> easily removed from the MIDI stream.  An invaluable tool, IMHO.
>

Or you could go to http://xgmidi.wtal.de/software.html and download
a tool I found there called MIDIOX.
It will monitor and display the input and/or the output, and you can
even save to a log file so you can look byte by byte and see exactly
what is going on.

That program does a bunch of other stuff like filtering etc too, you
may find it useful - I know I have :)

--
Merlin Zener
Piano, Synthesizer
Pattaya Thailand
http://www.merlinzener.com

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.495 / Virus Database: 294 - Release Date: 30/06/2003