Some more steps to solve audio glitches

Hauptwerk software technical support only. Please make sure you have read the manual, tutorials and FAQ pages before requesting support.
Post Reply
HeAu
Member
Posts: 107
Joined: Sat May 21, 2005 1:33 pm

Some more steps to solve audio glitches

Post by HeAu »

I am running HW4 on a Windows10-Home-PC, first equipped with 16 GB RAM, and squeezed my favorite organ (Nagold) to fit into 16 GB RAM, leaving 1 GB free.
Output of HW is routed to Reaper - ASIO4ALL - Onboard sound.
Occassionally, approx. once per day, the CPU-indicator jumped into the red area, even when the organ was loaded but idle.

Of course I followed all recommendations by MDA and others to optimize the PC for HW.
The PC is used for Hauptwerk only and is never connected to the Internet, no antivirus installed, defender disabled, networking and bluetooth disabled.

After some researches I executed 3 steps, which finally made the PC glitchfree:
  • 1. I expanded the RAM from 16 GB to 32 GB and "de-squeezed" the organ, so now HW reports 10 GB free when the organ is loaded. The samples are still loaded in compressed mode. From then on highload-situations did happen less frequently, but were still present.
  • 2. I disabled the scheduled Windows task "Microsoft\Windows\SystemRestore\SR" in taskscheduler.
  • 3. I disabled the scheduled Windows task "Microsoft\Windows\UpdateOrchestrator\Report policies" (only visible when logged in as administrator). This step is a little bit tricky - see the lines below.
Since then (now for more then a month) not any jump into the read area of the CPU-indicator occured. HW shows now at most 6 green bars at the CPU-indicator during normal playing.
Surprisingly, Windows is now reporting updates every day as successfull und claims my system to be up to date, although it is still not connected to the Internet.
Until now I did not notice any negative impacts caused by these steps, the system is running stable as always. But I intend to execute the disabled tasks manually from time to time.

Additionally I disabled the Windows task "Microsoft\Windows\Defrag\ScheduledDefrag", of which I think to be obsolete on systems without HDD (as mine), but I suppose this task had and has no impact.

- How to disable "Microsoft\Windows\UpdateOrchestrator\Report policies":
  • Task scheduler refuses access to "Report policies" even when logged in as administrator. So I went the following workaround:
  • 1. I had to download the file PSTools.zip from Microsoft Webpage.
  • 2. I had to extract the file PsExec.exe from the downloaded zip-file to the folder C:\Windows\System32.
  • 3. I had to enable ethernet in systemcontrol - networking and internet - network connections" (this is called Systemsteuerung - Netzwerk und Internet - Netzwerkverbindungen in my German language system. Maybe the translation ist not fully correct)
  • 4. I opend a command window as administrator ("as admin" is important).
  • 5. I entered following two commands in the previously opend command window:
    psexec -S cmd
    schtasks /change /disable /tn "Microsoft\Windows\UpdateOrchestrator\Report policies"
  • 6. I closed the command window and again disabled ethernet.
  • 7. That's all. Now playing.....

PS:
Of course, I know, modifications of the Windows tasks are interventions to Windows. I am doing it on my own risk and have all my files backed up to an external hdd. One should only follow these steps if he knows what he does.

Rgds
Heau
User avatar
mdyde
Moderator
Posts: 15695
Joined: Fri Mar 14, 2003 1:19 pm

Re: Some more steps to solve audio glitches

Post by mdyde »

Thanks, Heau. Excellent.
Best regards, Martin.
Hauptwerk software designer/developer, Milan Digital Audio.
User avatar
vpo-organist
Member
Posts: 344
Joined: Wed Apr 29, 2020 6:49 am

Re: Some more steps to solve audio glitches

Post by vpo-organist »

Thanks for the tipps,
SystemRestore\SR was already disabled on my old Win10.
I don't have the Task UpdateOrchestrator\"Report policies" but two other Services was disabled. I disabled now all sub tasks.
The PC starts as usual.
Regards
Wolfgang
Post Reply