Similar situation to Eric (first post) except working thru a friend who has a successful Hauptwerk setup of his own. Same deal, a MIDI interface connected to a Rodgers 1990ish 2M. Could not get auto-detect to work to ID the manuals. After hitting the lowest and highest notes, the DONE box started blinking (randomly.) MIDI=Ox showed Active Sensing present and some other garbage types. Doing nothing else except changing the MIDI interface to a MIDIsport 2 X 2, everything worked as expected.
Observation - bad MIDI interface, right? I got curious and had this friend bring along the so called bad interface. Connected it to my (MIDIfyed) Rodgers 340, Everything worked fine. The only difference I can imagine is that my instrument doesn't send Active Sensing. So we schlept all our needed stuff and went to his church (where he wanted to demo Hauptwerk) Same problem as before (with the original MIDI interface). Did the auto-detect bit, DONE started blinking (randomly). OK with the MIDIsport 2 X 2. Only "added feature" near as I can tell, is/was the Active Sensing
Same results using my (known good) HP laptop running Win 7 Ultimate, 64 bit.
Bottom line, trash the so called
bad MIDI interface. He's happy and I guess I am too. Slight curious tickle, tho.knowing Hauptwerk ignores Active Sensing.
Would this be a fair guess that the Active Sensing overwhelmed the (bad) box which might have insufficient buffering?
And yes, we tried all the obvious stuff like cables, etc
I Googled around and found this tidbit. Not sure it is relevant.
Filter to block all active sensing events. Active sensing
messages are optional MIDI messages and intended to
be sent repeatedly to tell a receiver that a connection is
alive, however they can clutter up the MIDI channel or be
inadvertently recorded when dumping raw MIDI data to disk.
http://gareus.org/oss/lv2/midifilter#noactivesensingRgds,
Ed