Hello Chris,
I see that you sent the diagnostic file from my test build to us yesterday -- thanks for that. I've had a good look through it, and here are my notes (partly for my own reference, and for anybody else reading this thread):
----------------------------------------------------------------------------------------------------------------
- Your CPU is an AMD Ryzen Threadripper 2920X 12-Core Processor , AMD64 Family 23 Model 8 Stepping 2.
- The CPU has 12 physical cores, and 24 virtual cores, which Hauptwerk is correctly detecting and using.
- The CPU's base clock speed is 3.5 GHz (
https://www.amd.com/en/products/cpu/amd ... pper-2920x ), which Hauptwerk is correctly reporting in the log, and my test build showed that the actual CPU clock speed was indeed staying constantly at 3.5 GHz whilst you were running the test build, so that should be fine.
- Hauptwerk is normally using AVX2 on that CPU, which is fine (although the test build that I sent was optimised for AVX, which shouldn't cause a problem).
- The log shows that you have 128 MB of installed RAM, and with St. Anne's loaded nearly all of it is still free, so that's fine.
- The OS and Hauptwerk are installed on just one drive/SSD in the computer (drive C:), which has about 1.5 TB free, so that's fine.
- Your Windows account has Windows administrator rights, so that's fine.
- When you ran the test, the process priority was normal, which is fine.
- Windows is reporting its version as 10.0.19044, and I think 19044 is still the latest feature version, so I would expect that to be fine. (I'm actually still using 19043, since I'm a bit reluctant to apply the latest feature release yet in case it breaks anything on my development environment.)
- When you launched the test build, and at all times subsequently whilst you were running it, the log showed the process and system CPU affinities both as hex. 00ffffff, which is fine, and indicates that Windows is reporting that Hauptwerk is allowed to run on all of the CPU's 24 virtual cores, as expected.
- The log showed that whenever Hauptwerk asked Windows to a set the CPU core affinity for a thread it was doing so correctly, to the intended core, and with the correct CPU affinity mask for that core, and that Windows was reporting that the CPU affinity for the thread had been set successfully, so that's all fine too.
- You're using the MOTU Pro Audio ASIO driver, with a buffer size of 1024, 1 buffer, and at 48 kHz, so that's all fine too.
- The log showed that the thread priorities were correct, and that the background models were performing well.
- I do notice that for St. Anne's you're currently using mixer preset 2, for which you currently have 25 IR reverb instances assigned (with maximum lengths about 6s), so that will add a reasonable amount of constant CPU load. However, I tried loading St. Anne's using exactly your settings (which the diagnostic file contains), and even my laptop's 12-year old quad-core Intel i7 CPU running at 1.6 GHz can allows me to play St. Anne's easily with all stops and couplers drawn (with all of your 25 reverb instances), without Hauptwerk's audio-CPU meter going into the red, and without any CPU spikes. Also, opening Windows' CPU affinity dialogue box and OKing it makes no noticeable difference to the audio-CPU meter or performance on my system (using your settings, including all 25 reverb instances).
Hence your log from the test build showed no indication of anything unexpected -- everything appears to be fine within Hauptwerk, and based on what Windows is reporting to Hauptwerk.
----------------------------------------------------------------------------------------------------------------
Some questions:
----------------------------------------------------------------------------------------------------------------
- To confirm, when you tried my test build, did you still see the problem , i.e. was Hauptwerk's audio-CPU meter going into the red?
- Is the PC's drive activity still flashing constantly whilst audio/MIDI is active (e.g. with St. Anne's loaded)? (Hauptwerk won't be accessing the drive, so something else apart from Hauptwerk must be causing that, which might perhaps be relevant to the problem.)
- If, with St. Anne's loaded, you temporarily change the audio mixer preset to 5 (which I see has no reverbs applied currently), does Hauptwerk's audio-CPU meter still go into the red, and/or the drive light continue to flash? [You don't currently have any device channels selected on the mixer screen for mixer preset 5, so you won't hear anything, although within mixer preset 5's node you could also try selecting device channels 1+2 for master mix bus 1, so as to hear the audio.]
- Do you have a different (non-MOTU) audio interface available that you could try, just as a test, in case the problem is due to something strange within MOTU's driver on your (AMD-based) system?
----------------------------------------------------------------------------------------------------------------
Please also try:
- Open Windows Resource Monitor (which can be opened from the button at the bottom of the Performance tab in Task Manager), then click on Resource Monitor's 'CPU' tab.
- Load one of the polyphony testing organs and set the number of pipes per key to high-ish value. (Don't try to do anything with CPU affinity.)
- Play and hold a chord, so that lots of pipes are sounding at once, so as to be reasonably demanding on CPU/polyphony.
- In Resource Monitor, are core numbers 4-23 (the core numbering starts from 0) reasonably evenly loaded? (They should be, if Windows has indeed put Hauptwerk's audio engine threads on the cores that Hauptwerk requested, and for which my test build showed that Windows was reporting success when told to set their thread affinities.)
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.