Concerning Windows 7 Pro:
Operating a Windows system for Hauptwerk has caused me to thrash around for solutions to various system issues, including audio glitches. I recorded some of my experience in a previous thread, http://forum.hauptwerk.com/viewtopic.php?f=16&t=12407, which began with Windows “Tablet” issues but concluded with my learning from Jan Loosman of the contribution of the Superfetch service to audio glitches. I now keep Superfetch (aka “stupidfetch” online) set to “Automatic,” but I “Stop” the service as a part of starting Hauptwerk. I have also reset some other services (particularly those that automatically call up internet or even some local activities) to “Manual” or “Disabled” – my Hauptwerk computer is almost never connected to the internet.
The present contribution refines the earlier one. I had no audio problems with my first (NEC) touch monitors prior to the last driver update that I downloaded for their 3M touchscreens. This last 3M driver accessed, for the first time, the Windows HID (Human Interface Device) software. This new utilization of HID released HIDeous storms of audio glitches upon touchscreen use. The obvious and fully successful remedy was to revert to the previous 3M touchscreen driver.
This year (2015) I upgraded my touchscreens to a pair of ēlo monitors which provide tremendous improvements both in touch accuracy (perfection beyond edge-to-edge, no front bezel) and in display clarity (all glass). However, under Windows these ēlo touch devices are strictly HID. This meant that using the new touchscreens in full mouse emulation mode again caused paroxysms of activity in the Hauptwerk CPU meter and hailstorms of glitches in the audio. Using the ēlo monitors in a single-touch mode eliminated the audio glitches, but it also meant that I could no longer swipe multiple stops on a Hauptwerk stop jamb or move a scrollbar or panel with my finger on the screen.
I have finally had the time to research and experiment, and this (not in historical order) is what I have learned concerning wisptis.exe.
1. Full name: Windows Ink Services Platform Table Input Subsystem. wisptis.exe is a subcomponent of Windows HID.
2. wisptis.exe is universally understood to be “CPU intensive.” This is one reason it is controversial. Opinions range from the formally correct, “It is in no way a virus,” to my favorite:
“Resource hog, bad design. Let's start calling these things what they are; I didn't ask for it to be installed, it is detrimental to my system and nothing I want on my system requires it to run. It's a virus. I don't care that it comes from a company. I should be given the option to remove it easily or to not install it in the first place.”
3. As implied in the preceding quote, wisptis.exe cannot be uninstalled; it would be automatically reinstalled, anyway (apparently by/for Windows, MS Office, or Adobe). I doubt that older online recipes for removing wisptis.exe are still valid.
4. I did find a method to deny permission to wisptis.exe, effectively eliminating it. Since this method was reversible, I tried it. In the absence of wisptis.exe activity, the computer no longer responded to touchscreen activation at all, although the mouse and keyboard worked normally. This was not an answer I could use.
5. By accessing the wisptis.exe process in the Task Manager window, I changed the Priority level for each of the two wisptis.exe instances from “High” (default) to “Low,” which is the lowest possible setting. MAKING THIS CHANGE DID ELIMINATE THE CPU OVERBURDEN AND AUDIO GLITCHES CAUSED BY wisptis.exe WITHOUT ADVERSELY AFFECTING TOUCHSCREEN USE. This was the answer I needed: I can now use the ēlo monitors in full mouse emulation mode. By the way, when running Windows in 64-bit, the Task Manager shows two instances of wisptis.exe processes, one designated SYSTEM and one for a user account, and the Priority setting needs to be changed for each of them.
6. Changing the Priority for wisptis.exe as described above does not change its default Priority setting. In an attempt to essentially change the default, I installed a free utility called Prio which acts as a “Task Manager enhancement.” I CANNOT RECOMMEND THIS “ENHANCEMENT.” (i) I found that although Prio could remember and automatically modify the Priority setting for some processes upon startup, it was not able/permitted to do so for wisptis.exe. (ii) During the brief time I left Prio in my system, I repeatedly experienced an odd circumstance in which, during abnormally decelerating sample set loads, a message suddenly appeared that indicated that the cache file (which had been in use) was deemed “present” but “cannot be found.” [Finally: a state of machine memory with which I can commiserate.] Furthermore, while attempting to rebuild a thus-damaged cache, a wav file was described by the system in the same way. After immediately uninstalling Prio (using its own uninstaller), I was able to rebuild the damaged caches without incident and without needing to reinstall anything. I believe that everything is back to normal.
And that normal is now as follows. At the beginning of each Hauptwerk session, I need to take a few moments to do the following (not in any specific order) to defeat audio glitches:
---- Stop the Superfetch service
---- Set the Priority for each wisptis.exe process instance to “Low”
---- Put Norton 360 (admittedly my choice for security) in “Silent” mode (stops background activities)
Codicil:
Not unlike Marco reported under http://forum.hauptwerk.com/viewtopic.php?f=16&t=14069,
I have recently experienced a single, isolated audio glitch 20 minutes or so after at least some startups. As I recall, this pattern began a couple of monthly patches ago. I have not found evidence of the offending activity in the Event Viewer, though looking for it has led me to trim some other unnecessary activities.
Now what will Windows 10 bring???
Operating a Windows system for Hauptwerk has caused me to thrash around for solutions to various system issues, including audio glitches. I recorded some of my experience in a previous thread, http://forum.hauptwerk.com/viewtopic.php?f=16&t=12407, which began with Windows “Tablet” issues but concluded with my learning from Jan Loosman of the contribution of the Superfetch service to audio glitches. I now keep Superfetch (aka “stupidfetch” online) set to “Automatic,” but I “Stop” the service as a part of starting Hauptwerk. I have also reset some other services (particularly those that automatically call up internet or even some local activities) to “Manual” or “Disabled” – my Hauptwerk computer is almost never connected to the internet.
The present contribution refines the earlier one. I had no audio problems with my first (NEC) touch monitors prior to the last driver update that I downloaded for their 3M touchscreens. This last 3M driver accessed, for the first time, the Windows HID (Human Interface Device) software. This new utilization of HID released HIDeous storms of audio glitches upon touchscreen use. The obvious and fully successful remedy was to revert to the previous 3M touchscreen driver.
This year (2015) I upgraded my touchscreens to a pair of ēlo monitors which provide tremendous improvements both in touch accuracy (perfection beyond edge-to-edge, no front bezel) and in display clarity (all glass). However, under Windows these ēlo touch devices are strictly HID. This meant that using the new touchscreens in full mouse emulation mode again caused paroxysms of activity in the Hauptwerk CPU meter and hailstorms of glitches in the audio. Using the ēlo monitors in a single-touch mode eliminated the audio glitches, but it also meant that I could no longer swipe multiple stops on a Hauptwerk stop jamb or move a scrollbar or panel with my finger on the screen.
I have finally had the time to research and experiment, and this (not in historical order) is what I have learned concerning wisptis.exe.
1. Full name: Windows Ink Services Platform Table Input Subsystem. wisptis.exe is a subcomponent of Windows HID.
2. wisptis.exe is universally understood to be “CPU intensive.” This is one reason it is controversial. Opinions range from the formally correct, “It is in no way a virus,” to my favorite:
“Resource hog, bad design. Let's start calling these things what they are; I didn't ask for it to be installed, it is detrimental to my system and nothing I want on my system requires it to run. It's a virus. I don't care that it comes from a company. I should be given the option to remove it easily or to not install it in the first place.”
3. As implied in the preceding quote, wisptis.exe cannot be uninstalled; it would be automatically reinstalled, anyway (apparently by/for Windows, MS Office, or Adobe). I doubt that older online recipes for removing wisptis.exe are still valid.
4. I did find a method to deny permission to wisptis.exe, effectively eliminating it. Since this method was reversible, I tried it. In the absence of wisptis.exe activity, the computer no longer responded to touchscreen activation at all, although the mouse and keyboard worked normally. This was not an answer I could use.
5. By accessing the wisptis.exe process in the Task Manager window, I changed the Priority level for each of the two wisptis.exe instances from “High” (default) to “Low,” which is the lowest possible setting. MAKING THIS CHANGE DID ELIMINATE THE CPU OVERBURDEN AND AUDIO GLITCHES CAUSED BY wisptis.exe WITHOUT ADVERSELY AFFECTING TOUCHSCREEN USE. This was the answer I needed: I can now use the ēlo monitors in full mouse emulation mode. By the way, when running Windows in 64-bit, the Task Manager shows two instances of wisptis.exe processes, one designated SYSTEM and one for a user account, and the Priority setting needs to be changed for each of them.
6. Changing the Priority for wisptis.exe as described above does not change its default Priority setting. In an attempt to essentially change the default, I installed a free utility called Prio which acts as a “Task Manager enhancement.” I CANNOT RECOMMEND THIS “ENHANCEMENT.” (i) I found that although Prio could remember and automatically modify the Priority setting for some processes upon startup, it was not able/permitted to do so for wisptis.exe. (ii) During the brief time I left Prio in my system, I repeatedly experienced an odd circumstance in which, during abnormally decelerating sample set loads, a message suddenly appeared that indicated that the cache file (which had been in use) was deemed “present” but “cannot be found.” [Finally: a state of machine memory with which I can commiserate.] Furthermore, while attempting to rebuild a thus-damaged cache, a wav file was described by the system in the same way. After immediately uninstalling Prio (using its own uninstaller), I was able to rebuild the damaged caches without incident and without needing to reinstall anything. I believe that everything is back to normal.
And that normal is now as follows. At the beginning of each Hauptwerk session, I need to take a few moments to do the following (not in any specific order) to defeat audio glitches:
---- Stop the Superfetch service
---- Set the Priority for each wisptis.exe process instance to “Low”
---- Put Norton 360 (admittedly my choice for security) in “Silent” mode (stops background activities)
Codicil:
Not unlike Marco reported under http://forum.hauptwerk.com/viewtopic.php?f=16&t=14069,
I have recently experienced a single, isolated audio glitch 20 minutes or so after at least some startups. As I recall, this pattern began a couple of monthly patches ago. I have not found evidence of the offending activity in the Event Viewer, though looking for it has led me to trim some other unnecessary activities.
Now what will Windows 10 bring???
Don Vlazny