MIDI-OX User Forum - Print Page


    
      
        MIDI-OX User Forum
        (http://www.midiox.com/cgi-bin/yabb/YaBB.pl)
      

        MIDI-OX >> MIDI-OX Beta Bugs >> MOXbeta 6.7.0.354 - strange release?
        
(Message started by: Peter L Jones on Aug 9^th, 2003, 6:44pm)

Title: MOXbeta 6.7.0.354 - strange release?
Post by Peter L Jones on Aug 9^th, 2003, 6:44pm

Hi there.

I think I've seen this reported before but couldn't find it when I searched.

Code:

TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
005C1133 10 1 90 40 39 1 E 4 Note On
005C11C8 10 1 90 40 00 1 E 4 Note Off
005C124F 10 1 90 3E 4B 1 D 4 Note On
005C12F7 10 1 90 3E 00 1 D 4 Note Off
005C139B 10 1 90 3C 2F 1 C 4 Note On
005C149F 10 1 90 3C 00 1 C 4 Note Off
Closed MIDI Input
Closed MIDI Output
Opened MIDI Input
Opened MIDI Output
0015003E 8 9 99 25 00 10 C# 2 Note Off
Closed MIDI Input
Closed MIDI Output
0015003E 8 9 99 25 00 10 C# 2 Note Off
Opened MIDI Input
Opened MIDI Output
Closed MIDI Input
Closed MIDI Output
0015003E 8 9 99 25 00 10 C# 2 Note Off
Opened MIDI Input
Opened MIDI Output

Where's that C# Note Off coming from..? From ages ago..?

This in on XP with myokent 1.71.0.019 Beta.

Other relevant facts: this was after changing config to one that didn't include my USB MIDI keyboard and turning the keyboard off - that causes the MIDI port to disappear.

(XP's USB MIDI port handling is horrid... sometimes it recognises my keyboard by name, sometimes not. Generally any running program doesn't get advised there are new/lost ports. Sometimes running programs crash when there's a change. Sigh)

Title: Re: MOXbeta 6.7.0.354 - strange release?
Post by Jamie OConnell on Aug 10^th, 2003, 2:13pm

I've seen that as well. I'm not sure what causes it (yet).