Sat Aug 01, 2020 7:58 am
Thanks everyone. I've done quite a lot of experimenting; I'll begin with something that may be of over-riding importance. With Neil Jensen's 3/35 loaded, I tried using my right hand on the trackball (I can't get on with mice) to operate the Sustain or Sostenuto switches, whilst playing notes with my left hand. I couldn't get any of the switches to do anything at all! I tried Great Sustain, Great Sostenuto, Solo Sustain, Solo Sostenuto, Piano Sustain.
I have the Paramount 450 on the same computer, so I loaded that, then operated the Sostenuto switch with the trackball. The switch is quite hard to find - it's on the Console view page, between the swell pedals for the Solo and Percussion chambers. Anyway that did exactly what I expected. Any notes that I was holding when I operated the switch stayedon; notes I played subsequently did not, which is what a Sostenuto pedal is expected to do. But when I manually set up the foot switch as I had for Neil Jensen's organ, I again couldn't get Hauptwerk to respond.
So part 2 of this message explains what I'd done earlier this morning; I'll just emphasise first that I always have the "Audio, MIDI and Performance" panel open so that I can check that a message is arriving on the expected channel.
===============================
rayjcar's first suggestion was:
"There are a couple of approaches you can take. You can right click on the virtual sustain switch, select manual adjustment, and confirm that the midi input channel corresponds to what you're seeing in Midi-Ox. Then scroll down the input settings, and select Midi Stop or Hold Piston - CC on/off. Ed is right. Hauptwerk is not looking for CC number 64 as the type of message."
That enabled me to turn the "Great Sustain" switch on and off; but notes played on a Great stop did not sustain. I tried an 8ft Tibia and the Piano.
Ray's second suggestion was:
"If that doesn't work, use the Midi Expression configuration software and change the output type from CC to note on/note off, and try auto-detecting again."
I used the Midi Expression configuration software and changed the output to MIDI note G8 (the highest note available); Channel 5, Velocity 127. MIDI Ox confirmed that is what's being output by the switch, but Hauptwerk wouldn't auto-detect it. A message was definitely being received by Hauptwerk as a light flashed on the "Audio MIDI and Performance" panel.
I used the Midi Expression software to change the note to Middle C, and that duly played a note on Channel 5.
I then followed Martin's suggestion, which produced masses of data. The final lines appear to be the most relevant - they are as follows:
2020-08-01-12-23-37: INF:2550 Diag: IN: MIDI note on: port: 828mk3 Hybrid #1, channel (1-16): 05, note (0-127): 127, velocity (0-127): 127. (Raw hex bytes: 94 7F 7F.)
2020-08-01-12-23-37: INF:2646 Diag: auto-detection: valid event received. Valid events so far: 0, spurious events so far: 0.
2020-08-01-12-23-37: INF:2644 Diag: auto-detection: event list now valid. Valid events so far: 1, spurious events so far: 0.
2020-08-01-12-23-37: INF:2550 Diag: IN: MIDI note on: port: Hauptwerk VST Link, channel (1-16): 05, note (0-127): 127, velocity (0-127): 127. (Raw hex bytes: 94 7F 7F.)
2020-08-01-12-23-37: INF:2642 Diag: auto-detection: conflicting event received. Reason code: 2716. Starting detection again.
2020-08-01-12-23-37: INF:2647 Diag: auto-detection: event being ignored. Valid events so far: 0, spurious events so far: 0. Reason code: 2717.
2020-08-01-12-23-38: INF:2551 Diag: IN: MIDI note off: port: 828mk3 Hybrid #1, channel (1-16): 05, note (0-127): 127, velocity (0-127): 064. (Raw hex bytes: 84 7F 40.)
2020-08-01-12-23-38: INF:2551 Diag: IN: MIDI note off: port: Hauptwerk VST Link, channel (1-16): 05, note (0-127): 127, velocity (0-127): 064. (Raw hex bytes: 84 7F 40.)
2020-08-01-12-23-38: INF:2646 Diag: auto-detection: valid event received. Valid events so far: 0, spurious events so far: 0.
2020-08-01-12-23-38: INF:2644 Diag: auto-detection: event list now valid. Valid events so far: 1, spurious events so far: 0.
2020-08-01-12-23-38: INF:2642 Diag: auto-detection: conflicting event received. Reason code: 2775. Starting detection again.
2020-08-01-12-23-38: INF:2647 Diag: auto-detection: event being ignored. Valid events so far: 0, spurious events so far: 0. Reason code: 2776.
2020-08-01-12-23-40: INF:2641 Diag: auto-detection: finished for SwitchInputOutput '282: TOGGLE_Great Sustain' (ID: 2423). Valid events: 0, spurious events: 0.
I don't fully understand all this, but I'm sure somebody here will. It seems that I can either activate the switch in the sample set, but it doesn't do anything; or I can send MIDI note on/off data, which Hauptwerk doesn't recognise.
My final attempt (after the above) was to change the MIDI note channel from 5 to 16, in case Hauptwerk was not happy with note G8 arriving from a "Non-keyboard" input. That still produced a note on Channel 5; I realised that was because my MIDI processing box is set to re-channelise notes on that input. So I set up an extra input to just allow through top G on Channel 16. Despite my setting up Hauptwerk manually to receive G8 on Channel 16 for "TOGGLE: Great Sustain", that switch still doesn't operate.
Thanks . . .