Tue May 03, 2022 6:01 am
Hello Scott,
I don't have first-hand experience with Rodgers organs, but if the organ has a MIDI SEQ port as well as a MIDI OUT, you might possibly find that that it transmits more useful data from its MIDI SEQ port, so I'd recommend trying having that one connected to the computer (instead of MIDI OUT).
Without Hauptwerk running, you could then use MIDI-OX (Windows) or Snoize MidiMonitor (macOS) to see exactly what MIDI messages the pistons are actually sending to the computer. To be usable, each piston needs to send a distinct MIDI message (e.g. a distinct MIDI program change message per piston), and the piston always needs to send the same MIDI message each time you press it (without varying according to the digital organ's internal stop states or its stored registration, for example).
If, when a piston is pressed, as well as the piston message (e.g. MIDI program change) the Rodgers is also transmitting a list of its internal stop states, then that's likely to prevent Hauptwerk's auto-detection from being able to identify the desired piston message from the stop-state messages. However, if that's the case you could potentially configure the MIDI settings for the virtual piston manually.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.