Thu Mar 28, 2019 12:12 pm
Here's the Support request I sent on 28 Feb:
"Hi Brett and Martin,
As you know there's a long-standing problem in HW4.2 with slow shutdown.
Here's an extract from my activity log included in the diagnostic file:
2019-02-27-08-09-58: INF:2509 Stopped audio and MIDI. Peak levels since last started: audio: -13.1 dB (>=0 dB indicates clipping), polyphony as pct of limit: 52.3, estimated audio CPU load: 71.6 pct. [Priorities: audio engines: 15, background models: 11, trem model: 11, wind supply model: 10, audio recorders: 15, MIDI player: --, MIDI recorder: 11, GUI rendering: 9, default user events: 10.] [Event buffer stats: (size in K-events, num floods, peak frac full pct, total traffic in K-events): GUI rendering: (64.0, 0, 0.00, 140.9), high-pri events: (8.0, 0, 0.00, 0.6), default user events: (8.0, 0, 0.00, 0.2).]
2019-02-27-08-10-26: INF:0403 Hauptwerk has finished shutting down. (USB key perf stats: min ms/avg ms/max ms: small accesses: '12.8 / 12.8 / 12.9', larger accesses: '0.0 / 0.0 / 0.0'.)
As you can see HW4.2 takes around 30 secs between stopping audio and MIDI and actually shutting down.
The problem has been discussed in the HW Forum and Martin indicated it was a Microsoft problem and suggested it might be fixed by April 2018. Since then there have been many Win10 updates but the problem remains.
Whilst waiting for a solution, I tried reverting to HW4. This shuts down immediately. It may be that HW4.2 uses a Win10 feature not used by HW4 or it may be a bug specific to HW4.2.
In any event I'd be grateful for a heads-up on the problem.
Best regards
Jon"
It's not a huge issue as I can shut HW down by closing its window. But the issue has been around for a long time so I thought it worth seeing if there's been any progress resolving the problem.