It is currently Thu Mar 28, 2024 4:06 am


Issues with "Auto Detect in Wurlitzer 320.

Hauptwerk software technical support only. Please make sure you have read the manual, tutorials and FAQ pages before requesting support.
  • Author
  • Message
Offline

ErnestM

Member

  • Posts: 20
  • Joined: Sun Aug 17, 2014 5:45 pm
  • Location: Orefield, PA (about 45 Miles N of Philadelphia) USA

Issues with "Auto Detect in Wurlitzer 320.

PostSun Mar 27, 2022 3:35 pm

Issue: Left click virtual piston button on touch screen to "Auto Detect a physical piston. After opening "Auto Detecting MIDI Settings" window, it is discovered that the "Done" button erratically flashes on and off all by itself. Unable to set any piston selected for Auto Detect. After pressing the "Cancel" button in the window to close the "Auto Detecting MIDI Settings" window, and thereafter left clicking on the virtual General Cancel button on the touch screen, the anomaly of the piston that was attempted to be set illuminates all by itself. No matter what virtual piston is selected to set to a physical piston the problem repeats itself. The "Cancel" button is left clicked again, and by itself, the virtual piston (that was attempted to be put onto a physical piston) jumps back to illuminate the piston that was attempted to be set on a physical piston via Auto Detect. With hopes to remedy the problem, reopened up the window and clicked on the "Clear all MIDI/key trigger settings..." for the desired piston to be physically set. Repeated the entire process. Alas the problem reoccurred. There are no issues with any of the other organs installed, only the Wurlitzer 320. Suggestions? Thank you!
Offline
User avatar

mdyde

Moderator

  • Posts: 15441
  • Joined: Fri Mar 14, 2003 1:19 pm
  • Location: UK

Re: Issues with "Auto Detect in Wurlitzer 320.

PostMon Mar 28, 2022 5:56 am

Hello Ernest,

From your description I think your MIDI console must be sending a stream of spurious MIDI messages, which are preventing Hauptwerk from being able to 'hear' the relevant message(s) from your MIDI piston when you try to auto-detect it. The most common culprit is a MIDI expression pedal/encoder, e.g. due has hysteresis, or dirty potentiometer contacts, or an electrical/grounding problem, or perhaps a vibration issue through MIDI console causing the expression pedal's potentiometer to move slightly as you touch other things on the console.

Given that you also mention that other virtual combinations are getting triggered erratically, I think you have probably unknowingly auto-detected that spurious MIDI message (e.g. from the MIDI expression pedal) to one of the other virtual pistons.

I'd suggest:

- Load the sample set set.

- 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, 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), right-click on the relevant virtual piston, and try to auto-detect it to your MIDI piston.

- Still without touching anything else, and assuming that the 'Done' button still flashes as before (which indicates that spurious conflicting MIDI events are being received), click the Cancel button.

- Still without touching anything else, select "Help | View activity log" from the menu.

- Near the end of the log, look for the last "INF:2640 Diag: auto-detection: started ..." message, and look at the MIDI IN messages that were received after it. Aside from the intended MIDI messages from your MIDI piston, you'll probably see some spurious additional MIDI messages (e.g. from your MIDI expression pedal). Hence that should allow you to identify the malfunctioning MIDI control, so that you can get it resolved.

