spyro
New Member
Posts: 25
|
Post by spyro on Dec 14, 2007 23:26:32 GMT
where are the options to disable/enable the watchdog?
I searched in the registry, and found this:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Watchdog
Is that the ASIO4ALL watchdog key?
thanks.
|
|
|
Post by Michael Tippach on Dec 15, 2007 0:35:15 GMT
where are the options to disable/enable the watchdog? I searched in the registry, and found this: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Watchdog Is that the ASIO4ALL watchdog key? Negative! Here's how to enable the ASIO4ALL Watchdog / Savemode: Go to "HKEY_CURRENT_USER\Software\ASIO4ALL v2 by Wuschel" There is a number of subkeys there, it may read like this: The "Defaults" entry will always be there, whereas the hex numbers vary in count and actual values. Each hex-numbered subkey represents the per-application setting for individual applications and there is no easy way to figure out which is which. Under each subkey, you have more subkeys which you are supposed to leave alone, but you also have one or two registry entries, named "Flags" and "SampleRate". If there _is_ a "Flags" key, delete it - except in the "Defaults" branch, where this key can now be used for global control of Watchdog / Savemode behavior. The "Flags" key has a double word format and bit 0 in that double word controls the Watchdog and bit 1 controls the Savemode feature. Setting either bit to "1" means the corresponding feature is enabled. Assume the value reads "0x00008000" you need to change it into "0x00008001" in order to enable the Watchdog, "0x00008002" for the Savemode feature and "0x00008003" for both. Guess I'm making this sticky for easy access by anyone looking for that information.
|
|
spyro
New Member
Posts: 25
|
Post by spyro on Dec 15, 2007 4:12:46 GMT
Ok, there was several branches with serials on them. All of them had "flags" inside. I deleted all of them (except of the flags in the defult branch) and now, when I open my sequencer the root branch has the key flags added again, but this time with 0x0000000 on it, meaning is disabled. the other folders didn't got any flags key again, which I assume is good. I just wanted to be sure the watchdog was disabeld. Thanks a lot for your help man really appreciated. 2.8beta 2 works really good with eveything I throw in it.
|
|
q
New Member
Posts: 2
|
Post by q on Apr 23, 2009 18:38:08 GMT
What is this watchdog key all about? Why the concern?
|
|
|
Post by Michael Tippach on Apr 23, 2009 21:59:15 GMT
What is this watchdog key all about? Why the concern? There is no actual reason for concern. There exists a watchdog feature that creates a low priority thread that itself does essentially nothing but record a time stamp of its last activation. This way, the audio thread - running at a rather high priority - can look at a this time stamp and, from that, it can detect a situation where audio processing takes close to 100% of the CPU. Which in turn would have rendered the system (nearly) completely unresponsive to user input. This increasingly has become a non-issue in times of multi core CPUs and the declining impact of the Netburst architecture FP denormal problem. Nothing to worry about, really.
|
|