Thanks, Andrew.
In Hauptwerk, on the '
General settings | Audio outputs' screen, first make sure that you have your audio interface's ASIO driver is selected (not DirectSound), and that you're using a reasonable buffer size (at least 256 frames).
If that doesn't solve it:
If Hauptwerk's audio-CPU meter (on the '
View | Large floating control panels | Audio, MIDI and performance' control panel) is going into, or nearly into, the red when few or no pipes are sounding then it indicates that the audio driver/host is calling Hauptwerk too late for Hauptwerk to have time to calculate the audio before the hardware needs to play it (i.e. resulting in a 'buffer under-run' and glitch), either because the audio driver isn't performing properly, or because the PC is having underlying hardware/driver timing issues (e.g. DPC latency). The following utilities should help to identify whether the latter is the issue, i.e. whether the PC and its drivers are performing sufficiently well to support real-time low-latency audio:
http://www.resplendence.com/latencymonhttp://www.thesycon.de/eng/latency_check.shtmlLeave each one of them running (but not both together, and without Task Manager being open) for half an hour or so whilst Hauptwerk is running with an organ loaded. The second of them, DPCLat might not be fully accurate on Windows 10, but it still seems broadly to work.
There are also some documents with detailed suggestions for troubleshooting PC audio problems here:
https://www.hauptwerk.com/clientuploads/documentation/Tutorials/WindowsOptimizationsAndDiagnostics.pdfhttps://www.cantabilesoftware.com/glitchfree/
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.