Here is an example of MIDI messages being received when auto-detecting a note-on/off MIDI piston to a virtual control (St. Anne's Swell divisional piston 1), with no spurious MIDI messages being received, i.e. an example of what you might see if everything was behaving correctly:

2022-03-28-11-47-40: INF:2640 Diag: auto-detection: started for SwitchInputOutput '060 Comb piston: Sw thumb 1' (ID: 661), screen input tab 1.

2022-03-28-11-47-43: INF:2550 Diag: IN: MIDI note on: port: Console MIDI IN 06 [=> micro lite: Port 5], channel (1-16): 01, note (0-127): 048, velocity (0-127): 066. (Raw hex bytes: 90 30 42.)

2022-03-28-11-47-43: INF:2646 Diag: auto-detection: valid event received. Valid events so far: 0, spurious events so far: 0.

2022-03-28-11-47-43: INF:2644 Diag: auto-detection: event list now valid. Valid events so far: 1, spurious events so far: 0.

2022-03-28-11-47-44: INF:2551 Diag: IN: MIDI note off: port: Console MIDI IN 06 [=> micro lite: Port 5], channel (1-16): 01, note (0-127): 048, velocity (0-127): 000. (Raw hex bytes: 80 30 00.)

2022-03-28-11-47-44: INF:2646 Diag: auto-detection: valid event received. Valid events so far: 1, spurious events so far: 0.

2022-03-28-11-47-44: INF:2644 Diag: auto-detection: event list now valid. Valid events so far: 2, spurious events so far: 0.

2022-03-28-11-47-46: INF:2641 Diag: auto-detection: finished for SwitchInputOutput '060 Comb piston: Sw thumb 1' (ID: 661). Valid events: 2, spurious events: 0.

2022-03-28-11-47-46: INF:2648 Diag: auto-detection: configured switch '060 Comb piston: Sw thumb 1' (per-organ: Y) with: event type: 'Stop or hold-piston: MIDI note-on/off', port: 'micro lite: Port 5' (engaging event type code: 1, disengaging: 2, wizard choices: toggle: N, send matching output: N, output port: '', Launchpad color code: 0).
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
Offline

ErnestM

Member

  • Posts: 20
  • Joined: Sun Aug 17, 2014 5:45 pm
  • Location: Orefield, PA (about 45 Miles N of Philadelphia) USA

Re: Issues with "Auto Detect in Wurlitzer 320.

PostMon Mar 28, 2022 6:49 am

Good Day, Martin;
Thank you for your reply. I will study your reply with hopes of a resolution. Thank you!

Ernie
Offline
User avatar

mdyde

Moderator

  • Posts: 15441
  • Joined: Fri Mar 14, 2003 1:19 pm
  • Location: UK

Re: Issues with "Auto Detect in Wurlitzer 320.

PostMon Mar 28, 2022 6:51 am

Thanks, Ernie. You're very welcome. Hope it helps.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
Offline

ErnestM

Member

  • Posts: 20
  • Joined: Sun Aug 17, 2014 5:45 pm
  • Location: Orefield, PA (about 45 Miles N of Philadelphia) USA

Re: Issues with "Auto Detect in Wurlitzer 320.

PostMon Mar 28, 2022 7:02 am

Marftin

Afterthought to your reply. If there may be issues with a "dirty potentiometer contact or an electrical/grounding problem..." as you state, why then is this anomaly only affecting the Wurlitzer? There are no MIDI performance issues with any of the other organs installed, and the expression involving both expression shoes on the Wurlitzer operates normayl without issues as well? The Wurlitzeer is the only organ with this Auto-Detect issue. Please extrapolate further to help me understand. Thanks!

Ernie:
Offline
User avatar

mdyde

Moderator

  • Posts: 15441
  • Joined: Fri Mar 14, 2003 1:19 pm
  • Location: UK

Re: Issues with "Auto Detect in Wurlitzer 320.

PostMon Mar 28, 2022 7:30 am

Hello Ernie,

If it definitely is the case that the auto-detection problem is (still) only occurring with one sample set then one possibility, for example, could be that some other virtual control is getting triggered from MIDI messages from your console, and that virtual control is configured to send MIDI messages back to your console, which is in turn causing the console to send some more MIDI messages back to Hauptwerk as you're trying to auto-detect.

However, rather than try to speculate on every possibility, if you try the test I suggested then it will probably immediately be clear what's actually happening, and what needs to be done to solve it, hence please do try that test. If needed you could post the log excerpt between (and including) the "NF:2640 Diag: auto-detection: started ..." and the "INF:2641 Diag: auto-detection: finished ..." lines to this forum topic, so that we can help interpret the results.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
Offline

ErnestM

Member

  • Posts: 20
  • Joined: Sun Aug 17, 2014 5:45 pm
  • Location: Orefield, PA (about 45 Miles N of Philadelphia) USA

Re: Issues with "Auto Detect in Wurlitzer 320.

PostMon Mar 28, 2022 9:31 am

Good Afternoon, Martin:

Thank you for you assistance. I will proceed with your suggested steps and tests and monitor the outcome.

Ernie

Return to Technical support

Who is online

Users browsing this forum: Roglu and 7 guests