Tweet
"Watchdog timeout" error
I'm having a funny issue with an error that appears as "Watchdog timeout: possible CoreConverter crash."
I've created a CLI Encoder for Ogg Vorbis R1. My digital music player is picky about the vorbis bitrates it will accept, so I need to encode my music at a constant bitrate. When I enter the appropriate command lines and begin transcoding, everything appears to be going well, until about a minute passes, at which point dbpoweramp reports the following error:
"Error: Watchdog timeout, possible CoreConverter crash."
I go ahead and click "ok" and then "finish" on the converter window, and it looks as though the conversion has failed. However, task manager reports that CLI.exe is still working in the background, and several seconds later, the file is created. It has no playback problems and is encoded at the correct bitrate. What's even stranger is that if I eliminate the strings to create a constant bitrate file (and just use the "-q" switch") dbpoweramp converts the file without returning any errors.
I'm not sure, but it appears as though dbpoweramp "thinks" the CLI encoder is crashing because it takes a little longer to encode an ogg vorbis file at a constant bitrate than under the -q switch. Is there a way to shut off this "watchdog timeout" so I don't get what appears to be this false error?
I've created a CLI Encoder for Ogg Vorbis R1. My digital music player is picky about the vorbis bitrates it will accept, so I need to encode my music at a constant bitrate. When I enter the appropriate command lines and begin transcoding, everything appears to be going well, until about a minute passes, at which point dbpoweramp reports the following error:
"Error: Watchdog timeout, possible CoreConverter crash."
I go ahead and click "ok" and then "finish" on the converter window, and it looks as though the conversion has failed. However, task manager reports that CLI.exe is still working in the background, and several seconds later, the file is created. It has no playback problems and is encoded at the correct bitrate. What's even stranger is that if I eliminate the strings to create a constant bitrate file (and just use the "-q" switch") dbpoweramp converts the file without returning any errors.
I'm not sure, but it appears as though dbpoweramp "thinks" the CLI encoder is crashing because it takes a little longer to encode an ogg vorbis file at a constant bitrate than under the -q switch. Is there a way to shut off this "watchdog timeout" so I don't get what appears to be this false error?
Comment