All settings in Hauptwerk Gone!

[mdyde]

Hello Jeffrey,

First of all, thanks very much for upgrading to v9, and glad to hear that updating Windows and rebooting resolved some things.

I assume that you still have the latest driver and firmware versions installed for your audio and MIDI interface(s), given that your PC was reinstalled a few days ago, but if in doubt then please check on their manufacturers' websites for the latest versions again. (For some interfaces you need to install firmware updates separately from their driver updates.)

Also, I think from your previous replies that you meant that you did actually test the PC's RAM for errors, and its hard-drive, otherwise please do check those thoroughly. (In particular, malfunctioning RAM boards can cause all manner of strange/erratic problems.)

Hauptwerk always saves all settings automatically before it exits (and whenever loading or unloading an organ). You can force it do so at any other time (to guard against a power cut or computer crash in the meantime) using "Other | File Save any unsaved settings (Hauptwerk auto-saves anyway)" from the touch menu.

Also, please check that your PC is shutting down cleanly, otherwise the operating system might not actually write changed files to the drive, thus losing changes. Also, virus scanners have very occasionally been known to corrupt settings files.

If you find that your problem with the pipes making no sound returns, please try clicking on the virtual keys on the screen, so as to try to determine whether the problem is with the MIDI connection(s) from the MIDI keyboards.

Also, when you mention losing your settings, if you right-click on the relevant controls, and select "Adjust ... manually ...", are the settings actually still there? Assuming so (and they should be), the problem is probably that your PC is dropping or changing USB connection(s) to your USB MIDI devices, thus resulting in the current/active connections that Hauptwerk has to them stopping working. Hauptwerk doesn't support 'hot-plugging' devices; it's important that you exit Hauptwerk before plugging in, or unplugging, any audio/MIDI/USB devices. Also, if any of your audio or MIDI devices are connected to a USB hub, then make sure it's a good-quality (reputable brand) hub with its own dedicated mains power supply. Insufficient power to USB hubs, or hubs that are otherwise unreliable, often cause problems with dropped MIDI connections. If possible, it is better to keep USB-MIDI and USB-audio devices connected directly to USB ports on the computer (rather than via a USB hub).

I read the manual because I cannot get my Bargraph LED's to work (the expression pedals work but no visual indicators - and the crescendo shoe works, but there is no Output screen to configure my 3 digit LED display. All choices are greyed out and I can only get 1 of the LCD screens to show the correct things (Organ, Loading and Temperament) The other two screens I cannot figure out how to set them up.

I assume you're referring to the two "Settings | MIDI settings ... | MIDI LCD panel control ..." screens. If so, the "MIDI LCD panel control (for this organ)" screen is only enabled once an organ is loaded, and the LCD line format for showing organ expression/crescendo pedals is only available on that screen (since those things are organ-specific). Also, on either of those screens you must have an entry inserted and selected in the left-hand browse list before you can configure any of its properties in the right-hand pane.

Does that answer your question? If not, which specific screen are you referring to?

Also the LCD Screen thing, curiously in the setup for these items I can only choose one device and I have three devices setup using the Midisport 8x8. the first LCD screen is setup to use the device iteself not the port out. I tried with the other two LCD screens to use the device itself instead of the assigned device Port Out. That did not work, but also identifying each device (as 1, 2 or 3) only worked on the first LCD Screen.

I'm not sure I'm clear what you're referring to. The "Settings | General: MIDI ports | MIDI OUT ports" screen shows all MIDI OUT ports that Windows reported as being present when you launched Hauptwerk. You need to have any MIDI ports ticked (enabled) on that screen before you can use them on other screens.

[jcrowley]

Thank you for replying so quickly.

For the sound settings or audio - I tested on screen keyboard and I get no pipe sound, but I can hear the blower and action. My audio interface shows this noise on the vue meter for each channel and also reacts favorably when I have a stop drawn and play on that keyboard.

I had to reboot my computer as a hard boot after shutting down correctly.

The MIDI merger is USB Power connected to computer which has 1100 Watts of power. Really nothing else uses any USB power. Everything else has a brick to power each device all pulling from different outlets since my apartment has very few outlets and 6 breakers.

[mdyde]

Thanks, Jeffrey.

For the sound settings or audio - I tested on screen keyboard and I get no pipe sound, but I can hear the blower and action. My audio interface shows this noise on the vue meter for each channel and also reacts favorably when I have a stop drawn and play on that keyboard.

I had to reboot my computer as a hard boot after shutting down correctly.

In that case, given that the audio from the pipe ranks was reaching your audio interface but not audible, I think the problem must have been something within the audio interface or its driver/control panel.

