Rangecast FAQ
[FAQ-1194] Error message: GARBLE (Code 20)

Page Type: SYMPTOM


"Garble" refers to an audio recording error where the Windows Audio recording process omits small sections of the original waveform, producing a recording that is slightly too short with random sections effectively snipped out. The effect is audio that appears garbled and perhaps overly loud (due to the abrupt shifts in waveform around the missing segments.) This is usually due to some errant process on the PC overloading the CPU.


When Garble is present, use Windows Task Manager and check for near-100% load on either the CPU or the disk. This overload may create a condition where the Windows audio system is unable to continuously record audio, resulting in garbled recordings.

If you see that CPU, memory usage, or disk access is near or at 100% loads, attempt to use Task Manager to determine what process or application on the computer is causing the problem. You may stop the Rangecast software to check that the problem persists even if Rangecast is not operating

[FAQ-1088] How to stop Rangecast software on a feed site PC (temporary stop, not decommission)

Rangecast software on a feed site PC includes a "watchdog" process that monitors for software faults, and may automatically relaunch the software if it is not closed correctly. The correct way to stop Rangecast is to click the Rangecast icon, and then press the Stop button.

Since Rangecast produces many temporary files, software that attempts to evaluate all new files may produce unacceptably high loads. This includes antivirus software, antimalware software, and the Windows search indexer. These are common culprits for CPU loads spiking to 100% on occasion, and disrupting Windows' ability to record realtime audio without interruptions (garble). In some cases, it is often not possible to determine what caused the problem, because the process driving the loads may be an internal component of Windows (e.g. "Host Process for Windows".) Especially if the culprit is an internal component of Windows, the problem will usually clear with a reboot of the PC. But some PCs show this problem on a chronic basis, so be aware that it may recur, especially if the cause appears to be antivirus software.

Task Manager can be started by right-clicking on an unused portion of the Windows taskbar, and selecting Task Manager from the context menu. Within Task Manager, you can click on a column heading to sort programs by their usage of that particular resource.

Here is a report showing CPU loads:

And a report showing 100% disk access loads. (This is NOT 100% disk full, but full loading of the data exchange communications path between the drive and the main computer. In this case, the problem was due to a hardware problem in the computer that reduced bandwidth between these components to an abormally low data rate.)

Less commonly, memory can also be a limiting factor, so also be aware of unusually high loads on the memory report in Task Manager. An example of a memory report:



Rangecast FAQ - ID 1194 - last updated 03 February 2019     Images shown - [block]