|
|
|
|
|
|
Known bugs in Hauptwerk
The following is a list of all bugs in Hauptwerk of which we are aware, so that you can work around them when possible. If you find any bugs in Hauptwerk that are not listed on these pages, please contact us and we will add them here.
Known bugs in the current version of Hauptwerk
Please click here to return to the list of known bugs in the current version.
Known bugs in earlier Hauptwerk 3 or Hauptwerk 2 versions, which are fixed in the current version
HW-000002: MIDI system exclusive errors in log when deactivating (Advanced Edition only).
Very occasionally, and on certain computers configured to control large numbers of LCD panels using Hauptwerk's LCD panel system, a large batch of errors (ERR: 3840) appeared in the log file during deactivation, relating to failure to send LCD system exclusive messages. We believe that was due to the MIDI interface driver's buffer becoming flooded. The volume of MIDI messages sent to the LCD panels has now been reduced very significantly, since many of the messages being sent were actually duplicates and thus unnecessary. This appears to have successfully prevented the problem from recurring with good quality (sufficiently-buffered) MIDI interfaces.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000006: [Sample set developers only] Windows Notepad could corrupt Hauptwerk XML files, which crashed Hauptwerk.
If Windows Notepad is used to edit XML files, it can write two-byte 'byte order marker (BOM) codes' to the start of the files, which strictly renders them invalid as XML files. Although not themselves a bug in Hauptwerk, such invalid codes could cause Hauptwerk to crash, so Hauptwerk has been changed simply to ignore such codes.
Product version introduced: 02.00
Product version fixed in: 02.01
HW-000009: Main window occasionally not resized if switched apps during de/activation.
It very occasionally happened that the main window was not resized properly when switching to another application during activation/deactivation.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000010: Component installer packages needed to be copied to hard-drive for installation.
In version 2.00 the component installer would abort incorrectly with error code 1161 (no read privileges) if installing a component package (e.g. sample set) from non-writeable media, such as CD or DVD. The work-around was to copy the files to a hard-drive prior to installing them.
Product version introduced: 02.00
Product version fixed in: 02.01
HW-000011: [Documentation] Incorrect link in user guide.
In version 1.00 of the user guide, on the 'MIDI Implementation' page, the 'MIDI organ consoles section' link on the 5th line pointed to the wrong page.
Product version introduced: 02.00
Product version fixed in: 02.01
HW-000012: [Sample set developers only] If an invalid organ info file was specified in an organ definition, Hauptwerk could crash.
If a sample set developer specified an invalid/non-existent organ-info file in the organ definition file for the sample set then Hauptwerk could crash when 'Organ | Show organ information' was clicked.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000013: [Sample set developers only] first column in diagnostic log files had no comma.
Diagnostic logging is possible for various internal virtual organ objects to aid sample set developers. The first column in these log files should be terminated with a comma, but was not.
Product version introduced: 02.00
Product version fixed in: 02.01
HW-000014: [Sample set developers only] If a sample set image file was missing, the loading progress indicator was not closed after the error.
When creating a sample set, if an image file was specified which was not present, then an error message was given correctly, but the loading progress indicator was not closed.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000015: Original organ tuning option only worked when sample set loaded with 'Organ | Load organ, adjusting rank audio output routing'.
If a sample set has been loaded two or more times consecutively using the 'Organ | Load organ' or stand-by/recent options, its samples are read from a special fast sample cache rather than the original files. In such cases the 'Temperament | Original organ tuning' option could cause no audio output or a crash. The work-around was always to load a sample set with 'Organ | Load organ, adjusting rank audio output routing' if the original organ tuning option was to be used.
Product version introduced: 02.00
Product version fixed in: 02.01
HW-000016: Could not insert/update with 'General settings | Audio output groups' screen.
Clicking OK on the 'General settings | Audio output groups' screen gave error 0813.
Product version introduced: 02.00
Product version fixed in: 02.01
HW-000017: If a combination file was loaded at the same time as notes were being played, sometimes the notes were not released.
When loading a combination file, the stops and controls were reset correctly, but sometimes the keys were not, causing notes to stick until 'Functions | Reset' was selected from the menu.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000018: If an organ was left active for a long period of time, the audio may crash (usually only with DirectSound drivers).
In such circumstances the audio output could become silent or make a buzzing noise, and Hauptwerk would not close or deactivate properly. The problem was extremely unlikely to occur with ASIO drivers.
Product version introduced: 02.00
Product version fixed in: 02.01
HW-000019: Shutting the computer down without first closing Hauptwerk could prevent settings changes being saved.
If the computer was shut down from the Windows Start menu or by pressing the computer's power-off button, Hauptwerk may not have closed cleanly, and any changes to its settings may not have been be saved. This problem did not affect the 'File | Shut computer down' or 'File | Re-start computer' menu items in Hauptwerk, which shut Hauptwerk down correctly before shutting the computer down. The work-arounds were to ensure that you used one of these options, or quit Hauptwerk before shutting the computer down.
Product version introduced: 02.00
Product version fixed in: 02.01
HW-000020: [Sample set developers only] Samples larger than about 8 MB in 32-bit resolution could crash Hauptwerk.
If a sample was loaded in 32-bit resolution, and its size exceeded 8 MB after conversion to that resolution, then Hauptwerk could crash. 8 MB equates to a stereo 32-bit sample at 48 kHz of about 21 seconds in length, hence samples should not exceed that length. This is an intentional limit, and is only listed as a bug because Hauptwerk crashed in such circumstances, rather than reporting the error properly.
Product version introduced: 02.00
Product version fixed in: 02.01
HW-000033: [Sample set developers only] tuning scheme deviation in definition file should always allow zero.
When creating a sample set, the organ definition file should allow zero to be specified for the Pipe_SoundEngine01.Pitch_Tempered_BaseTuningDeviation if the Pitch_Tempered_BaseTuningSchemeCode is an increment type.
Product version introduced: 02.00
Product version fixed in: 02.01
HW-000035: [Documentation] Incorrect reference to organ ID range in CODM User Guide.
In version 1.00 of the Custom Organ Design Module User's Guide, page 13, fourth paragraph the range should read 800000 to 899999.
Product version introduced: 02.00
Product version fixed in: 02.01
HW-000039: Occasionally hung during deactivation or when closing Hauptwerk.
We found a circumstance which could cause Hauptwerk to hang occasionally during deactivation of the audio system, such as when closing the program with a sample set loaded. Because the settings are saved on exit, this could prevent changes to the settings being saved.
Product version introduced: 02.00
Product version fixed in: 02.01
HW-000040: Computer keyboard key codes greater than 255 could not be used for switch (MIDI) inputs.
The 'General settings | Switch (MIDI) inputs' screen allowed maximum values of 255 to be entered for the engaging and disengaging event numbers for 'Computer keyboard key pressed/released' event types. Special keys (function keys, etc.) have higher key codes and so the limit needed to be raised accordingly.
Product version introduced: 02.00
Product version fixed in: 02.01
HW-000041: [Documentation] Computer keyboard key codes for switch (MIDI) inputs were not listed in the user guide.
Key codes needed to be listed in the user guide for 'Computer keyboard key pressed/released' event types for the 'General settings | Switch (MIDI) inputs' screen.
Product version introduced: 02.00
Product version fixed in: 02.01
HW-000047: If there was insufficient memory to load one of Hauptwerk's internal images, an incorrect error message was shown.
If Hauptwerk could not load one of its internal images (e.g. MainBackgroundPage.png) due to insufficient memory or resources, then the error was reported as ERR:4404 or ERR:4405, whereas the message should have been more explicit. Very minor.
Product version introduced: 02.00
Product version fixed in: 02.02
HW-000052: Certain samples (especially percussion) could consume excessive CPU resources, leading to audio break-up at low polyphony with certain stops.
This behaviour is processor-dependent and partly unavoidable on processors earlier than the Pentium 4 (C1 stepping), i.e. Pentium III, AMD Athlon XP and other pre-Pentium 4 processors, since it is caused by the floating point handling of the processor. However, on Pentium 4 (C1 stepping and above), AMD Athlon 64 and AMD Opteron processors, optimisations are available to avoid the problem. Alternative more limited optimisation techniques are possible for the Pentium III and Athlon XP. Although Hauptwerk 2 has always used the optimisations in the Pentium 4 and AMD 64-optimised builds (determined by the processor installation option), due to a compiler issue we have found that one of the optimisations was not being used in a key part of the audio engine. Although arguably not a bug in Hauptwerk itself, we have been able to produce a version that works around the problem for Pentium 4 and AMD 64 processors and, to a more limited extent, for Pentium III and Athlon XP processors. Note that no fix is possible for earlier processors. In particular, this problem caused the audio to break up on the percussion ranks of the Milan Digital Audio Virginia WurliTzer sample set.
Product version introduced: 02.00
Product version fixed in: 02.02
HW-000064: Very occasionally could hang during deactivation or when closing Hauptwerk.
We found a further circumstance which could (very rarely) cause Hauptwerk to hang during deactivation of the audio system, such as when closing the program with a sample set loaded. Because the settings are saved on exit, this could prevent changes to the settings being saved.
Product version introduced: 02.00
Product version fixed in: 02.02
HW-000065: If an audio device driver type (e.g. ASIO or DirectSound) was selected for which no drivers were installed on the computer, and then Hauptwerk was closed at that point, an error message was given preventing a different driver type being selected.
When the audio driver type is changed (either ASIO or DirectSound for stand-alone Windows configurations), Hauptwerk correctly raises an error if no drivers of that type are installed on the computer. However, if Hauptwerk was closed at that point then the message would be given whenever it was re-run, preventing the device driver type being changed back. To prevent that situation it now offers the option to restore the driver type back to its default for the platform (DirectSound on Windows) and then opens in maintenance mode.
Product version introduced: 02.00
Product version fixed in: 02.02
HW-000068: If a MIDI device driver was broken and could be queried, it could prevent Hauptwerk from opening.
If one of the MIDI device drivers for a MIDI device that is or was installed on the computer was broken, and Hauptwerk was unable to query its name from the operating system, Hauptwerk raised an error on initialisation, preventing the program from being opened. Since it was possible that the device was not needed anyway for use with Hauptwerk, such a device is now simply labelled as invalid, rather than a blocking error being raised.
Product version introduced: 02.00
Product version fixed in: 02.02
HW-000069: The fields on the Routing tab of the 'General settings | Audio outputs' screen were not always enabled and disabled correctly and the aux send look-ups sometimes misbehaved.
If the output type was changed on the Routing tab of the 'General settings | Audio outputs' screen, some of the fields on that tab correctly became enabled or disabled. However, if the selection in the left-hand browse list was changed, the status of those fields was not updated. Also the aux send fields sometimes allowed incorrect (primary) audio outputs to be selected, with their look-ups not always being updated properly if audio outputs were inserted or deleted without clicking OK.
Product version introduced: 02.00
Product version fixed in: 02.02
HW-000081: Component installer incorrectly allowed a patch to be installed if a prerequisite version was not present.
When applying a patch to a sample set data package, the component installer did not prevent the patch being applied if an earlier prerequisite version of the package was not already installed and valid.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000082: If a Windows display style (theme) other than 'Windows Classic' was used, the division headings on the Custom Organ Design Module console pages were not always visible.
Organs created with the Custom Organ Design Module show a black bar along the top of each console screen page with labels for the divisions. If the Windows display style (theme) was 'Windows XP' or another style other than 'Windows Classic' with wide window title bars, then the division headings were not always be visible.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000083: Unnecessary console screen redraws when system functions triggered from MIDI or a computer key.
Previously the virtual console was redrawn each time that a 'system function' (menu function) was triggered, regardless of the function and regardless of whether it was triggered from the menu or from a MIDI piston or computer key. In many cases this was unnecessary, such as when entering or leaving capture mode or using the registration sequencer, and caused an unsightly flicker. The screen is now only redrawn when it is absolutely necessary, determined on a function-by-function basis.
Product version introduced: 02.00
Product version fixed in: 02.20
HW-000086: If an aux-send audio output was deleted whilst a primary output was routed to it, a crash was possible.
On the 'General settings |Audio outputs' screen if an audio output was configured as an aux-send output, another (primary) output had that aux-send output specified as an aux-send destination, then the aux-send output was deleted and OK clicked on the screen without first having navigated to the referring primary output, Hauptwerk would crash.
Product version introduced: 02.02
Product version fixed in: 02.10
HW-000087: Very occasionally a recorded audio output file was not be finalised properly when recording was stopped.
This circumstance was very unlikely unless many audio streams were recorded simultaneously, e.g. when using many audio output channels (multi-channel audio output) and recording them all separately, rather than mixing them down and recording just the mixed output.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000091: [VSTi only] Selecting a sample set via the VST instrument program number/name in the VSTi edition of Hauptwerk could cause the sample set to be re-loaded unnecessarily when the host project was saved.
In the VSTi edition of Hauptwerk, a sample set can be specified by assigning it as a stand-by organ and then selecting the corresponding entry as the program property of the VST instrument in the VST host software. However, some hosts trigger a program selection when saving a project or at other times, which could cause Hauptwerk to re-load the specified sample set unnecessarily. Hauptwerk has been changed to ignore such selection messages if the corresponding program (stand-by sample set) is already selected. Please note that sequencer projects saved for use with versions of Hauptwerk prior to 2.10 may need to have their VST instrument program number (stand-by sample set) updated, since it has been necessary to re-number the programs to work around this problem.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000109: [VSTi only] The VST plug-in 'program' numbers did not all correspond properly to the stand-by organ numbers.
In the VSTi edition of Hauptwerk, a sample set can be recalled by assigning it as a stand-by organ and then selecting the corresponding entry as the program property of the VST instrument in the VST host software. However, only the first of the eight VST 'program' entries were triggering stand-by organ entries, and then not the ones expected. This has now been corrected, and all eight stand-by organs can be recalled from VST 'programs'. Additionally, a VST program entry has been added which causes no organ to loaded. Please note that sequencer projects saved for use with versions of Hauptwerk prior to 2.10 may need to have their VST instrument program number (stand-by sample set) updated, since it has been necessary to re-number the programs to correct this problem.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000112: Console screen area could vary slightly according to Windows style/theme.
If the Windows display style (theme) is 'Windows XP' or another style other than 'Windows Classic' with wide window title bars, then the top few pixels of a sample set's console window could be hidden by the page tab bar.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000115: [Documentation] In the 'virtual console' section of the user guide the St. Anne's setter piston was incorrectly referred to as labelled 'S'.
The St. Anne's setter piston was incorrectly referenced in the user guide.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000116: [St. Anne's, Moseley organ sample set] The couplers were not being recalled by the crescendo action.
On the crescendo programmer page, the couplers were stored and recalled properly in combination files but did not actually affect the couplers when the pedal was operated.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000118: [VSTi only] An LCD panel object and MIDI output path were included in the default configuration even though the LCD system is disabled for the VSTi edition.
The VSTi edition of Hauptwerk does not allow the LCD panel system to be used since the VST specification does not support the required type of MIDI messages. However, an LCD panel entry and associated MIDI output path were included in the default configuration, and could not be deleted because the LCD panel screen is not available in the VSTi edition, thus preventing deletion of the spurious output path.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000120: [Documentation] Trivial typing error in 'registration sequencer' section of user guide.
The example showing the frame number calculation by bank was incorrect.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000129: Unlikely circumstance identified in which sample cache could be regenerated unnecessarily.
If a sample set has been loaded two or more times consecutively using the 'Organ | Load organ' or stand-by/recent options, its samples are read from a special fast sample cache rather than the original files. A very unlikely circumstance was found in which the cache could be regenerated unnecessarily, causing a longer than necessary loading time on rare occasions. Diagnostic messages have also been added to the log file to show the reason that the cache is regenerated each time to help diagnose such problems in the future.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000138: Custom Organ Design Module works with short tremulant samples.
Previously the Custom Organ Design Module (CODM) required each tremulant waveform sample to have at least 100 milliseconds of data before the start of a loop to allow for its crossfade. Since this has caused problems with certain sample sets (notably the Milan Digital Audio Virginia Virtual WurliTzer), the length of the crossfade has been reduced to 10 milliseconds to improve compatibility. In particular, the CODM is now compatible with the Virgina WurliTzer sample set.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000147: Hauptwerk could occasionally crash on a few particular PCs if tremulants with particular parameters were left running for long periods of time.
Only a very small number of computers exhibited this problem, and only then with particular sample sets, notably the Milan Digital Audio Virginia Virtual WurliTzer. It was traced to a bug in Hauptwerk's tremulant synchronisation mechanism which was sensitive to the particular tremulant settings and timing of the computer, and has now been fixed.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000152: When console screen display is disabled the screen size was still checked.
When using Hauptwerk 'headless' (with no mouse, monitor or computer keyboard connected), the computer's display driver often sets the desktop screen size to a standard basic size (e.g. 1024 x 768 pixels). Hauptwerk's display can be disabled for such 'headless' use, but was still checking whether the resolution was sufficient when loading a sample set. This could prevent a sample set with a large screen display from loading if no monitor was connected.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000184: CODM documentation: trivial error in Custom Organ Design Module user's guide.
The description of the StopRank.MIDINoteNumOfFirstMappedDivisionKey field in the Custom Organ Design Module (CODM) user's guide had a minor error.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000185: Re-installing a patch with the component installer would un-install the component first.
If a sample set data component was installed, then patched, then the same patch applied a second time, the component would incorrectly be un-installed prior to re-applying the patch, which could leave it only partly installed.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000186: Component installer would fail to clean up temporary files after installation if hidden files were included in a sample set.
Although a sample set should not contain hidden files, Hauptwerk has been changed to be resilient to their existence. Previously, if a sample set contained hidden files, the component installer would install the components properly but then give error 'ERR:1220 Could not empty Hauptwerk's temporary folder ...' after their installation.
Product version introduced: 02.00
Product version fixed in: 02.10
HW-000198: No audio device channels were available for selection with ASIO drivers that support 44100 Hz sample rate only.
When Hauptwerk queries the audio devices (which occurs if the selected driver type or audio hardware change), no channels will be listed on the 'General settings | Audio output channels' screen if it is unable to query the driver (usually because it is in use by another application) or if the driver does not support any of Hauptwerk's audio formats. The reasons are written to the main Hauptwerk log file. If an ASIO driver supported ONLY the 44.1 kHz sample rate, Hauptwerk incorrectly concluded that no supported sample rates were available, even though 44.1 kHz is in fact a valid sample rate for Hauptwerk. This bug affected very few ASIO drivers since almost all also support sample rates other than 44.1 kHz. Such drivers are now handled correctly.
Product version introduced: 02.00
Product version fixed in: 02.11
HW-000199: Was very occasionally possible to cause a crash by deactivating/unloading at exactly the instant that a MIDI message was being processed.
A virtual console screen update resulting from the MIDI message could conflict with the screen handling during deactivation.
Product version introduced: 02.10
Product version fixed in: 03.00
HW-000205: Hauptwerk v1 Silver Octopus 25/36-stop Willis sample sets did not import into v2.10 properly.
A few entries were found in the Hauptwerk version 1 Silver Octopus 25/36-stop Willis organ definition files which caused problems when importing into Hauptwerk version 2.10. The import process has been changed to allow for these circumstances for version 2.11 onwards. If you previously tried and failed to import one of these sample sets, please re-import the sample set using Hauptwerk version 2.11 or above before attempting to load it via the 'Organ' menu. Note that, because the keyboards were assigned in an unconventional order, once the sample sets have loaded, you may need to use 'Organ settings | Connect keyboard MIDI inputs to organ keyboards' to adjust the keyboard assignments. Hauptwerk now detects and corrects cases where the pedalboard was assigned a MIDI input other than the conventional pedalboard input (which previously caused the wrong key images to be displayed for the pedalboard and a manual) and allows for console image items that are partly or fully outside the visible screen area.
Product version introduced: 02.10
Product version fixed in: 02.11
HW-000209: Prospectum Carl Schaefer and St. Michael Hauptwerk v1 organ sample set did not import into v2.10 properly.
A few entries were found in the Hauptwerk version 1 Prospectum Carl Schaefer and Prospectum St. Michael organ definition files which caused problems when importing into Hauptwerk version 2.10. The import process has been changed to allow for these circumstances for version 2.11 onwards. If you previously tried and failed to import one of these sample sets, please re-import the sample set using Hauptwerk version 2.11 or above before attempting to load it via the 'Organ' menu. Specifically, Hauptwerk now ignores cases where multiple keyboards were assigned to the same Hauptwerk version 1 MIDI input, and detects and corrects cases where the pedalboard was assigned a MIDI input other than the conventional pedalboard input (which previously caused the wrong key images to be displayed for the pedalboard and a manual).
Product version introduced: 02.10
Product version fixed in: 02.11
HW-000210: On the pipe voicing screen, if the 'QUICK' faders had been used, Hauptwerk could sometimes crash.
The problem only occurred after adjusting the 'QUICK' faders for octaves without a full complement of pipes.
Product version introduced: 02.10
Product version fixed in: 02.11
HW-000221: Periodic audio glitches were audible on some PCs with version of v2.10.
A few computers (probably determined by the motherboard design) were found to experience periodic very brief audio glitches, usually about once every 1 to 3 minutes.
Product version introduced: 02.10
Product version fixed in: 02.11
HW-000227: Tab order was incorrect on the 'Organ settings | General options' screen.
Most notably on the 'Audio Engine' tab.
Product version introduced: 02.10
Product version fixed in: 02.11
HW-000230: Hauptwerk v1 aH Moerdijk Marcussen sample set would not load when imported into v2.10.
The 34/04-D#1.wav sample in the Hauptwerk version 1 edition of the aH Marcussen sample set had a corrupted loop point, which prevented the sample set from loading once imported into Hauptwerk version 2.10. The error number given was 'ERR:4926 The sample file 34/04-D#1.wav is invalid ...'. For Hauptwerk version 2.11 onwards, Hauptwerk tolerates an invalid loop point in the same way that version 1 did; the loop will not sound correctly if the key is held down for a long time, but the sample set can still be loaded and used apart from that. A warning is now written to the log file for such samples.
Product version introduced: 02.10
Product version fixed in: 02.11
HW-000233: MIDI input had a tendency to stick with extreme processor loads on multi-processor systems.
Previously on multi-core/multi-processor computers with certain MIDI or audio drivers there was a tendency for the MIDI stream to become delayed the first time that many pipes sounded after activation, causing notes to stick in the 'on' state for a few seconds. Usually it would only happen only once (occasionally twice), shortly after activation, and only with very large chords with more than a few hundred pipes sounding at once, and would work normally thereafter. Some fine-tuning of Hauptwerk's multi-processor engine and NUMA optimisations have eliminated this problem, and MIDI input should now be fully responsive under even extreme processor loads.
Product version introduced: 02.00
Product version fixed in: 02.20
HW-000238: Some pipes with release sample(s) in separate files to the attack/sustain sample(s) did not play correctly in version 2.10.
In particular, some of the ranks on the Sonus Paradisi Doksy Rieger sample set were affected by this problem and produced odd sounds.
Product version introduced: 02.10
Product version fixed in: 02.11
HW-000242: Installer: Now able to repair partial/broken installations/deinstallations properly.
Previously if an installation or deinstallation failed part way through, which could happen if an error occurred reading the Hauptwerk CD, it was possible that the installer would be misled into believing that Hauptwerk was already installed, whilst being unable to repair the installation due to the installation paths being detected as 'NULL'. The installer has been changed to handle this situation safely. Now if some of the paths cannot be detected the installer behaves as for a clean installation, thus allowing the whole installation to be overwritten or repaired.
Product version introduced: 02.00
Product version fixed in: 02.20
HW-000246: The 'Organ settings | General options' option to disable voicing did nothing.
It now correctly bypasses any user voicing changes.
Product version introduced: 02.10
Product version fixed in: 03.10
HW-000253: Installer: main installer executable resilient to CD/download data errors.
Previously, if the Hauptwerk CD media was physically damaged or a data read/write error occurred, Hauptwerk's installer could continue but produce unexpected results, sometimes corrupting the Hauptwerk installation. To make it more robust against such media/download errors, the main installer executable is now contained within a self-extracting archive file that includes automatic error-checking. Hence an error will now be shown if the media/file is corrupted, preventing the installer itself from executing and potentially causing damage to an installation.
Product version introduced: 02.00
Product version fixed in: 02.20
HW-000267: Hauptwerk v1 import: minor difference in behaviour between v1.2x and v2.1x with one Sonus Paradisi Doksy-Kruh v1 organ definition file.
The 'compound mixture' version of the Hauptwerk version 1 organ definition file for the Sonus Paradisi Doksy-Kruh sample set assigns several stops to the same MIDI note number. When imported into Hauptwerk version 2.10+, those are presented as multiple stops, and could not be mapped to a single MIDI switch. As far as we know, that was the only Hauptwerk version 1 organ definition configured in that way (multi-rank stops controlled by a virtual invisible keyboard in a version 1 organ definition file work as expected, which was the conventional way to control multi-rank stops in version 1). It is no longer a problem because it is now possible to assign several virtual stops to be controlled from a single MIDI switch (e.g. MIDI draw-knob/tab or computer key), as covered in ENHANCEMENT HW-000243.
Product version introduced: 02.10
Product version fixed in: 03.00
HW-000272: Component installer occasionally crashed when installing certain sample sets.
With a few particular sample sets, some users reported problems with the component installing crashing during extraction prior to sample set installation on certain computers. The third-party archive extraction tool, used by Hauptwerk to perform the extraction, has been updated to a more recent version and this problem now appears to be fixed.
Product version introduced: 02.00
Product version fixed in: 02.20
HW-000276: VSTi: crash on launch if Hauptwerk's main configuration file had been deleted/moved.
If Hauptwerk's main configuration file had accidentally been moved or deleted by the user, launching the Hauptwerk VSTi plug-in would correctly show error message 4114 (indicating that its settings file could not be found) but then crash. It now shows the error message and exits properly.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000284: [Documentation] Incorrect footnote in prerequisites about Image-Line FL Studio VST Host features.
The host does, in fact, allow multiple audio outputs from a VST plug-in.
Product version introduced: 02.10
Product version fixed in: 02.20
HW-000287: Global setting to disable multiple loops should reload any currently-loaded organ.
Changing the 'Disable multiple sample loops' setting on the 'General settings | General options | Audio Engine' screen should cause any currently-loaded organ to be re-loaded, but did not.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000291: Changes in tremulant rates in organ definition files were being ignored unless voicing was reset.
Voicing data are stored for tremulants, including the tremulant rates. However, the user voicing screen to adjust tremulant parameters has not yet been included in Hauptwerk. Since a tremulant rate voicing parameter overrides the organ definition value, this was preventing changes to the rate being picked up from the organ definition file, for example if the user changed the rate value in a Custom Organ Design Module (CODM) organ definition, unless the voicing was reset explicitly. The tremulant voicing parameters are now ignored until the relevant user tremulant voicing screen has been implemented.
Product version introduced: 02.10
Product version fixed in: 02.20
HW-000314: Hauptwerk v1 import: error was given if Enclosure.AmplitudeMinimumLevel was greater than 60.
When importing a Hauptwerk version 1 organ, an error would be given if the [Enclosure] AmplitudeMinimumLevel setting in the v1 organ definition file was greater than approximately 60. This did not affect any commercial version 1 sample sets and the setting would not normally be set that high, so it was very unlikely to affect user-created organ definitions.
Product version introduced: 02.10
Product version fixed in: 03.00
HW-000316: MIDI system-exclusive dumps larger than 256 bytes could cause notes to stick or other corruption of MIDI input stream.
In practice this was unlikely, but the problem has now been rectified.
Product version introduced: 02.00
Product version fixed in: 02.20
HW-000327: Output LCD status display could cause unnecessary MIDI reset messages with some MIDI drivers (Concert Edition only).
The Concert Edition of Hauptwerk has functionality to drive an LCD panel to display Hauptwerk's status without needing a computer monitor. An incorrect byte in the MIDI system exclusive message used to control it could previously trigger some MIDI drivers and devices to perform a MIDI reset.
Product version introduced: 02.00
Product version fixed in: 02.20
HW-000328: Output MIDI status indicator lamp system was not compatible with all MIDI decoders (Concert Edition only).
Hauptwerk has functionality to control lamps/LEDs as indicators for its statuses (organ loaded, recording, combination capture mode, etc.), to allow operation without a computer monitor. Previously these status messages were configured by default to send MIDI note-on/off messages with a velocity of zero. However, many MIDI decoders interpret a note-on message with velocity zero as a note-off message. A velocity of 127 is now sent by default for these messages.
Product version introduced: 02.00
Product version fixed in: 02.20
HW-000329: Custom Organ Design Module ignoring full organ name.
In the Custom Organ Design Module (CODM) both a 'full' and 'short' name can be specified for an organ definition. Previously the full name was being ignored.
Product version introduced: 02.00
Product version fixed in: 02.20
HW-000330: Stand-by combination file menu items 2-8 were not working properly.
Combination files can be assigned to the menu using eight 'stand-by' menu items so that they can be recalled quickly via the menu or from MIDI pistons or computer keys. Previously, assigning a combination file to any of the eight stand-by slots always incorrectly assigned it to slot number one.
Product version introduced: 02.00
Product version fixed in: 02.20
HW-000337: Rare settings corruption problem fixed.
An extremely rare circumstance was identified in which it was possible that one of Hauptwerk's settings files could be corrupted when unloading an organ or closing Hauptwerk. The problem has now been fixed.
Product version introduced: 02.00
Product version fixed in: 02.20
HW-000349: Component installer was forgetting last-used folder following a deinstallation.
Previously the last-used component package folder was not being used as a default if a deinstallation had been performed immediately before installing a new package.
Product version introduced: 02.10
Product version fixed in: 02.20
HW-000390: [Sample set developers only] Conditional inertia/Willis continuous control linkage timing error.
There was a problem whereby conditional inertia/Willis-type continuous control linkages in an organ definition were being evaluated using an incorrect time interval the first time that they were iterated when the condition changed state, causing unexpected behaviour with theatre organ pizzicato couplers and similar mechanisms for forthcoming sample sets. This problem is not known to affect any existing sample sets.
Product version introduced: 02.00
Product version fixed in: 02.20
HW-000391: Installer: un-installer could freeze if installation had previously been upgraded from pre-v2.20 version (Windows only).
If you previously had a version of Hauptwerk 2 installed prior to 2.20 and then upgraded to 2.20 or later, the un-installer could freeze during the final stage when removing Windows registry entries.
Product version introduced: 02.20
Product version fixed in: 02.21
HW-000395: Documentation/installer: installation note that dongle driver installer window can appear behind other windows (Windows only).
The driver for the USB licence dongle is automatically installed or upgraded by Hauptwerk's installer as a final installation step. On Windows PCs, if you use Alt+Tab to switch to another application during installation then you use Alt+Tab to switch back to Hauptwerk's installer, it may appear to have frozen whilst waiting for the driver to install. In fact that is not the case - the driver installer is a separate application, so you just need to switch to that to acknowledge its status message. If you do not switch applications during installation then the driver installer's window always appears on top, so it is obvious that you just need to click OK on it. This behaviour probably cannot be changed because the driver installer is a separate application, but a note to this effect has been included in the installation instructions in the user guide.
Product version introduced: 02.20
Product version fixed in: 02.21
HW-000400: Installer: non-English or non alpha-numeric characters in installation folder names could prevent Hauptwerk launching (Windows only).
Characters other than a-z, A-Z, 0-9, space, underscore and hyphen (such as an ampersand) could be incorrectly encoded into Hauptwerk's XML settings files by the installer, preventing Hauptwerk from reading the folder names correctly. In such cases you could see error 1108 (XML parsing error) in a file named FileLocations.Hauptwerk.xml when you attempted to launch Hauptwerk. Special characters should now be encoded correctly by the installer, so any folder names valid for the operating system should be acceptable on Windows PCs. Please note that non-English characters in installation folder names may still cause problems on Mac OS X and additional work will be needed to address the issue fully on that platform (see bug HW-000679). Hence please still use only the a-z, A-Z, 0-9, space, underscore and hyphen characters in folder names when installing Hauptwerk on Mac OS X.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000402: Component installer could appear to have frozen when installing very large sample sets (Windows only).
In Hauptwerk version 2.20 onwards, when you have selected a component package to install using the 'File | Install organ, sample set, temperament or impulse response' menu function, Hauptwerk's component installer first copies the whole component package file to a temporary location on your hard-disk before attempting to extract it. During this initial copying process the message 'Please wait whilst the component package is prepared for extraction' is displayed, with a progress indicator beneath it. However, with extremely large component package files of several gigabytes, the progress indicator could incorrectly stay at 0 percent throughout the whole process. Since copying a file of several gigabytes may easily take five minutes or more, it appeared that Hauptwerk had frozen. This problem was related to the way that the size of such files is reported incorrectly by some Windows functions, and the problem did not affect Mac OS X.
Product version introduced: 02.20
Product version fixed in: 02.21
HW-000403: VSTi: error message ERR:0813 could appear when clicking OK on audio outputs screen.
In the VSTi configuration (only) of Hauptwerk, clicking OK on the 'General settings | Audio outputs' screen could give 'ERR:0813 You have specified a value for the attribute named buffer size (sample frames), which is not allowed'.
Product version introduced: 02.20
Product version fixed in: 02.21
HW-000404: Possible periodic audio glitches when recording output (Windows only).
Occasional glitches in the audio output could be heard in version 2.20 (only) when the output was being recorded. These usually took the form of a brief glitch lasting a few milliseconds every 20 - 90 seconds and were related to the buffering of the audio stream. They may or may not have appeared in the recorded audio, usually not. This only seems to have been a problem on Windows; it had not been found to affect Mac OS X.
Product version introduced: 02.20
Product version fixed in: 02.21
HW-000405: Installer: Hauptwerk 2.20 installer could cause user settings to revert to their defaults under a certain circumstance.
If you had not used Hauptwerk version 2 since the 31 October 2006 before upgrading to version 2.20, version 2.20's installer would overwrite your general settings with its defaults because the timestamp on the default settings files was 31 October and it would incorrectly overwrite the settings if its default files were more recent than those already installed. If you had already upgraded to 2.20 and had been affected by this problem and want to recover your previous settings, please contact us for instructions.
Product version introduced: 02.20
Product version fixed in: 02.21
HW-000406: Notes could stay on if a MIDI sequencer was stopped with notes sounding.
Some MIDI sequencers (notably Cakewalk Sonar) do not send individual note-off messages for any pressed keys when playback is stopped, instead sending a single 'all notes off' message. Hauptwerk versions 2.20 and below did not implement the special MIDI 'all notes off' message, so the notes could remain sounding if a MIDI sequencer was stopped while notes were sounding.
Product version introduced: 02.00
Product version fixed in: 02.21
HW-000407: CODM: value of 0 for Rank.WindSupply_MaxFlowRandomisationPct parameter gives error.
When using the Custom Organ Design Module (CODM) for non-pipe 'ranks' (e.g. harpsichords) one might reasonably want to disable the turbulence model by setting the WindSupply_MaxFlowRandomisationPct parameter to 0 for the Rank table. However, doing so gave error ERR:4505 when loading the compiled organ definition file.
Product version introduced: 02.00
Product version fixed in: 02.21
HW-000409: Very occasionally virtual console display was not redrawn fully after an organ was loaded.
After loading an organ, on rare occasions the virtual console display would be only partly drawn, leaving parts of the logo screen still visible.
Product version introduced: 02.20
Product version fixed in: 02.21
HW-000410: Global organ start-up mode was reset if user aborted organ load.
Previously, if an error occurred when loading an organ that was set to load automatically on Hauptwerk start, the 'General settings | General options | Organ loading mode when Hauptwerk starts' setting was reset to its default of 'Normal (inactive, no organ loaded)' to ensure that an error loading an organ couldn't lead to a situation in which it was impossible to open Hauptwerk. However, if the user cancelled the load that would also reset the setting. The setting is now only reset if a genuine error occurs.
Product version introduced: 02.00
Product version fixed in: 03.10
HW-000412: Copy-protected sample sets would not install or load on Apple Mac G4/G5 computers using Hauptwerk 2.20 (Mac OS X only).
If you tried to install a copy-protected sample set on an Apple Mac with a G4 or G5 processor (only) using Hauptwerk version 2.20, error ERR:1223 would appear, preventing the installation from continuing. This problem did not affect Apple Macs with an Intel processor or Windows PCs.
Product version introduced: 02.20
Product version fixed in: 02.21
HW-000423: Component installer could be very slow in version 2.20 when installing large sample sets (Windows only).
In Hauptwerk version 2.20 onwards when you have selected a component package to install using the 'File | Install organ, sample set, temperament or impulse response' menu function, Hauptwerk's component installer first copies the whole component package file to a temporary location on your hard-disk before attempting to extract it. In version 2.20 on Windows PCs this copying process could be very slow, depending on the speed of the CD/DVD drive. The problem did not affect Mac OS X. It has been possible to speed up the copying so that sample sets now install much faster.
Product version introduced: 02.20
Product version fixed in: 02.21
HW-000424: Component installer: crash during sample set installation was possible with large sample sets (Windows only).
In previous versions of Hauptwerk it was recommended that Windows' virtual memory should be disabled to prevent Hauptwerk's sample data being cached ('paged') to disk. This is no longer necessary (see ENHANCEMENT HW-000483) since Hauptwerk now guarantees that sample data are kept only in physical memory, and we now recommend keeping Windows virtual memory enabled. Hauptwerk's component installer (used when installing sample sets) calls a third-party utility to extract the sample set data, which could sometimes crash when installing very large sample sets, causing Hauptwerk itself to crash. This usually occurred when Windows virtual memory was disabled or exhausted and should no longer happen. Hauptwerk also now attempts to trap and handle any crashes from the third-party utility so that Hauptwerk itself should not crash even if a virtual memory shortage does still arise.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000425: VSTi: recording format setting was not mandatory on audio outputs screen.
In the VSTi version (only) on the 'General settings | Audio outputs' screen the recording format setting was not mandatory, but should have been. This caused no functional problems.
Product version introduced: 02.20
Product version fixed in: 02.21
HW-000427: Crash could occur with some sample sets if blower turned off and wind regulators allowed to deflate fully (Non-USA Advanced Edition only).
The Advanced Edition of Hauptwerk includes a physical model of a pipe organ wind supply (not available in the U.S.A.). Some sample sets include a blower switch, which allows the wind regulators to deflate. If the regulators were allowed to deflate fully whilst pipes were sounding a crash could sometimes occur.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000428: 'What's this' question-mark help not working on Apple G4/G5 computers using Hauptwerk 2.20 (Mac OS X only).
Each settings screen has a question mark button which is used to provide help for each setting on the screen. Clicking that button on Apple G4/G5 computers (only) caused Hauptwerk to crash.
Product version introduced: 02.20
Product version fixed in: 02.21
HW-000432: Component installer: was still slow to read some sample sets from DVD or CD (Windows only).
Although previous versions included speed enhancements in this area, when installing certain sample sets from CD or DVD, Hauptwerk's component installer could still be slow to read the CDs/DVDs on Windows PCs. Additional optimisation has been added that now ensures that all CDs and DVDs are read at least as fast as Windows Explorer is able to copy files from them. This reduces the overall time taken to install such sample sets very significantly.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000435: CODM: very large numbers of virtual divisions or swell boxes could cause memory error or crash on activation.
This has now been rectified. Please note, however, that large numbers of divisions or swell boxes increase the processing load for the wind supply model (not available in the U.S.A.), so should still be used with caution in order to avoid excessive reductions in polyphony if the wind supply model is enabled.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000436: [Sample set developers only] If sample and output sample rates differed then original organ tuning option gave the wrong pitch.
If one or more samples within a sample set was saved using a different sample rate to the global output sample rate for the sample set, then Hauptwerk's 'original organ pitch' temperament option (only) could cause those samples to sound at the wrong pitch. This was not known to affect any current sample sets and has now been corrected.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000441: Markers within a sample were numbered backwards.
If a sample had more than one marker (WAV 'cue point') within it and the sample set specified where the pipe release should start using the marker number, then the wrong marker might be used because Hauptwerk (versions 2.10 to 2.21 only) numbered them backwards from the end of the sample, whereas they should be numbered forwards from the start. This was only known to affect some Sonus Paradisi/Hauptwerk.cz sample sets, giving less prominent decay transients than intended for those sample sets, and has now been rectified.
Product version introduced: 02.10
Product version fixed in: 03.00
HW-000444: CODM: specifying an enclosure for a non-existent division caused a crash.
In the Custom Organ Design Module, if an enclosure was included for a division that did not exist for the organ, Hauptwerk would crash when attempting to load the custom organ. It now correctly gives an error message.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000452: VSTi: Auto-load organ option gave VST error message.
Using the 'General settings | General options' screen to set the 'Organ loading mode when Hauptwerk starts' setting to anything other than 'Normal' could cause the VST host program to give an error indicating that the plug-in failed to install/initialise when launching. This has now been fixed. Please note, however, that some hosts (notably Sonar and Cubase 4) instantiate and open all installed plug-ins when they start, causing the organ to load every time that the host is opened, which can be very slow. Hence in general it is still recommended that you use the VST host's VST program selection for the Hauptwerk plug-in to select the organ to load instead, which allows a Hauptwerk stand-by organ to be chosen and is usually saved in the VST host program's project file.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000461: CODM: Unnecessary unique constraints on StopRank table.
In the Custom Organ Design Module (CODM) there was a unique constraint on the StopRank table on the fields (StopCode, RankID) and another on (StopCode, ExternalRankID). Those constraints were not necessary, and prevented a given rank being referenced multiple times with partial compasses for a given stop, for example to use it within several parts of a mixture or other compound stop. This did not affect the main organ definition file format. The unnecessary constraints have now been removed.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000465: Component installer: error message 1223 (can't read organ definition because no valid licence found) clarified.
If attempting to install a protected sample set when no valid licence had been installed on the USB licence key dongle for the sample set, Hauptwerk's component installer gives error message 1223. The text of the message was somewhat confusing, and has been clarified.
Product version introduced: 02.10
Product version fixed in: 03.00
HW-000468: MySQL database integration: backslash character in a filename gave XML parsing error.
The separately-licensed MySQL database integration option allows organ definition files to be exported to and imported from a MySQL database as a tool for sample set development. If an organ definition file contained a backslash character then incorrect data could be exported to the database (since a backslash character has a special meaning in SQL scripts), which could give error 'ERR:1108 XML parsing error at line NN [not well-formed]' when the database was imported back into Hauptwerk. This has now been corrected. Note also that Hauptwerk interprets both forward-slash and backslash character as valid directory separators for compatibility with both Windows and Mac OS X.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000469: Bug in Creative X-Fi ASIO driver could cause Hauptwerk to lose user settings changes (Windows only).
Hauptwerk queries the installed audio devices when it starts. Due to a bug in the Creative X-Fi ASIO driver whereby the driver gives an invalid response when queried, if you had a Creative X-Fi sound card installed in the PC, Hauptwerk could show error 'ERR:1132 Failed to validate the 'ChannelGroupNumber' attribute of the 'AudioOutputDeviceChannel' object' in its log file, followed by 'INF:4116 The main Hauptwerk configuration file Config.Hauptwerk.xml, located in the configuration file folder, could not be loaded successfully and may have been corrupt or contained invalid settings or values. Hauptwerk successfully restored and loaded the file automatically from backup. However, some previous settings changes may have been lost as a result.' The main effect of this was that any settings changes you made would be lost when you next started Hauptwerk. Hauptwerk has been changed to work around the driver bug explicitly, so that the invalid responses from the Creative driver no longer cause any errors to be reported or Hauptwerk settings to be lost or reverted.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000470: Some audio interfaces' ASIO buffer sizes could not be adjusted without external access to the drivers' ASIO control panel (Windows only).
In Hauptwerk version 2.20 the option to open the audio interface driver's ASIO control panel was removed from the Hauptwerk menu and instead the ASIO buffer size was made adjustable via the 'General settings | Audio outputs' screen, since that was felt to be more user-friendly. However, some audio drivers, such as the Echo Gina/Darla ASIO driver, ignore any requested ASIO buffer sizes and only uses the value set via their own ASIO control panel. Since that control panel is not accessible via all drivers' audio control panel utilities and was no longer accessible via Hauptwerk, the ASIO buffer size could not be adjusted for those interfaces. A new button has been added to the 'General settings | Audio outputs' screen to open any selected ASIO driver's ASIO control panel, thus allowing the buffer size to be adjusted again natively for such devices.
Product version introduced: 02.20
Product version fixed in: 03.00
HW-000474: Installer: froze during installation on a few Apple Macs (Mac OS X only).
Hauptwerk's installer is a Java application and relies upon the Java system within Mac OS X. A few users reported to us that the installer froze on certain Macs, either during its initialisation or during the installation phase (usually when installation shows that UninstallHauptwerk.app was being installed). This appeared to occur if OS X's Java installation was not fully current, if 1.4 rather than 1.5 was selected for OS X's default Java version, or if OS X's Java installation had become corrupted. Hauptwerk's installer has now been changed to use Java version 1.5 only, regardless of OS X's default Java version setting. We believe that has addressed the problem. If you do still experience the problem, please first wait for a few minutes to ensure that the installer has genuinely frozen, rather than just running slowly. Please then ensure that all current OS X updates have been applied (click on the Apple icon at the top-left of your screen and select 'Software Update ...' and allow it to apply all updates, especially any relating to Java). Reboot if any updates were applied. If that doesn't solve the problem, please let us know.
Product version introduced: 02.20
Product version fixed in: 03.00
HW-000475: CODM: General tremulant could not be included.
In the Custom Organ Design Module, attempting to include a general tremulant in the organ specification caused an error message.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000476: Hauptwerk v1 import: imported organs could be slow to load the first time and their organ-specific settings could be lost/overwritten if importing from multiple configurations alternately.
Hauptwerk identifies each organ by an ID number, which is globally unique across all sample sets and organs. All organ-specific settings for the organ are stored relative to that ID number to enable Hauptwerk to identify which settings relate to the organ. For sample sets in the native version 2 sample format and later that ID number is assigned centrally by Crumhorn Labs to guarantee uniqueness. However, the Hauptwerk version 1 format did not have any means of identifying organs uniquely since Hauptwerk version 1 did not have any organ-specific settings. Hence when a version 1 organ is imported, Hauptwerk must generate a new ID number to identify it so that settings can be saved for it. Previously, Hauptwerk attempted to ensure that the number was unique by assigning IDs incrementally for each imported version 1 organ from within a range of numbers reserved from the purpose. The last-allocated ID number used for importing version 1 organs was stored internally in the global settings for each Hauptwerk configuration (stand-alone, MIDI sequencer or VSTi). However, if you reinstalled Hauptwerk, reverted some but not all of its settings (which can happen if you use Windows System Restore), or imported version 1 organs from multiple configurations alternately, the last-allocated ID number for the configuration might no longer have been accurate, causing an imported version 1 organ to be assigned an ID number that had previously been assigned to another version 1 organ. The effect of this was that the organ might be very slow to load the first time after it had been imported and its organ-specific settings could be incorrect. We have now changed the version 1 organ importing mechanism to search all configurations for evidence of a given ID number having been used previously before assigning it. If the ID had previously been used and the version 1 organ definition filename matches that being imported, then it is reused so that previous settings saved for the organ should be preserved if importing the same version 1 organ definition file multiple times. If the ID had been used for a different version 1 organ definition file, then it is not now reused, preventing incorrect settings being applied to the newly-imported version 1 organ in the above cases.
Product version introduced: 02.10
Product version fixed in: 03.00
HW-000480: Licensed copies of Hauptwerk could start in evaluation mode if launched automatically on boot (Mac OS X only) and new option to wait for dongle to be found on start-up.
On Mac OS X it is possible to make an application such as Hauptwerk launch automatically when the computer is booted by adding it to the 'Login Items' list for a given operating system account in the Accounts preferences pane within the System Preferences utility, or by dragging the Hauptwerk short-cut to the Dock and right-clicking on it. However, if your computer has only a single user account, with its login options set to log into that account automatically (i.e. no login screen is displayed, which might be the case if you wanted to use the computer purely as an engine for running Hauptwerk, with no direct interaction with the computer), then OS X can start very rapidly, and could log in and launch Hauptwerk before the dongle driver had finished initialising, causing Hauptwerk to start in evaluation mode. To avoid this problem, a new setting has been added to the 'General settings | General options' screen: if Hauptwerk has previously been launched at least once with a licence key dongle attached to the computer, but the dongle is not found when you subsequently launch Hauptwerk, it will now wait for the time specified by 'Maximum time to wait for licence key dongle on start-up (seconds)' before starting in evaluation mode. This is mainly useful if you have Hauptwerk configured to start automatically when your computer starts. You can set value to 0 if you wish to disable the delay entirely. However, the delay has no effect if the dongle is found immediately, thus no unnecessary delay should be introduced when starting Hauptwerk.
Product version introduced: 02.20
Product version fixed in: 03.00
HW-000485: Component installer: progress indicator re-started repeatedly when installing sample sets above 2 GB in size.
For component packages (sample sets) larger than 2 GB, during the initial phase of reading/preparing the data, the progress indicator displayed by Hauptwerk's component installer could scan from 0 to 100 percent repeatedly, rather than displaying the true progress values. This had no functional impact, in that the component installer would still process such packages correctly. The progress indicator now displays the correct values with component packages of any size.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000487: Small brief crackle/audio glitch could be heard when minimising the main Hauptwerk window (Windows only).
If Windows virtual memory was enabled, minimising the main Hauptwerk window whilst pipes were sounding could cause a small audio glitch or crackle because Windows would automatically move all of Hauptwerk's data to its disk cache ('page file'). Hauptwerk now locks all of its data into physical memory on Windows (as it previously did on Mac OS X), so this problem can no longer occur provided that you are logged onto your computer with an operating system user account that has administrator privileges, such as the default Windows account. Please see ENHANCEMENT HW-000483 for more details. As described there, we now recommend keeping Windows virtual memory enabled.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000490: If Steinberg's emulated 'ASIO DirectX' or 'ASIO Multimedia' drivers were corrupted Hauptwerk would not launch (Windows only).
Most Steinberg products, such as Cubase, Cubasis and V-STack, install two emulated drivers named 'ASIO DirectX Full Duplex Driver' and 'ASIO Multimedia Driver'. Those drivers maintain databases of other Windows drivers and provide an emulated ASIO interface to them. They do not give good performance with Hauptwerk, and their driver databases frequently become corrupted if audio interfaces or drivers are added or removed. It is possible to identify whether the drivers have become corrupted by trying to open the 'ASIO DirectX Full Duplex Setup' or 'ASIO Multimedia Setup' utilities found in the Start menu program group for your Steinberg application(s). If one of the drivers has become corrupted, its corresponding Steinberg set-up utility will crash or fail to open. Hauptwerk queries installed drivers when it launches. If a driver crashes or freezes when queried, that can cause Hauptwerk itself to crash or freeze. Since those particular drivers frequently became corrupted and crashed, causing Hauptwerk to crash on launch, and since those drivers are not relevant to Hauptwerk anyway, Hauptwerk now explicitly ignores those two drivers when querying the installed audio drivers. Thus it should no longer affect Hauptwerk if the Steinberg emulated drivers become corrupted.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000491: Transposer could leave keys stuck if transposition changed whilst holding keys.
If a chord was held whilst the transposition was changed, the keys that were previously pressed could incorrectly remain pressed. Keys are now correctly released when changing the transposition.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000502: LCD status display panel text was misaligned if organ short name was less than sixteen characters in length (Advanced Edition only).
The Hauptwerk Advanced Edition has the ability to drive an LCD display panel to show Hauptwerk's status, including an abbreviated form of the name of the organ loaded. If the abbreviated name was less than sixteen characters in length, the alignment of the other information on the display was not correct on the LCD panel. Hauptwerk now pads the abbreviated name automatically with spaces as necessary.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000517: Switching the dongle attached to a given computer gave confusing message when re-loading a sample set for the first time.
For customers and re-sellers that have multiple licences for Hauptwerk, and thus have several USB licence key dongles, changing the dongle attached to a given computer could give a confusing error message about the sample cache being invalid the first time that each sample set was re-loaded unless the sample cache was explicitly re-generated by loading the sample set with 'Organ | Load organ, adjusting rank audio output routing'. Acknowledging the message and then re-loading would allow the organ to load correctly. Hauptwerk now automatically detects whether the sample cache was saved with a different dongle attached and re-generates the caches transparently when necessary.
Product version introduced: 02.10
Product version fixed in: 03.00
HW-000518: Audio output device channel names sometimes showed incorrectly if configured for multiple audio devices at once (Mac OS X only).
If Hauptwerk was configured to use multiple audio device drivers (separate physical audio devices) simultaneously for multi-channel audio on Mac OS X then the device channel names on 'General settings | Audio outputs' could sometimes be shown with an incorrect value, although the correct channel would still be used. The device channels now always show the correct selected value.
Product version introduced: 02.20
Product version fixed in: 03.00
HW-000530: If Hauptwerk was closed during activation then configuration settings changes could be reverted.
Hauptwerk saves its general configuration settings when it closes. If Hauptwerk was closed, or if the computer was shut down, at exactly the moment that an organ had finished loading and the audio and MIDI systems were being started, then invalid values could be saved to its configuration file. The effect of this was that Hauptwerk would detect that the settings file was corrupted when it was next started and automatically revert the settings from a backup of the configuration file from the last point in time at which it had been loaded successfully. Hence any settings changes made in the previous session could be lost. It has now been changed so that activation of the audio and MIDI systems is allowed to complete safely before any shut-down request is processed, ensuring that the settings are written correctly in this (unusual) case.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000534: [Sample set developers only] If multiple mono attack and release samples were used at the same time for a given pipe extreme distortion could occur.
When loading into memory the sample data was becoming corrupted in this case (only), causing strange sounds and distortion. This did not affect any publicly-available sample sets and has now been rectified.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000551: When deactivating/unloading organ LCD panel text was not cleared (Advanced Edition only).
The Hauptwerk Advanced Edition has the ability to drive LCD display panels to show the names of draw-knobs and other virtual controls alongside their associated MIDI draw-knobs/tab/pistons on MIDI consoles, with the correct values for each distinct sample set. It can also use a single additional LCD panel to show status information. When a sample set was unloaded or deactivated, the LCD panel text was not previously cleared, leaving misleading text displayed on the MIDI console. The LCD panels are now always cleared when a sample set is unloaded or audio/MIDI are deactivated.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000552: First registration frame in status bar showed as 000 but 001 on LCD status display panel.
The status bar at the bottom of the main Hauptwerk window displays the combination sequencer registration frame number. The value was previously displayed using numbering starting at 000 for the first frame, which was not consistent with the LCD status display panel (Advanced Edition only), numbered from 001. The status bar display has now been changed also to use numbering starting from 001, which is considered more user-friendly.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000553: During audio/MIDI activation/deactivation LCD panel messages were sent 4-5 times in a row (Advanced Edition only).
The Hauptwerk Advanced Edition has the ability to drive LCD display panels to show the names of draw-knobs and other virtual controls alongside their associated MIDI draw-knobs/tab/pistons on MIDI consoles, with the correct values for each distinct sample set. It can also use a single additional LCD panel to show status information. Previously when a sample set was loaded, unloaded or the audio/MIDI systems activated/deactivated, the text would be sent to all configured LCD panels 4-5 times in a row, potentially generating a large and unnecessary amount of MIDI traffic, which could cause problems with some MIDI interfaces with less buffering. Message text is now sent once only in each case.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000597: Ctrl/Alt+Y menu short-cut was duplicated between re-directable routes and original organ tuning.
This has been addressed as part of BUG HW-000606.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000606: Various menu short-cut key combinations re-assigned since some short-cuts weren't working on OS X.
Some of the key combinations previously assigned to menu items weren't working under OS X because they had special reserved functions within OS X itself. To address this, menu short-cuts are now triggered by using both the Control and Alt keys on OS X, rather than just the Alt key. For example Control + Alt + F1 loads the first stand-by organ. On a Windows PC the Ctrl key is used in combination with the short-cut key as before. It has also been necessary to re-assign various menu short-cuts to ensure consistency between OS X and Windows whilst avoiding reserved key combinations on both platforms. Hence please check the menu short-cut key combinations again if you used them with previous versions.
Product version introduced: 02.20
Product version fixed in: 03.00
HW-000607: Stand-by menu entries weren't appearing to be updated when 'set stand-by' sub-menus were used for assignment.
The stand-by entries on various menus provide convenient short-cuts to load particular organs, temperaments or combinations. The 'set stand-by' sub-menus provide options to assign currently-loaded items to those stand-by entries. However, assigning items with those sub-menus did not always cause the text of the main menus to be refreshed, so sometimes it would appear that the assignment had not worked. The menus now refresh correctly.
Product version introduced: 02.20
Product version fixed in: 03.00
HW-000608: Some entries on the Temperaments menu were not showing as disabled on OS X at times that they should have been (Mac OS X only).
The menu items are now shown in their correct states at all times.
Product version introduced: 02.20
Product version fixed in: 03.00
HW-000612: Was possible to cause a crash by triggering two system functions at exactly the same time (e.g. one via the menu and another with a keyboard shortcut).
A system function can now only be triggered once any previous system function has completed.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000614: Settings screen layouts could be incorrect if user had customised Windows default font size (Windows only).
Windows has a setting that allows the user to customise its default font size. If a custom value other than the two defaults of 96 DPI and 120 DPI was chosen, then the layout of Hauptwerk's settings screens could make some settings illegible. Hauptwerk now ignores font size settings above 120 DPI to ensure the screens remain legible whatever Windows font size has been selected.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000617: Voicing: swell box harmonic content adjustment was not always select-able (Advanced Edition only).
The 'Swell boxes: harmonic content (dB)' setting on the per-pipe voicing screen sometimes did not appear in the list of adjustments when it should, preventing it being adjusted. It is now correctly available whenever the user has not be disabled swell box filters.
Product version introduced: 02.10
Product version fixed in: 03.00
HW-000622: Notes could hang if registration sequencer frame was advanced/decremented rapidly whilst playing.
The problem is now fixed.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000627: Invalid audio or MIDI drivers could cause Hauptwerk to crash on launch (Mac OS X only).
Hauptwerk queries the audio and MIDI devices available when it is launched. If a device driver returned an error code when queried, in some circumstances Hauptwerk could crash. Error codes being returned by device drivers are now handled correctly.
Product version introduced: 02.20
Product version fixed in: 03.00
HW-000629: Hauptwerk v1 import: re-importing a v1 organ with updated sample files could leave sample caches in invalid state.
Whenever a Hauptwerk version 1 sample set is imported, Hauptwerk's sample caches are invalidated to ensure that any changes to samples within a re-imported sample set are picked up correctly. Please note, however, that we don't recommend creating new sample sets in Hauptwerk version 1 format.
Product version introduced: 02.10
Product version fixed in: 03.00
HW-000632: VSTi: unloading Hauptwerk VST plug-in whilst loading organ or installing sample set could cause crash/freeze.
Unloading the Hauptwerk VST plug-in by removing it from the VST host's current project or by closing the VST host's project whilst Hauptwerk was loading an organ or installing a sample set could previously cause the host to crash or freeze. This has now been corrected. Please note, however, that some hosts (notably Cakewalk Sonar) can still crash or freeze if you attempt to close the host application whilst the Hauptwerk plug-in is loading an organ or installing a sample set, without cancelling the action in Hauptwerk first. We have not found a way around that at this stage (see BUG HW-000636).
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000635: Installer: performing custom installation to root of hard-drive prevented organ information displaying and component installer patching (Windows only).
If the root of a hard-drive was selected as the destination for a custom installation in Hauptwerk's installer, then 'Organ | Show organ information ...' might not work or might cause a crash. The component installer might also not be unable to apply sample set patches. The installer has now been changed to handle installation to the root of a hard-drive correctly.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000637: Excessively high audio output level causing severe clipping could crash some audio drivers (Windows only).
Having Hauptwerk's audio output level set so high that extreme distortion ('clipping') occurred could crash some Windows audio drivers, such as the M-Audio ASIO driver. Hauptwerk now explicitly clips the signal before sending it to the driver to guard against such problems.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000653: CODM: example organ 1 had slightly misleading setting for Samples_SampleMIDINoteNumOfLastAvailableSample.
For the 56-pipe manual ranks in the Custom Organ Design Module example organ 1 the Rank.Samples_SampleMIDINoteNumOfLastAvailableSample setting was set to 92, rather than the expected 91. This did not make any functional difference in this case since the value only defines the range of samples available.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000670: Was possible under certain circumstances to load an organ when audio configuration was invalid, causing crash or strange audio routing.
If Hauptwerk's user audio configuration settings are invalid, for example if no audio outputs have been included in a given audio output group, then Hauptwerk displays a warning message and disables most of the menu items until that invalid configuration has been corrected by the user. However, there were some circumstances under which it was still possible to load an organ, which could cause a crash whilst the organ loaded and/or strange audio routing could be heard. Hauptwerk now correctly prevents an organ being loaded if the user audio configuration is invalid.
Product version introduced: 02.00
Product version fixed in: 03.00
HW-000686: Documentation: some custom coupler codes were incorrect in CODM user guide.
Version 1.05 of the Custom Organ Design Module user guide listed some incorrect values for the custom coupler codes.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000689: Distortion/crackle in recorded output with some DirectSound drivers (Windows only).
When using Hauptwerk's built-in audio recording system with some Windows DirectSound drivers (notably Creative sound cards), distortion/crackle could occur in the recorded output.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000691: 'Out of memory' errors when Nero CD/DVD writer running at the same time as Hauptwerk (Windows only).
The third-party Nero packet CD/DVD-writing software reserves large amounts of the computer's physical memory when running. Hauptwerk version 3.00 also reserved/locked its sample memory to prevent potential audio glitches (caused by Windows moving its sample date temporarily to its disk 'page file'). If Nero software (or another application that behaved similarly, although no others are known presently) was running at the same time as Hauptwerk then Hauptwerk might be able to use less memory than expected because some of the computer's memory would already have been reserved/locked by Nero. To avoid this issue (and also because of significant compatibility issues with certain drivers - see BUG HW-000692), Hauptwerk version 3.10 and later no longer locks or reserves its memory. Please see BUG HW-000692 and ENHANCEMENT HW-000853 for more details.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000692: Freezes, crashes, very slow loading or no sound under 64-bit Windows with certain drivers when 4 GB or more of memory installed or if Windows page file disabled (Windows only).
By default Hauptwerk version 3.00 locked its sample data into physical memory on Windows in order to guard against audio glitches that could otherwise be caused by data being cached to the operating system's disk page file. However, some 64-bit drivers seem not to be fully 64-bit throughout, but instead to use some 32-bit components internally (most notably E-MU's drivers, although some motherboard, graphics card or other drivers might work in that way), which could cause Windows or Hauptwerk to freeze, crash, run extremely slowly, produce no audio output, or cause other strange effects if 4 GB or more of memory was reserved/locked by Hauptwerk, or if Windows page' file had been disabled. We believe that these problems could occur because those drivers with 32-bit components only work properly in certain portions of the memory (the 32-bit address space) and could cause severe malfunctions if another application such as Hauptwerk had reserved/locked most of that memory for its use or if Windows page file was disabled, preventing any application memory being swapped out to disk from that portion of the memory if a 32-bit driver component needed it.
To avoid this (relatively widespread and severe) issue (and also because of compatibility issues with some other applications - see bug HW-000691), Hauptwerk version 3.10 and later no longer locks its sample data into physical memory on Windows platforms. Please see ENHANCEMENT HW-000853 for more details. Also because of these driver issues we strongly recommend not attempting to disable Windows' page file, especially if 4 GB or more of physical memory is installed, otherwise Hauptwerk, Windows or other applications might behave strangely, depending on the drivers and other software installed on the computer.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000693: Occasional errors writing to log file or crashes/freezes when loading/activating organ with many audio output channels (Mac OS X only).
On Apple Macs, if multi-channel audio output was configured and the number of audio channels multiplied by the number of CPU cores exceeded a certain value it was possible that error 'ERR-0604: Log file ...Log.Hauptwerk.xml could not be opened.' might sometimes be reported, or Hauptwerk might crash or freeze when loading an organ or activating the audio/MIDI interfaces. The problem occurred because all of OS X's internal file handles could become used up due to a bug in the multi-platform library Hauptwerk uses. This has now been worked around.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000694: Performance: some sample sets were slower to load in Hauptwerk v3.00 than in v2 when memory compression was enabled.
This issue has been fixed and there should now be very little difference in loading times regardless of whether compression memory is enabled. The new loading mechanism (HW-000676) also means that sample sets should load in a fraction of the time required by any previous Hauptwerk version.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000704: Log file incorrectly reported OS X version as above 10.5 when using OS X Tiger 10.4.9 (Mac OS X only).
All currently-available versions (up to 10.5.3 and 10.4.11) are now reportedly correctly in the log file.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000709: Documentation: minor error in default MIDI settings descriptions.
In the user guide the 'Couplers: div. 3 (Swell) to div. 4 (Choir) ...' entries had incorrect descriptions on the 'MIDI organ consoles' and 'MIDI input' pages.
Product version introduced: 02.00
Product version fixed in: 03.10
HW-000711: A stand-by or recently-used menu entry that no longer existed would cause an error to be reported.
Now Hauptwerk automatically and silently removes an entry from the stand-by or most recently-used lists on the menus if you select it but the component it refers to is no longer present (for example if a combination file has been deleted or an organ un-installed).
Product version introduced: 02.00
Product version fixed in: 03.10
HW-000713: CODM: example organ 2 Swell reeds not coupled to Great or Pedal.
The coupler behaviour has now been corrected in the Custom Organ Design Module 'example organ 2'.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000714: CODM: Ped Bass coupler was of incorrect type in example St. Anne's organ definitions.
The bass coupler did not behave correctly in the Custom Organ Design Module St. Anne's example organs.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000717: Cirumstances existed in which loading an organ or activating audio/MIDI were possible even if audio settings were invalid, causing crashes or other strange behaviour.
This mainly affected OS X, but was also possible in one particular situation on Windows. The main menu items (such as those to load an organ or activate audio/MIDI) now correctly remain disabled until the user's audio configuration settings are valid.
Product version introduced: 02.00
Product version fixed in: 03.10
HW-000723: Recent versions of Windows Media Player could crash if opening recorded output from Hauptwerk.
This only occurred with Windows Media Player and only if the recording resolution was set to 32-bit in Hauptwerk. It was due to a difference in the way that recent versions of Media Player interpret some data in 32-bit audio files. This has now been worked around.
Product version introduced: 02.00
Product version fixed in: 03.10
HW-000724: MIDI feedback could still cause freeze if using only virtual MIDI cable (e.g. MIDI Yoke) ports (Advanced Edition only).
Hauptwerk version 3.00 and above has a built-in MIDI feedback detection mechanism. However, a freeze could still sometimes occur via virtual MIDI cable software before Hauptwerk's MIDI feedback detection mechanism had had a chance to test for feedback. Hauptwerk now waits 100 milliseconds for the feedback detection mechanism to complete before allowing any other MIDI output to be sent.
Product version introduced: 02.00
Product version fixed in: 03.10
HW-000725: Performance: 'playing' polyphony could be slightly lower than with Hauptwerk v2 even though static polyphony was higher on PowerPC G4/G5 Macs (Mac OS X only).
It was found that the polyphony limit might need to be set slightly lower under version 3.00 than under version 2.21 on PowerPC G4/G5 Macs (only), even though the static polyphony in version 3.00 was higher. This has now been addressed.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000734: Component installer didn't give re-install/upgrade options if incorrect drive-letter/folder-name case was entered for installation locations when Hauptwerk was originally installed.
When installing Hauptwerk for the first time there are two installation type options: 'Simple' and 'Custom'. The Custom option allows you to enter/select the folders into which Hauptwerk is to be installed. When you originally installed Hauptwerk, if you selected the Custom option and you typed the folder names manually (rather than using the folder browse button) and you entered the folder-names or drive letter (Windows PCs) using the wrong case (for example, if you entered a lowercase drive letter), then Hauptwerk's component installer would not allow components (sample sets, organs, etc.) that had already been installed to be upgraded or re-installed. In such cases only 'Install' or '<none>' would be listed as possible actions even if a component was already installed. The component installer now considers installation paths to be case-insensitive.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000735: If organ loading was cancelled at first stage then menu functions could do nothing for a few seconds.
If the 'Cancel' button was clicked whilst a sample set was at the first stage of loading (reading the organ definition file), then the progress indicator window would close so it would be possible to access the menu functions. However, it could be a few seconds until the loading process was actually halted, during which time the menu functions would do nothing. The progress indicator window now remains on the screen until the process has been halted, correctly blocking access to the menus.
Product version introduced: 02.00
Product version fixed in: 03.10
HW-000737: Documentation: minor error in description of Switch MIDI inputs screen settings.
A sentence in the user guide confused the 'Event value' and 'Event number' settings in the description of the 'General settings | Switch (MIDI) inputs' screen.
Product version introduced: 02.00
Product version fixed in: 03.10
HW-000740: VSTi: VST hosts could freeze on some PCs when scanning unlicensed (evaluation) Hauptwerk VST plug-in or on low-spec computers (Windows only).
With some computers and VST hosts, displaying a message box on start-up could cause the VST host to freeze when scanning for installed VST plug-ins. Such a message would typically be displayed if Hauptwerk was running in evaluation mode (if no licence key dongle was attached) or if it was the first time that it had been run on a low-specification PC. Hauptwerk now avoids displaying any warning messages on start-up for this reason, but still logs the relevant information to its log file.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000747: OS X Leopard sometimes crashed (kernel panic) when starting firewire audio drivers (Mac OS X only).
This was due to a bug in OS X Leopard versions 10.5(.0) to 10.5.2 and was fixed by Apple in OS X Leopard 10.5.3. Since this is a serious bug in earlier versions of OS X that directly affects Hauptwerk, it is listed here for information. To avoid this problem we have made 10.5.3 the minimum required version of OS X Leopard (OS X 10.4 Tiger is still supported) and very strongly recommend applying all current OS X updates if you are using Leopard.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000754: Sample set developers: a version number comparison could fail incorrectly.
Hauptwerk could incorrectly report that a component's version was too low if its version and the minimum required version were set to certain values. This problem did not affect any existing sample sets.
Product version introduced: 02.00
Product version fixed in: 03.10
HW-000759: Transposer could still sometimes leave notes stuck if changing transposition whilst notes held.
Bug fix HW-000491 was included in Hauptwerk v3.00 to allow transposition to be changed whilst notes were held. However, that fix didn't always work reliably. It has now been fixed fully.
Product version introduced: 02.00
Product version fixed in: 03.10
HW-000762: One pipe sample wasn't working properly in Sonus Paradisi St Maximin sample set.
The bottom 'A' pipe on the G.O. Trumpet 8 sometimes didn't speak properly in version 3.00.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000788: Voicing screen could cause crash if all ranks were disabled (Advanced Edition only).
If no ranks at all had been loaded into memory then opening the voicing screen would cause a crash.
Product version introduced: 02.10
Product version fixed in: 03.10
HW-000798: Sample set developers: occasional crash was possible if loading several organs from a MySQL database without closing Hauptwerk in-between.
A MySQL session parameter was not always being reset between connections.
Product version introduced: 02.00
Product version fixed in: 03.10
HW-000806: Key action noises were not working properly with some sample sets in v3.00.
In Hauptwerk version 3.00 the key release action noises would sound too quietly (or be completely inaudible) with some sample sets because automatic release sample amplitude modulation was being applied when it should not have been.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000809: Component installer: might not be able to upgrade or uninstall sample set if hidden/system files present.
If a user had extracted a sample set manually (using WinRAR or similar), rather than installing it via Hauptwerk's native component installer, then any operating system hidden/system/read-only files that were present in the component package file would also have been extracted (such as Windows Thumbs.db, Desktop.ini or Mac OS X .DS_Store files). If the sample set had been installed with Hauptwerk's component installer then those files would intentionally and correctly have been skipped. Using Windows Explorer or OS X's Finder to browse a sample set's folder structure subsequently could also create such files. If such files were present then attempting to uninstall, upgrade or reinstall the sample set using Hauptwerk's component installer could fail. The component installer has now been made resilient to the presence of such files for all operations.
Product version introduced: 02.00
Product version fixed in: 03.10
HW-000814: Status bar 'redirectable' indicator text wrong when organ loaded.
In version 3.00 both re-directables were incorrectly labelled as 'Redir 1:' in the status bar when a sample set was loaded.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000830: Sample set developers: hidden/OS files in component installer packages could give error.
If a sample set package contained non-Hauptwerk files in certain locations (for example hidden/OS files such as Windows Thumbs.db, Desktop.ini or Mac OS X .DS_Store files in the OrganDefinitions or Temperaments folders) then Hauptwerk's component installer would give an error when trying to install it. The component installer now specifically skips unexpected files in a component installer package.
Product version introduced: 02.00
Product version fixed in: 03.10
HW-000840: Some keys connected incorrectly with Sygsoft Eenum and Krewerd sample sets.
The Sygsoft Eenum and Krewerd sample sets internally have key and division nodes specified both manually and for generation for the same nodes. Although that would not normally be beneficial, Hauptwerk version 2 was tolerant to the situation, whereas version 3.00 gave priority to the generated nodes, meaning that some of the bottom-octave keys in the 'original' views in those sample sets did not sound. Version 3.10 has been changed so that any manually-specified nodes are given preference in cases where a given node/key is specified twice within a sample set.
Product version introduced: 03.00
Product version fixed in: 03.10
HW-000850: Component installer: if loading organ, cancelling then uninstalling component installer could give 'cannot remove folder' error.
This could happen because the working directory could still be set to the sample set's package folder.
Product version introduced: 02.00
Product version fixed in: 03.10
HW-000863: Installer: desktop icons sometimes didn't work properly after upgrading Hauptwerk on OS X Tiger until computer rebooted (Mac OS X only).
The desktop icons are sometimes not refreshed properly until OS X 10.4 ('Tiger') has been rebooted after upgrading Hauptwerk via the installer. The upgrade instructions now specifically recommend rebooting after upgrading on OS X Tiger (only). This should not be necessary on OS X 10.5 ('Leopard').
Product version introduced: 02.20
Product version fixed in: 03.11
HW-000865: Documentation: installation/upgrade instructions were slightly ambiguous regarding Windows page file recommendations (Windows only).
It is very strongly recommended that the Windows page file should be left set specifically to 'system managed size' (which is the default for a new Windows installation). This has been clarified in the installation/upgrade instructions in the user guide. An incorrect page file size can cause severe operating system, driver or application stability or performance issues, especially with 64-bit Windows, even if the amount of memory being used by Hauptwerk is less than the amount of free physical memory (as it should be).
Product version introduced: 03.10
Product version fixed in: 03.11
HW-000866: Audio distortion or crash was possible if notes sustained after first time (only) that some Sonus Paradisi sample sets had been loaded.
The first time that Hauptwerk loads a sample set (or after Hauptwerk has been upgraded, or if you change any audio routing settings), Hauptwerk will re-generate its sample set data cache for that sample set. Subsequent times that you load the sample set it will instead load from the cached version (which is much faster). After regenerating a sample set data cache it had been found that sustaining long notes could cause sudden and severe audio distortion and/or a crash with certain recent Sonus Paradisi sample sets, notably the Sonus Paradisi Forcalquier, Prague Baroque and Zwolle sample sets. Specifically, the problem could occur if the default release sample for a pipe was stored in a separate file to the default attack sample. (The bug has existed since Hauptwerk version 2.00 but had only become apparent recently since until recently no sample sets had been created that contained samples formatted in that specific way. The problem was also more likely to be noticed in version 3.10 because memory is reused more aggressively internally due to the loading speed improvements in version 3.10 and above.)
Product version introduced: 02.00
Product version fixed in: 03.11
HW-000867: Errors 4669 or 4664 could be incorrectly reported when loading certain sample sets.
Error 4669 ("... this sample object is configured to read the pitch from the sample file, but the sampler chunk in the file does not contain a valid pitch.") or 4664 ("... the specified loop range does not exist within the file.") might have been reported incorrectly when loading certain sample sets. The problem had mainly been reported on 32-bit Windows platforms with the Sonus Paradisi Litomysl Dry sample set, the Sygsoft Boezemkerk sample set and some user-created organ definitions generated with the Oberwerk software that use samples that are not part of Oberwerk's native sample set. It was possible but much less likely to occur on 64-bit Windows or Mac OS X or with other sample sets. (The bug had existed since Hauptwerk version 2.10 but was more likely to be seen in version 3.10 because memory is reused more aggressively internally due to the loading speed improvements in version 3.10 and above.)
Product version introduced: 02.10
Product version fixed in: 03.11
HW-000869: Documentation: some stop codes and custom coupler codes were incorrect in CODM user guide.
A stop code range was incorrect for one division. Some of the custom coupler codes were also listed incorrectly.
Product version introduced: 02.00
Product version fixed in: 03.11
HW-000871: Error 4403 occasionally incorrectly reported when loading sample sets on single-core computers.
The first time that Hauptwerk loads a sample set (or after Hauptwerk has been upgraded, or if you change any audio routing settings), Hauptwerk will re-generate its sample set data cache for that sample set. Subsequent times that you load the sample set it will instead load from the cached version (which is much faster). Error 4403 ("Could not load an image file from the sample set data cache. Please try re-loading the sample set so that the cache is regenerated (which might be slow).") could occasionally and incorrectly be reported when loading sample sets from their caches on single-core computers (only) unless the high-speed sample set loading mechanism was disabled. This has now been fixed so it is safe to enable the high-speed loading mechanism again if you previously disabled it as a work-around for this problem.
Product version introduced: 03.10
Product version fixed in: 03.11
HW-000872: Tuning randomisation model was not being bypassed in 'original organ pitch' mode.
Hauptwerk's tuning randomisation model is designed to model the slight drift in tuning between pipes that occurs naturally in real pipe organs, imparting movement to the sound. However, the model should only apply when a temperament other than 'original organ tuning' is selected. Previously it was also incorrectly being applied in 'original organ tuning' mode.
Product version introduced: 02.00
Product version fixed in: 03.11
|
|
|