The MIDI merger is USB Power connected to computer which has 1100 Watts of power. Really nothing else uses any USB power. Everything else has a brick to power each device all pulling from different outlets since my apartment has very few outlets and 6 breakers.

If you have problems again that appear to be previously-auto-detected MIDI settings stopping working, first check via right-click "Adjust ... manually ..." whether the settings are actually still present (as they should be). If so, almost certainly the driver/hardware/Windows dropped/changed the active USB to the MIDI interface. Re-launch Hauptwerk (which will cause it to re-query the list of MIDI devices from Windows and establish new connections to them) to see whether that fixes it. If not, try fully shutting everything down and rebooting.

You also mentioned an M-Audio MIDISPORT 4x4. I think M-Audio discontinued them quite a few years ago, so it's conceivable that yours has simply developed a fault. If you have a different MIDI interface, perhaps try using that instead (exit Hauptwerk before unplugging or plugging in any devices), to see whether it works better.

If you then still need us to help with it, please try temporarily switching to working with St. Anne's organ and reproduce the problem with that (since we all have ready access to St. Anne's, and so could look at your settings for it via a diagnostic file), then use "Other | Help | Create a diagnostic file ..." and send the resulting file to Francois at support [at] hauptwerk.com mentioning this topic and describe exactly what you did and what isn't working.

[jcrowley]

Slight update ~

Yesterday (2/11/2025) I tested the only organ that I have loaded since the upgrade - the Essen TUP.

When I booted the computer up I pinged the USB ports. All seem to be working and Windows Device Manager does not report any dead or malfunctioning USB ports.

I loaded HW 9 , then opened TUP (I did not save the settings last night on purpose)

The Sound of the blower and key/shutter action is present. I had to re-set everything up again from scratch. Missing the Setter >Next and Previous, which are a Piano sostenuto pedal and two pistons for 5 devices programmed to make the stepper work.

