Update Polyphony Limit

Important Notice

This script is not officially supported by Hauptwerk. If you are unfamiliar with the use of the Terminal, there is a risk of inadvertently disrupting your Hauptwerk setup.

Please ensure that you carefully follow the instructions provided in the README.md file on GitHub, and create a full backup of your settings before making any changes.

Use this script at your own risk. No responsibility is taken for any issues that may occur as a result of using this script.

Hauptwerk applies conservative default polyphony settings when new sample sets are installed. Adjusting the polyphony limit requires manual changes for each individual sample set.

Hauptwerk stores the polyphony limit for each sample set in individual XML configuration files located in:

HauptwerkUserData/ConfigX-OrganSettings

In this path, X ranges from 0 to 3:

• Config0-OrganSettings is the default configuration folder used when Hauptwerk is launched normally.
• ConfigX-OrganSettings are alternative configuration folders used when launching Hauptwerk in alternate modes..

Each organ’s settings are stored in a file named:

OrganIDxxxxxxConfig.OrganConfig_Hauptwerk_xml

Here, xxxxxx represents the unique UniqueOrganID assigned by the sample set producer.

These files follow the XML format. When opened in a standard text editor, they contain multiple XML nodes and elements. The specific setting relevant to polyphony is stored in the element. The script changes the value of this element.

To streamline the process, a Terminal script has been developed and will soon be published on GitHub.

The script updates only those configuration files whose polyphony limit differs from the selected value. For each modified file, it automatically creates a backup using the .bak extension. This extension is intentionally chosen to avoid conflicts with the backup files automatically generated by Hauptwerk.

Kindly review the comprehensive instructions provided in the README.md file for detailed guidance.

I’d like to express my gratitude to Evert-Jan van der Leij. Thanks to him, the script is now more user-friendly and has been thoroughly tested on Windows.