Thanks, Steve.
sclg wrote:The 'Set' button on my (Renatus) console sends a code when pushed and a code when released so I've always set it up the way I described earlier, programming the default input for 'push' and input 2 for 'release'. It's not possible to set it the conventional way. If I do a normal autodetect on it, when I press the piston in, the 'Done' button is highlighted but when I release the piston, the dialogue box returns to the 'Cancel' button being highlighted.
If Hauptwerk can't auto-detect both the 'on' and 'off' events in one go then I think your MIDI setter piston is probably sending 'asymmetric' MIDI message from the two events (e.g. on different MIDI channels, or with different MIDI note numbers).
By auto-detecting it in the way that you're doing effectively you would be toggling the state of the virtual setter as you pressed the MIDI piston in, and then toggling its state again as you released it. If something else had toggled the state of the virtual setter in-between (e.g. some logic in an ODF, or by having the "
General settings | General preferences | Main 2: Cancel setter ... automatically when capturing to a combination" option ticked) then it could end up in an unintended state.
Another possibility is that the console might be sending some additional, unexpected MIDI messages (e.g. its MIDI stop states from its internal combination system) as you operate its MIDI pistons (its combination pistons and/or its setter piston), causing some unintended virtual control(s) to be triggered. Make sure you don't have both its MIDI stops and its MIDI pistons auto-detected to Hauptwerk, otherwise the two combination systems will inevitably 'fight over' the states of the stops (see the "
Playing Hauptwerk live from a digital organ" section in the main Hauptwerk user guide -- pages 261-262 in the current v7.0 version -- for more details). E.g. maybe some setting or stored combination in your Renatus has changed since you previously had it working.
If you want to see whether you can get its MIDI setter piston working, you could experiment with using St. Anne's in that 'spare' (all-default-settings) Hauptwerk configuration, with the "
General settings | General preferences | Advanced ...: Diagnostics: log all MIDI messages" option turned on. After each piston press you could then see exactly what MIDI messages had been received from the console, and what virtual controls they had triggered, via "
Help | View activity log".
Alternatively, you could use MIDI-OX (when Hauptwerk isn't running), although of course that wouldn't show what MIDI messages had been sent from Hauptwerk, or what virtual controls incoming MIDI messages had triggered.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.