Thanks, Tom.
It would make no difference whether you use v4 or v7 -- there are no relevant differences between the two versions, and fundamentally the problem is that currently your Johannus isn't actually sending MIDI messages from its pistons at all, so nothing within the computer could ever respond to them. Instead the Johannus is just sending messages if/when Johannus' stops change state. E.g. if the registration stored within the Johannus' combination system for one of the Johannus pistons happens to turn a particular Johannus stop on (or off) then the Johannus will send a state-change MIDI message from that stop. So whether any MIDI message(s) at all get sent to the computer (and what the MIDI messages are) depends solely on what registration you happen to have drawn on the Johannus prior to pressing the piston, and also on what Johannus registration you happen to have drawn.
You could perhaps try contacting Johannus themselves for support to ask them whether there is any way that you could get your Opus 30 to send MIDI messages directly from its pistons (instead of its stops). E.g. perhaps there is some setting within the digital organ to enable it (but I think that's unlikely, since its user manual doesn't mention anything about that, and the user manual's MIDI implementation section doesn't list its pistons as sending MIDI messages). Or perhaps they might be able to supply and/or fit some upgrade circuit board or firmware that makes its pistons send MIDI messages. I recall that some later Johannus models do/did have the ability to send MIDI messages from their pistons, so maybe yours could be upgraded internally.
Failing that, as I mentioned, as a crude work-around, you could conceivably come up with a procedure whereby, within a particular Johannus combination memory bank, you programme exactly one Johannus stop to one Johannus piston, then exactly one different Johannus stop to the next Johannus piston, then exactly one different piston to the third Johannus piston, and so on, then, starting from an all-off Johannus registration each time, auto-detect the pistons to Hauptwerk's pistons. If you had it partly working previously (e.g. in v4) then presumably that's what your son-in-law had set up for you, and that would work equally in v7 [no relevant differences in Hauptwerk between the two versions].
However, it would never really be satisfactory, as a I mentioned, because:
a) You wouldn't be able to press any given Johannus piston more than once in a row (so it could never work as a stepper-advance piston, for example), and:
b) When pressing a Johannus piston after having pressed a different Johannus piston, the previous Johannus piston's programmed stop would turn off (indirectly triggering the Hauptwerk function/piston again that you'd auto-detected to it, given that Johannus organs send the same MIDI program change message again when any given stop turns off that they did when it turned on). That might, or might not, cause a problem depending on whether the Johannus always sends any applicable stop-off messages before it sends stop-on messages when the Johannus triggers one of its internal combinations.
c) You would need to avoid subsequently storing any other registrations to the relevant Johannus memory bank, i.e. you would need to keep that Johannus memory bank set up appropriately for use with Hauptwerk.
d) You would need to make sure that all Johannus stops were off prior to using Hauptwerk, and that the relevant Johannus combination memory bank was selected, and then avoid touching the Johannus stops whilst using Hauptwerk (otherwise you would potentially unintentionally trigger Hauptwerk functions, given that you would effectively have auto-detected its stop-on/off messages to the Hauptwerk functions/pistons.
If you do want to try setting it up in that way I'll have to leave it to you to experiment with, I'm afraid. I would recommend either:
1. (Ideal) contact Johannus to see whether they can help you to get your Opus 30 to send MIDI messages directly from its pistons (e.g. via some internal Johannus settings or firmware/hardware upgrade). Or:
2.. Conceivably some other Hauptwerk user who has a Johannus Opus will see this topic and know of some to get an Opus to send MIDI messages directly from its pistons. (However, I think it probably can't be done without a firmware/hardware upgrade, based on what the Opus' user manual says.) Or:
3. Buy a second-hand "Novation Launchpad Mk2", e.g. on eBay. They are very easy to set up and use with Hauptwerk, and we could help you with how to set it up if needed. N.B. the 'Mk2' model is no longer available from Novation, and Hauptwerk doesn't yet have full native support for its successor, so you would probably need to find a second-hand one. It's specifically the 'Mk2' version you need. Or:
4. See whether your son-in-law can help you set the Johannus up as he did before (presumably using the work-around I suggested). The caveat is that it could never be really satisfactory if set up that way, for the reasons above. Or:
5. If needed, you could perhaps consider employing Francois on a one-to-one consultancy basis ( http://www.hauptwerkconsultant.com/contact-us.html ) to help you set your Johannus using the work-around I suggested. Again the caveat is that it could never be really satisfactory if set up that way, for the reasons above.
[Edit: P.S. I see that Iain and I replied at the same time.
P.P.S. In case you need it, I found a copy of the Opus 5/10/20/30 user manual here: https://all-guidesbox.com/manual/118950 ... al-45.html .]
Thob3769 wrote:Let me give you one example of what I do not understand: on 4/09 you had me check one piston to see if only one numbered green led flashes which it did. If so, you said that my JOH is successfully sending Midi messages. Yet on 4/11 you described a procedure that said to make sure all JOH midi stops were off. That seem puzzling to me since I already knew that if the midi stop is off, no led lights would flash indicating no message had been sent. And when I looked at the diagnostic file I could tell that my 10 second intervals of pressing all thumb pistons sequentially were not all recorded. So was that because none of the midi stops were on?
A larger question is why is this problem seemingly caused by updating to Version VII? Although with Version VI there were a few registration glitches now and then, I was always able to auto-detect as desired. What do you think the explanation for this is?
It would make no difference whether you use v4 or v7 -- there are no relevant differences between the two versions, and fundamentally the problem is that currently your Johannus isn't actually sending MIDI messages from its pistons at all, so nothing within the computer could ever respond to them. Instead the Johannus is just sending messages if/when Johannus' stops change state. E.g. if the registration stored within the Johannus' combination system for one of the Johannus pistons happens to turn a particular Johannus stop on (or off) then the Johannus will send a state-change MIDI message from that stop. So whether any MIDI message(s) at all get sent to the computer (and what the MIDI messages are) depends solely on what registration you happen to have drawn on the Johannus prior to pressing the piston, and also on what Johannus registration you happen to have drawn.
You could perhaps try contacting Johannus themselves for support to ask them whether there is any way that you could get your Opus 30 to send MIDI messages directly from its pistons (instead of its stops). E.g. perhaps there is some setting within the digital organ to enable it (but I think that's unlikely, since its user manual doesn't mention anything about that, and the user manual's MIDI implementation section doesn't list its pistons as sending MIDI messages). Or perhaps they might be able to supply and/or fit some upgrade circuit board or firmware that makes its pistons send MIDI messages. I recall that some later Johannus models do/did have the ability to send MIDI messages from their pistons, so maybe yours could be upgraded internally.
Failing that, as I mentioned, as a crude work-around, you could conceivably come up with a procedure whereby, within a particular Johannus combination memory bank, you programme exactly one Johannus stop to one Johannus piston, then exactly one different Johannus stop to the next Johannus piston, then exactly one different piston to the third Johannus piston, and so on, then, starting from an all-off Johannus registration each time, auto-detect the pistons to Hauptwerk's pistons. If you had it partly working previously (e.g. in v4) then presumably that's what your son-in-law had set up for you, and that would work equally in v7 [no relevant differences in Hauptwerk between the two versions].
However, it would never really be satisfactory, as a I mentioned, because:
a) You wouldn't be able to press any given Johannus piston more than once in a row (so it could never work as a stepper-advance piston, for example), and:
b) When pressing a Johannus piston after having pressed a different Johannus piston, the previous Johannus piston's programmed stop would turn off (indirectly triggering the Hauptwerk function/piston again that you'd auto-detected to it, given that Johannus organs send the same MIDI program change message again when any given stop turns off that they did when it turned on). That might, or might not, cause a problem depending on whether the Johannus always sends any applicable stop-off messages before it sends stop-on messages when the Johannus triggers one of its internal combinations.
c) You would need to avoid subsequently storing any other registrations to the relevant Johannus memory bank, i.e. you would need to keep that Johannus memory bank set up appropriately for use with Hauptwerk.
d) You would need to make sure that all Johannus stops were off prior to using Hauptwerk, and that the relevant Johannus combination memory bank was selected, and then avoid touching the Johannus stops whilst using Hauptwerk (otherwise you would potentially unintentionally trigger Hauptwerk functions, given that you would effectively have auto-detected its stop-on/off messages to the Hauptwerk functions/pistons.
If you do want to try setting it up in that way I'll have to leave it to you to experiment with, I'm afraid. I would recommend either:
1. (Ideal) contact Johannus to see whether they can help you to get your Opus 30 to send MIDI messages directly from its pistons (e.g. via some internal Johannus settings or firmware/hardware upgrade). Or:
2.. Conceivably some other Hauptwerk user who has a Johannus Opus will see this topic and know of some to get an Opus to send MIDI messages directly from its pistons. (However, I think it probably can't be done without a firmware/hardware upgrade, based on what the Opus' user manual says.) Or:
3. Buy a second-hand "Novation Launchpad Mk2", e.g. on eBay. They are very easy to set up and use with Hauptwerk, and we could help you with how to set it up if needed. N.B. the 'Mk2' model is no longer available from Novation, and Hauptwerk doesn't yet have full native support for its successor, so you would probably need to find a second-hand one. It's specifically the 'Mk2' version you need. Or:
4. See whether your son-in-law can help you set the Johannus up as he did before (presumably using the work-around I suggested). The caveat is that it could never be really satisfactory if set up that way, for the reasons above. Or:
5. If needed, you could perhaps consider employing Francois on a one-to-one consultancy basis ( http://www.hauptwerkconsultant.com/contact-us.html ) to help you set your Johannus using the work-around I suggested. Again the caveat is that it could never be really satisfactory if set up that way, for the reasons above.
[Edit: P.S. I see that Iain and I replied at the same time.
P.P.S. In case you need it, I found a copy of the Opus 5/10/20/30 user manual here: https://all-guidesbox.com/manual/118950 ... al-45.html .]
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
Hauptwerk software designer/developer, Milan Digital Audio.