Hello Kayeisha,
Kayeisha wrote:I tried to do what you suggested however when I got to the General settings the console disappeared from the screen so I continued with General and Advanced preferences and Diagnostics log however I could not click on the Great div. pistons as requested because as mentioned the screen was blank except for a drop down box box saying that diagnostic was running and not to leave it running.as it would affect the performance so I closed it..During this time the screen did not display the console.
Yes -- it's normal and expected that the virtual console will disappear temporarily whilst one of the preference screens is open (when audio/MIDI isn't running). You need to OK the preference screen, and then simply acknowledge the warning about poor performance due to MIDI logging, and then the virtual console screen will appear again so that you can try the auto-detection.
Here are screenshots showing the exact steps to do:
- Exit MIDI-OX if it's running.
- Load the Paramount 341 organ, if it isn't already loaded and select its "
Great/Solo Tabs" virtual console display page.
- Select "
General settings | General preferences" from the main menu:
- Click its "
Advanced preferences" tab, and make sure that the "
Diagnostics: log all MIDI messages received and sent" option is ticked:
- Now click the screen's OK button:
- After a few moments the following performance warning will appear. Simply acknowledge it, by clicking the "
Keep logging MIDI" button:
- Right-click on one of the numbered Great divisional virtual pistons and select the "
Auto-detect MIDI ..." menu option. (My screenshot instead shows a different piston, but the process is the same):
- An auto-detection screen similar to the following should appear. Without touching anything else (so that we can tell apart the relevant messages that get logged), press, then release, your MIDI piston.
- Without touching anything else, and assuming that the 'Done' button doesn't become enabled, click the 'Cancel' button:
- Still without touching anything else, use "
Help | Create a diagnostic file ..." from the main menu:
- [You can now turn MIDI logging off again, e.g. via the "
General settings | General preferences | Advanced preferences | Diagnostics: log all MIDI messages received and sent" option.]
- Email the resulting file to Francois at
support [at] hauptwerk.com with a note mentioning this forum topic so that he knows what it's referring to. [Usually submitting a support ticket would be needed, but MDA's website is currently being
worked upon and that part doesn't seem to be working at the moment.]
The diagnostic file should then allow him to see what MIDI messages your MIDI console sent when you tried to auto-detect the MIDI piston, and thus hopefully why Hauptwerk was unable to auto-detect it.
Kayeisha wrote:Another problem recently encountered is that some tabs will not operate by touch but ok with the mouse.
So I went through the touch screen options ,cleaned screen, calibrated etc but diagnostic said fault although when I run the touch screen diagnostic in windows it says all is ok
That would be a problem somewhere in the touch-screen hardware or (more likely) its driver or calibration. I can't help you with that, I'm afraid, but if you mention its make and model then perhaps some other user of that make/model on this forum might have some tips. Failing that, you could try contacting its maker for support, or searching the Internet for similar issues with the make/model.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
Sun Apr 16, 2023 9:28 pm