Thu Sep 08, 2022 3:09 pm
Hello Adrian,
Please first check that the installation is using Hauptwerk v6.0.2, since that had several important bug-fixes in it above v6.0.0/1. As long as you're using that version then I can basically promise you that the problem isn't due to any bug in Hauptwerk.
The amplitude, sound, and voicing of Hauptwerk's audio output is determined entirely by your Hauptwerk settings, and the *only* situation in which Hauptwerk will ever change any settings automatically is if the relevant settings file is corrupted when Hauptwerk tries to load it (e.g. due to the computer not shutting down cleanly, or due to a memory fault, or drive corruption). In that specific circumstance it will try to revert the corrupted settings file to the last-known-good backup of the file (which it makes and keeps automatically specifically for the purpose), and if that fails too then it will revert the settings file entirely to defaults. In either of those case it will log a warning in the Hauptwerk activity log accordingly, so please try searching the the log ("Help | View activity log") for the word "restore", which should find them. Also check through the log for any other warnings or errors that were logged between the the time that it was working properly and when the problem occurred.
Very importantly, make sure that Hauptwerk and the computer are shutting down cleanly, otherwise settings may get lost or corrupted. Search the log for "INF:4165" messages ("Welcome to Hauptwerk") and make sure that every instance of it is preceded by an "INF:0403" message ("Hauptwerk has finished shutting down."). If it isn't, then Hauptwerk didn't exit cleanly, probably because the computer didn't shut down cleanly, or because an audio or MIDI driver crashed.
Also:
- Test the computer's RAM for errors.
- Test the drive for errors.
Aside from those things, the other thing that will make an organ's settings/voicing appear to become corrupted when reloading an organ after loading a different one is if two organs have the same OrganID in their organ definition files (ODFs), since organ settings/voicing are stored for the OrganID. Sample set producers are supposed to request unique OrganIDs for their sample sets from us, and we allocate them from a central pool to ensure uniqueness. However, if an ODF (or CODM ODF) is used that someone has made themselves with doing that, then its settings/voicing may conflict with those of another organ, resulting in seemingly lost/garbled settings/voicing.
Search the log for the text "Organ ID" (including the space), which will find the messages that are logged whenever an organ has finished loading. Check that the ID of the relevant organ isn't also reported for any other organs.
Very occasionally, virus scanners also corrupted settings files. Also, there have been instances in the past whereby Windows System Restore has tried automatically to revert settings/files/XML to older versions it had backed up, e.g. following a failed Windows updates, or operating system corruption. However, I haven't heard of that occurring for a quite a few years, so maybe Microsoft improved on that.
In case you ever want to compare your current Hauptwerk settings to those from a backup, you could extract the backup via "Help | View/extract the contents of a backup ..." and then compare the corresponding settings files to the current ones using a file comparison utility such as UltraCompare.
However, given that you mention that you route different divisions to different speaker pairs, and that what changed was the relative amplitudes of the divisions, maybe one or more of your amplifiers or speakers developed a fault, or one or more amplifier levels were changed accidentally, or some level setting(s) changed in your audio interface's control panel (or it developed some fault).
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.