Thanks for the explanation. That makes a whole lot more sense. :-)
--Adam
> -----Original Message-----
> From: djbrow54 [mailto:davebr@...]
> Sent: Sunday, October 08, 2006 10:23 AM
> To: motm@yahoogroups.com
> Subject: [motm] Re: MOTM-650 V1.3 RC1 bugs reported
>
> You are correct and this 'error' should be ignored. It was
> my test software to try and get MIDI notes in the various
> ranges. I had written some software to transpose down two
> octaves and my keyboard wrapped around to notes -1, -2 -3, etc.
>
> Of course these should have been interpretted as real time
> single byte messages but the problem is that the -650 whould
> then use the following data as the note number and velocity,
> but of course it was just velocity so now the MIDI sequence
> is all screwed up. This IS NOT an issue with the -650. It
> was an issue with my test code.
>
> On the good side, I found the -650 performance flawless with
> MIDI notes in the range of 0 - 12 other than the noted unison
> issue with the sustain pedal.
>
> It might be interesting sometime to throw a bunch of
> real-time messages at it and see how it performs.
>
> Sorry for the confusion.
>
> Dave
>
> --- In motm@yahoogroups.com, "Adam Schabtach" <adam@...> wrote:
> >
> >
> > > b) sending "illegal" MIDI notes (outside the defined 127 note
> > > range) to the MOTM-650. Apparently, some software
> programs do this.
> >
> > At the risk of trying to troubleshoot a system I'm completely
> > unfamiliar with, I'm not sure that that's a correct diagnosis. The
> > only way a MIDI note number could be outside of the range
> [0, 127] is
> > if the high bit of its byte was set. The MIDI spec says that if the
> > high bit of a byte--any byte--is set, then it's a Status
> byte, not a
> > data byte. [See pages 4-5 of the MIDI spec] So in other
> words, could
> > it be that "some software programs" are sending Status
> bytes that the
> > 650 isn't expecting, rather than "'illegal' MIDI notes"?
> >
> > --Adam
> >
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
>
>