I have also a MIDI LaunchPad Mini that used to be programmed to handle the Memory levels, English Piston System, Extra Stepper buttons such as [000], [00] and [0] - MIDI Panic. The English piston system [A,B,C etc]. the transport buttons for the recording system and all of the bonus couplers that are not unison for 4 manuals (I have a 3 manual keyboard and do not use the "Floating Division" I do it with unison off's and Unison/sub/super couplers to either of the three remaining keyboards, Regular, Scope and Scoped buttons, basically I used all 64 buttons on the device and it was working for almost 4 years. It even had indicator lights when they were "on".

Suffice it to say, I have the LaunchPad In/Out MIDI Ports defined in the settings pages. The only button that I currently have programmed is the [000]. I had it working WITH backlight in Amber on/off. Zero settings in Hauptwerk today, but the system does recognize the button during the "discovery" phase, but, no indicator light. No warning that it could not find the LaunchPad on Hauptwerk start-up.

I rehearsed for a couple of hours and when I had finished with the Prelude (which only has one setter combination used and after all of that setup - No parameters in the setter system and the General Cancel and the Set Button. The couplers (I have Classic MIDI works Lit Rocking Tabs - which BTW - used to light up when it was on) were missing parameters.

So I methodically set everything up again. I forgot to mention no pipe sound only blower. Keys on "console" screen used with mouse click and no sound for any stop. My vue meter for my Audio interface WAS active when I depressed a key with a stop on but no sound.

I went into Windows>System>Sound and clicked on the supposed ASIO USB (this has a IEEEE plug to an outlet), however, is connected to the PC with a USB cable - it always worked extremely well with HW 6 and my setup. So I clicked on the ASIO Focusrite USB "Speaker" in that window and ran the test and the sound was fine @96,000Hz and 516 buffer. I then "saved" my Hauptwerk settings manually. I closed the organ and then Hauptwerk (Lo and behold - there was another Windows Update getting installed) so I had to wait until that dog and pony show was finished.

I did extensive RAM tests and it took almost 9 hours to complete. Found Zero problems, and ran several different products besides Windows just to make sure.

The hard drives were all present and working well.

No Windows 11 errors after the update and I looked in System Error Log and Windows Error Log nothing jumps out at me.

The computer restarted - I waited about 10 minutes, then launched Hauptwerk 9, then loaded TUP organ.

Cannot see any settings for the LaunchPad in the Settings setup windows.

But, the Launch Pad programmed [000] worked as expected. Still no sound and no Keyboards setup, the on screen keyboard did work with pipe sounds. So I re-discovered the keyboards again.

Saved my "settings" manually. Closed the Organ and shut down Hauptwerk. Then I waited about 20 minutes. Re-Launched Hauptwerk and the Organ and now it was as if nothing happened, I still cannot setup any of the LaunchPad Mini with indicator lights when on, the lit rocking tabs lost their "discovered settings" and after discovery I cannot get the backlight to work on them. They used to do this with the "simple discovery" in HW 6. I did not have to make any further changes on the Output screen.

I got 1 Universal LCD screen to work correct but not all three [Organ Name, Loading %> Temperament] as device 001.

The LED bargraphs worked fine in HW 6. I have three "expression pedals" (left to right=Choir/Positiv Expression, Swell Expression, Manual IV Expression/Great Expression/Crescendo] These are on a "per organ" basis.

The odd thing is these devices are connected via MIDI Expression Black T/S 1/4" connectors, they go back to Hauptwerk and then Hauptwerk supposedly sends the data out to a MIDI Port (Channel 8, Channel 12, and Channel 10) they all go to the MIDI Merge box and go out the first port to the daughter board (MIDI Boutique) where the devices are plugged into the board with ribbon cables. They have always just worked and I could do this with a simple discovery - not a complex discovery. There are three Bar Graphs to indicate for the expression and one 3 digit 7 segment device to display the crescendo level in Percent.

Odd, when I attempt to "discover" the expression shoes/Crescendo shoe it states that the messages are coming IN to the MIDI Port of the MIDI merge box (instead of the MIDI Expression BLack Device which is connected by USB to the computer, having #11 as the type of device and all on a separate MIDI Channel and the MIDI Merge box distributed the devices clearly and without any further setup required (I also have a little program to "flash" the ROM of the daughter board to state the MIDI Channel and what type of device it is). I used the setting of #7 Main Volume for the Crescendo Shoe so that if I have 2 expression and one crescendo the data will go to the correct device and it always just worked. Not it won't work at all if I manually setup the IN and OUT tabs for the Expression shoes (and the On-screen shoes do not work either.

This setup is incorrect and I do not know how the system can mistake input? I literally have never unplugged, removed, or changed USB ports. All has stayed right where I had put them 4 years ago.

Well, short answer is after I saved the settings again, manually. The computer slept well and when rebooted and Hauptwerk was invoked with the TUP organ. All of the settings were populated as I had put them. Still no Launch Pad, but it works for now. I am going to leave this as is until I can video and record my Bach piece for the local festival. I will experiment after March 1st.

[mdyde]

Hello Jeffrey,

v9 is no different than v6 in the way that MIDI is used or configured.

Regarding your Launchpad, on the "Settings | General: MIDI ports" screen, make sure that the Launchpad's column is ticked on the "MIDI OUT ports" tab (as well on the "MIDI IN ports" tab). Provided that it's enabled for both input and input, when auto-detecting any one of its buttons Hauptwerk will prompt you to select the desired button lamp colour, and will then configure and control its lamp automatically.

Odd, when I attempt to "discover" the expression shoes/Crescendo shoe it states that the messages are coming IN to the MIDI Port of the MIDI merge box (instead of the MIDI Expression BLack Device which is connected by USB to the computer

It all sounds as though the problem is indeed simply that the computer's connections to the USB MIDI devices are dropping/changing/swapping whilst Hauptwerk is running, resulting in your existing settings no longer seeming to work because the active connections to the MIDI devices have been dropped, or have swapped themselves around. Especially given that this only started happening a few days ago, perhaps one of your USB devices has begun malfunctioning erratically, or perhaps some recent automatic Windows update, driver update, or BIOS update caused it.

Well, short answer is after I saved the settings again, manually. The computer slept well and when rebooted and Hauptwerk was invoked with the TUP organ. All of the settings were populated as I had put them. Still no Launch Pad, but it works for now. I am going to leave this as is until I can video and record my Bach piece for the local festival. I will experiment after March 1st.

When you return to looking at it (after your festival recording, etc.), please try the following:

- Reboot the computer, log in to Windows, and wait 60+ seconds for devices to have time to finish booting.

- Make sure that Hauptwerk isn't running, and that no other audio/MIDI applications are running.

- Launch Hauptwerk using the "Hauptwerk (alt config 3)" desktop shortcut (assuming that you haven't been using that one for anything important; settings are entirely independent between configurations).

- Within it, use "Other | File | Revert all Hauptwerk settings to factory defaults" (which will affect all settings for "Hauptwerk (alt config 3)", but won't affect any other configurations). Hauptwerk will exit once done.

- Re-launch Hauptwerk using the "Hauptwerk (alt config 3)" desktop shortcut.

- The General Configuration Wizard will run automatically. When prompted, select the appropriate MIDI hardware/console type, then select "Yes. Enable MIDI output ...", then click Finish.

- The MIDI Ports screen will then appear automatically. On the "MIDI IN ports" tab, tick just the devices that you use with Hauptwerk, and give them meaningful aliases (names or short descriptions) in the rows in which you ticked them. Giving them aliases is important because it will help to make sure that you can tell them apart reliably, even if Windows subsequently changes the device names (or if it switches them around, for example). Do likewise on the "MIDI OUT ports" tab. OK the screen.

- The Audio Device screen will then appear automatically. Select your audio interface's ASIO driver, and leave all other settings at their defaults (48 kHz, buffer size=1024, etc.). OK the screen.

- [Don't change any other settings. The aim of all this is to have a minimal test case.]

- Load St. Anne.s.

- Auto-detect your MIDI keyboards to the St. Anne's virtual keyboards.

- Draw some stops and verify that you can hear their sound correctly when playing from your MIDI keyboards.

- Auto-detect the first two buttons on your Launchpad to the "Trigger cued: xx0" and "Trigger cued: xx1" buttons on the touch menu's Overview tab respectively.

- Verify that pressing those Launchpad buttons causes the corresponding buttons to light up on the Overview tab, and also that the corresponding Launchpad buttons' lamps light up.

- [Don't change any other settings.]

- Use "Other | File | Create a diagnostic file ..." and save the file named "MinimalTest1" (in case we need to look at it or compare it later).

- Exit Hauptwerk.

- Re-launch Hauptwerk using the "Hauptwerk (alt config 3)" desktop shortcut.

- Load St. Anne's and draw some stops.

- See whether your MIDI keyboards still cause the St. Anne's virtual on-screen keyboards to play, and whether you still hear the corresponding pipe sound. Also see whether your first two Launchpad buttons still trigger the xx0 and xx1 buttons on the touch menu's Overview tab, and whether the Launchpad button lamps still light up properly. If not, on the "Settings | General: Preferences | Main" screen tab, turn on the "Diagnostics: log all MIDI messages received and sent" option, OK the screen, then without touching anything else (so that we can tell the relevant messages apart easily in the log) press one key on each of your MIDI keyboards, then press each of your first two Launchpad buttons, then use "Other | File | Create a diagnostic file ..." again and save the file named "MinimalTest2", then send both the MinimalTest1 and MinimalTest2 files to Francois at support [at] hauptwerk.com mentioning this topic.

- If the keyboards and xx0 and xx1 buttons and sound *did* work properly in the last step, then exit Hauptwerk, reboot the PC, and repeat the last three steps, to see whether rebooting causes them not to work. If it still works properly, keep rebooting (turning off all power) and repeating the last three steps to see whether that causes them not to work.

[jcrowley]

Today - February 13, 2025:

Launched Computer

Launch Hauptwerk probably about 20 minutes after turning the computer on (everything power is connected to the same power strip and turned on before I turn on the computer. I usually wait 5-10 minutes to turn computer on.

I forgot that a few message back the MIDI Merge device is a MIDItech MIDIface 8x8 not a MIDI sport.

Launched TUP. (It does take quite awhile to load the instrument 9 about 6 minutes or so. Actually less time than HW 6.
I noticed that the only LCD Screen that is working - has no data on it at all during the Organ load.

When I check out all of the settings - everything is empty. I did manually save the organ last night. The Audio is present for the blower only. The keyboards are not configured but the keyboard on-screen plays audio when a stop is drawn and the screen keyboard is used.

I set-up the keyboards again, had to setup the stepper triggers again.

I got the LED Bar Graphs displaying correctly (and I did nothing different with my discovery and setup other than I had to "discover" the expression shoes.

The Crescendo shoe still has a greyed out MIDI Out screen - so I cannot setup the numeric displays. I had to setup the first LCD display again, only a different MIDI out defined. I still cannot get the other two LCD screens to get text to them, but the screens are on and powered each by a power brick.

I agree with you - I think that some of my USB ports are changing around or going in and out. I have 13 USB ports on my computer.

4 in front that the iLok dongle is connected to (USB 3.0) - my dongle for the keyboard and mouse. The other two are empty.

The rest are all on the back of the PC and are all 3.0 ports including a daughter board that has 5 3.0 USB's it is a PCI internal card drawing power from the Computer power. I also have 1 USB Type "C" on the back plate of the motherboard, and two :"Powered USB" (the ones with orange sockets) but I do not use them.

Is there a good USB detective on the market where I can also get a printed report on the validity of the ports?

I will try your suggestions in March, when I will have more time.

[mdyde]

Thanks, Jeffery.

Is there a good USB detective on the market where I can also get a printed report on the validity of the ports?

I will try your suggestions in March, when I will have more time.

I don't know of any USB debugging software off-hand, but something that logs when USB devices connect and disconnect might help, and may well exist. If any USB connections are dropped or establish (or re-initialised) whilst Hauptwerk is running then that would potentially indicate a problem.

The test I described should also help to show (especially via the logged MIDI messages' MIDI port names) whether device connections are getting lost/changed.

Also bear in mind that it may only take one USB device (or one USB port) to be misbehaving in order for the connections to all of the USB devices to drop and re-establish (and potentially be swapped).

[jcrowley]

Well, Eureka!
I think I have figured this out!

I removed the MIDItech 8x8 MIDI Merge device.

I re-installed and my old MOTU Micro-lite (they stopped making it years ago, but continue to support the simple device with Windows 1 drivers that are dated this year (2025).

I initially removed it from my build because I was having difficulty with the first manual tripping stepper sequences, but only when I used the lower manual.

I did some more MIDI testing with MIDI Medic and spoke to the folks at Classic MIDI works in Canada. I sent the manual board back to them for repair. When it got there they did not find anything wrong with it and sent it back. I reinstalled the board and by that time I had purchased the MIDItech 8x8 and installed it. BTW it has one of those MIDI Power USB cables and it was connected to the correct port on my computer.

Things just were not adding up. The LCD screens, the LED BarGraph and 7-segment 3 digit Numeric display. The missing LaunchPad ports. The last time all of it worked was in November before I sent the Keyboard motherboard to Classic MIDI works.

So I kicked the MIDItech 8x8 to the curb and after re-installing the MOTU device which operates on a lowly USB-A to USB - B cable with 5 in and 5 out ports. The simplest of devices it really won't ever go wrong unless it is damaged somehow.

Fired back Hauptwerk. It discovered the new MOTU MIDI ports in / out. I flagged them all in the settings arena, low and behold now there is a LaunchPad MIDI port in / out in the setup.

I launched TUP and made all of the usual discovery items. Got the LED Bar Graphs to work, for the Expression Pedals and I had to use the Universal Crescendo discovery method which opened up the Send tab so I could do the old switcher-oo (because I had to say Most Common MIDI changes on the Receive tab - the channel broadcast, and the device which is (11- a potentiometer) for the two expression shoes. (Both are on separate Channels being sent via one MIDI Port in the MOTU) For the Crescendo I use (11) on the Receive tab and (7 - Master Volume, since that sends a percentage to the 3 Digit Display bypassing the "expression" setup - so no Bar Graph).

Then I tackled the LCD screens (3x16x2) displays. I had to set this up differently than I did in Hauptwerk v6. I had to say that each one was Display 001, because they are all on separate MIDI out ports. In Hauptwerk v6, I just configured them to be [Display 001, 002 and 003], It did the correct thing anyway. I do not have these devices daisy chained together only the power is distributed in that fashion.

I had to setup the Universal Stepper items so [<,>,000, Xcl, Set] again because they were distributed on the MIDI Expression T/S junction and the keyboard pistons.

So it was not USB ports problem it was a MIDI problem and the MIDI Out ports did not ever work on the MIDItech 8x8 and perhaps there was not enough power to the unit - but I definitely had it plugged into the correct computer USB port for Powered devices and there is no capability for the device to have an external power source. Too bad because it was extremely expensive - now in the electronic graveyard dump.

So maybe it is all solved. I have rebooted the computer several times today and have had no further issues.

[mdyde]

Thanks, Jeffrey. Excellent -- glad to hear you appear to have it all working now.

[jcrowley]

New Report...and...good news!

Turned on Computer and launched TUP.

All LCD screens working as designed. All Bargraph/Digital displays working.

Lit rockers all still assigned to correct couplers - but still do not light up when "on". HW6 they light up when in the "on" state just via normal "discovery" and "send matching data to device". But I will figure this out in the future.

The Combination Set loaded and displayed on my LCD's. Stepper position displaying. Combination System status and position on LCD displays.

Set, Cancel, Next, Previous, back to 000 worked without having to discover them again.
And most important keyboards retained their assignment and work with actual keyboards and Audio works with the stops and sounds even clearer than before. Audio settings remained intact.

Who knew probably errant MIDI ports would cause this to happen from the audio to the devices.

Lesson Learned.

Thanks!

[mdyde]

Splendid. Thanks, Jeffrey.