Rangecast FAQ
[FAQ-1290] INDEX - Hub Administration - Channels and reception of channels


Page Type: INDEX


OVERVIEW

Topics related to the effective recording of specific broadcast channels that may require special attention


REFERENCE


[FAQ-1256] Trunk system patch channels

Trunked systems can operate patches (temporarily connecting users across multiple talkgroups). Unlike normal communications, patches are not associated with any single specific talkgroup, so patch transmissions are not indexed to a specific channel in Rangecast. Instead, patches are associated with a pseudo-channel corresponding to the trunking broadcast tower carrying the patch. The channel ID format for patch traffic is like TL12345 where the number is a tower ID.




[FAQ-1259] Blocked Channels

If recordings on a single scanner from a broadcast channel consistently produce no meaningful audio content (defined as more than two-thirds of audio being silent, extremely loud such as digital data, or broken into recordings of nearly zero duration), the channel will be temporarily blocked from that scanner. If all scanners in a cluster independently determine that the channel meets these criteria, the channel may be temporarily excluded from Rangecast. Temporary blocks are cleared daily, but the block will be regularly restored for channels with consistently bad quality.




[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.



CITATIONS

INDEX


Images shown - [block]