Thanks, Tom.
From your description, I suspect that currently your Johannus isn't actually sending distinct, constant MIDI messages from its pistons, and is probably instead sending changes in the states of the Johannus' own stops resulting from pressing the Johannus combination pistons. I.e. probably it's sending its internal combination system's stop state changes, not piston messages directly. It might also be (re-)sending the positions of its expression pedals as you press its pistons.
To be usable reliably with Hauptwerk you really need it to be sending distinct, constant MIDI messages directly from its pistons themselves.
I managed to find a PDF copy of the manual for the Johannus Opus 30 on the Internet, and it says that it has two MIDI OUT ports: "MIDI MOD" and "MIDI SEQ". The MIDI implementation chart in the manual doesn't mention anything about its pistons sending MIDI directly:
However, I think I recall hearing from another Johannus use that some Johannus models do send MIDI directly from their pistons (maybe MIDI sys-ex messages) via the MIDI SEQ port.
I'd suggest:
- In Hauptwerk, on the "
General settings | General preferences" screen, make sure that the "
MIDI hardware/console type" is set to "
Unmodified MIDI digital/electronic organ: Johannus".
- Make sure that the computer's MIDI IN port is connected to the Johannus' MIDI SEQ port (not MIDI MOD).
- For good measure, also make sure that its divisional "MIDI" stop switches are all off (although I think they might not be relevant via the MIDI SEQ port anyway).
- (After resetting MIDI settings in Hauptwerk again), see whether that allows its pistons now to be auto-detected reliably. If not:
- Turn on a few of the Joahnnus' own stops (so that its registration is not initially blank).
- In Hauptwerk, temporarily turn on the "
Diagnostics: log all MIDI messages received and sent" option on the "
General settings | General preferences | Advanced ..." screen tab and OK the screen (and OK the warning about performance).
- Without touching anything (in Hauptwerk, and on your Johannus), wait 30 seconds or so, so that the relevant MIDI messages can be identified by their timestamps.
- Still without touching anything else (so as to avoid other actions being logged to confuse the issue), press the Johannus piston Swell piston 1, then wait about 10 seconds, then press it again, the wait 10 seconds, then press the Johannus piston Swell piston 2, wait 10 seconds, press it again, and repeat for each of its other divisional and general combination pistons in turn [leaving about 10 seconds between each, and avoiding touching anything else].
- Use "
Help | Create a diagnostic file" and save it somewhere for reference, in case you need us to look at it.
- Use "
Help | View activity log", and have a look at the MIDI messages that Hauptwerk received from each of those piston presses.
If it's sending MIDI in a useful format, you should see just one MIDI message being sent as a result of any given piston press (e.g. a single MIDI sys-ex message), and that MIDI message should always be the same when that particular piston is pressed, regardless of the states of the Johannus stops, and the MIDI message from any given piston should be distinct from that from any other piston.
Is that the case? [If so and its pistons are sending control-change messages then you would fall foul of the known bug in v7.0.0, but I've never heard of a digital organ console that sends MIDI control changes from its pistons, so I think that's very unlikely to be applicable.]
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.