|
From: Mark K. <mar...@gm...> - 2005-01-01 19:18:34
|
On Sat, 1 Jan 2005 11:10:14 -0800, Mark Knecht <mar...@gm...> wrote:
>
> I wonder if this could be something like the 'malformed MIDI' issue
> that was reported by Garett yesterday? I'll see if amidirecord can
> capture the incoming MIDI that causes the crash.
>
> - Mark
>
And the winner is....... (drum roll) Control Change or Program Change?
[mark@Godzilla mark]$ arecordmidi --port 64:0 --dump
Chick-bass-midi.mid Waiting for data. Press Ctrl+C to end
_______Tick Event_________________ Ch _Data__
53411 Control change 1 7 96
53411 Program change 1 32
53591 Note on 1 50 76
53855 Control change 1 64 127
53981 Note on 1 50 0
54031 Control change 1 64 0
54037 Note on 1 57 70
54174 Control change 1 64 127
54392 Control change 1 64 0
54408 Note on 1 64 86
54410 Note on 1 57 0
54704 Control change 1 64 127
54816 Note on 1 64 0
54950 Note on 1 57 63
Pro Tools does not seem to have a way to not send these values. It
filters on the input side by not on the transmit side. I don't know
how to filter this on the LS machine. Since Garett reported the
malformed MIDI messages issue WRT a MIDI filter maybe that's not the
issue at all, but rather he just received these same sort of messages
also?
This MIDI file is a commercially available file that works fine with GSt.
Cheers,
Mark
|