Hello AlbanyMusician,
AlbanyMusician wrote:1. Midi stop
My new Johannes Opus 350 has One midi stop for each manual. When a program code is stored in memory for that stop, it transmits to other midi instruments to turn on that particular sound in that instrument. With Hauptwerk, receiving stop commands is done via NRPN codes. Receiving piston commands is done via program codes. Thus if I press a Midi stop on my Johannes, I can touch a piston on Hauptwerk that has the same program code.
The midi stop tab on the Johannes is an on-off button. With some of my other sound devices, it can actually turn that program sound on or off. But with Hauptwerk and accessing pistons that does not work. The only way to turn off a piston is to do a cancel command. That is ok, and I understand that principle. My Johannes cancel button provides a general cancel to Hauptwerk as well.
So the real question is there a way for a program code coming from Johannes to control a stop rather than a piston? If that were the case, then the stop could be turned on and off.
Hauptwerk has full native support (including auto-detection) for the MIDI program change MIDI implementation that Johannus organs use for their stops, and also for the sys-ex implementation they use for their main pistons. Hauptwerk certainly doesn't require NRPNs for stops, or require MIDI program changes for pistons.
You need to:
- First make sure that you've read the '
Playing Hauptwerk live from a digital organ' section in the main Hauptwerk user guide (pages 179-180 in the current v4.2.1 version) that covers how to connect things and also some very important points, especially that you can interface either the MIDI stops or pistons, but not both (which would inevitably result in the Johannus' combination system 'fighting with' Hauptwerk's combination system over the states of the stops).
- Make sure that the MIDI ports connecting to/from your Johannus are ticked in the *left-hand* ('Console MIDI IN/OUT') columns on Hauptwerk's '
General settings | MIDI ports | MIDI IN ports' screen tab (*not* the 'Sequencer MIDI IN/OUT' columns, which use a special fixed MIDI NRPN implementation), and likewise on the 'MIDI OUT ports' tab.
- (If you're using Sonar at the same time as Hauptwerk then make sure that Sonar doesn't also have the MIDI ports enabled, since a MIDI port can safely be open in at most one application at a time, and sequencers such as Sonar don't natively have the functionality to integrate fully with Johannus implementations, as Hauptwerk itself can.)
- Make sure that Johannus is selected as the '
MIDI hardware/console type' on Hauptwerk's '
General settings | General preferences' screen.
- Then auto-detect the stops and pistons.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.