Rangecast FAQ
[FAQ-1235] Working with wanted channels that produce substantial debris (loud/quiet/brief transmissions)



If a substantial fraction of a channel's audio content is unusable (because the audio is extremely loud or quiet, or the transmissions are extremely brief), the radios automatically lock out that channel for the remainder of the day. This is to exclude channels that should be excluded, such as data traffic, birdies, etc. However, if such a channel is wanted for some reason, this FAQ describes methods for preventing lockout.


1) To prevent a channel from being locked out due to automatic detection of unusable audio (loud or quiet audio levels, or transmissions lasting less than a fraction of a second), on the Configuration screen, Special Settings, enter the command


... where CID is replaced with the CID (channel ID) of the channel that should be protected. If multiple channels should be protected, they may be specified together with a dash as a separation character, e.g.


2) If audio levels of recorded content seem peculiar, the PC may command a new sweep of audio ports, to check and see if Windows may have reassigned the audio ports to new IDs (this happens sometimes during operation.) If the radio is receiving channels with substantial periods of silence, this may mimic the appearance of such a problem, triggering frequent sweeps of audio ports. These may occupy the scanner and lower the quantity of traffic received. If you want to limit the frequency with which these port tests are retried, you can establish a limit on the Configuration screen, Special Settings, with a command like this:


... where the number is the minimum allowed interval in milliseconds between port retests. The value above corresponds to 24 hours. However, if this "recalinterval" feature is used, the PC will not promptly decect an actual problem with Windows reassigning port IDs while software is in operation, which may result in audio sometimes being passed through the Rangecast system where the recording is from the wrong radio.



Rangecast FAQ - ID 1235 - last updated 31 January 2019     Images shown - [block]