MIDI lockup on 0.6.4 (Windows)

[Louis B.]

Hi,

 Ok to tidy things up. this appears not to be a PB problem but a RT midi problem on windows. So I cannot help you much more. However I have two suggestions you could try.

1) contact the author of RT midi about this problem.

2) contact the mididev mailing list available here http://groups.google.com/group/mididev/topics. They are very helpful and they could probably find some C source code that works with your hardware. This code would then need to be modified to working with RtMidi.cpp. RtMidi.cpp is not as bad as it looks as on one third or it applies to windows, (the other thirds are for the Mac and Windows).

Also Linux now runs very well on old PCs

Louis

[Mark Morgan Lloyd]

Louis B. wrote

 Ok to tidy things up. this appears not to be a PB problem but a RT midi problem on windows. So I cannot help you much more.

I agree. It's not your problem, rather it's something to do with RTMidi mis-parsing unexpected events.

In practice I'll probably just boot the laptop into '98 for this particular app- I don't like doing that since we've always focussed on NT (and derivatives). Any other solution is impractical since there quite simply isn't space for another screen in that corner of my workroom.

> Also Linux now runs very well on old PCs

Yes, I've been using it since the early 90s and now support it on the gamut from ARM to SPARC. Unfortunately about the only machine I've not got it running on is this elderly Sony Maiow.

-- MarkMLl

[Mark Morgan Lloyd]

Context: Piano Booster, or probably the underlying rtmidi library, was locking up on NT4 when it saw a sysex from a Yamaha HC-4 organ.

For completeness, I find that if Piano Booster is receiving its input from MIDI-OX via MIDI Yoke with a map file to transpose by an octave that it no longer locks up, although there might be some odd note bounces. Presumably MIDI-OX handles arbitrary sysexes more robustly than rtmidi.

-- MarkMLl