New to SDRTrunk
413 views
Skip to first unread message
John Phillips
Mar 13, 2022, 9:35:44 PM3/13/22
to sdrtrunk
I'm up and running. v0.5.0-alpha6
How do I delete or turn off the talk groups I don't want?
I did create a Alias List with one and only one group, but SDRTrunk continues to grab every active group.
I did not import all Talk Groups and created the one I wanted. It does pick up this group.
Can't seem to find any conversations on this issue and the manual is for older versions.
Thanks!
John
rlm...@gmail.com
Mar 14, 2022, 12:32:22 AM3/14/22
to sdrtrunk
John, you didn't look far enough on the GitHub page. All of the answers to your questions are here: https://github.com/DSheirer/sdrtrunk/wiki/Playlist-Editor
Ron
Ron Webb
Mar 15, 2022, 1:41:17 PM3/15/22
to sdrtrunk
Provided you have the ability to import aliases from RadioReference, I would advise you to import ALL aliases and then mute all of the aliases you do not wish to hear. Another alternative, although not what I would suggest, is to create aliases that span a range you do not wish to listen to. For example, in the Sacramento (California) system, the highest talkgroup number is 35057. Say I wished to ONLY hear Sacramento Metro Fire, which has talkgroups between 3325 and 3441. I would create aliases for all of these talkgroups, so I'd know which talkgroup is talking but then I could create an alias that includes talkgroups 1-3324 and another alias that includes all talkgroups between 3442 and 35057. I would then mute all of the lower talkgroups and all of the higher talkgroups. As I stated though, this would not be my preferred method if I could help it. Thankfully, because I feed my audio to Broadcastify, I get a free premium account through RadioReference, which provides me with the ability to import all their data as needed for free.
Once you understand how the aliases work, you can use it for identifying units. For example, I monitor the City of Roseville (CA) and see that when it comes to radios, there are a plethora of individual radios... far too many to know each and every radio. I notice though that dispatcher consoles are all within a similar range of numbers. The dispatcher consoles vary by shift and I've even seen a number used by both police and fire during different times. While I don't know exactly how they assign their console numbers, I can at least attribute the traffic to a dispatcher as opposed to a police officer's mobile or portable or those from the fire service mobiles and portables. I created an alias that I just call "Dispatcher" where the Protocol= APCO-25 and the Radio ID range is between 9213000 and 9213020. On the primary fire dispatch talkgroup, the city also has a VHF frequency that is linked to it. The ambulance service does not have their trunked radios and neither do many of the mutual aid agencies from outside the city, but all fire and medical resources have access to conventional VHF. Whenever the traffic originates from the VHF side, the Radio ID is 256. Radio ID 256 is also used when the fire dispatcher hits the pre-alert tones, which is three beeps prior to their voice reporting the incident. Those beeps come from 256 and then their voice comes from a number between 9213000 and 9213020. Likewise, when there is a critical incident on the police primary, the dispatcher hits a button that transmits a beep every few seconds to remind all units to only transmit if their traffic is urgent and related to the incident. This beep every few seconds is also on Radio ID 256. I then created an alias I call "VHF or Tones". This comes in handy when looking at either the Broadcastify Calls or when recording these files for use with something like Trunking Recorder. If there is an incident, I scan the column that covers the "From" or "Source" and when I see "VHF or Tones" I can quickly find when something began, to catch up on the incident.
Once you understand how the aliases work, you can use it for identifying units. For example, I monitor the City of Roseville (CA) and see that when it comes to radios, there are a plethora of individual radios... far too many to know each and every radio. I notice though that dispatcher consoles are all within a similar range of numbers. The dispatcher consoles vary by shift and I've even seen a number used by both police and fire during different times. While I don't know exactly how they assign their console numbers, I can at least attribute the traffic to a dispatcher as opposed to a police officer's mobile or portable or those from the fire service mobiles and portables. I created an alias that I just call "Dispatcher" where the Protocol= APCO-25 and the Radio ID range is between 9213000 and 9213020. On the primary fire dispatch talkgroup, the city also has a VHF frequency that is linked to it. The ambulance service does not have their trunked radios and neither do many of the mutual aid agencies from outside the city, but all fire and medical resources have access to conventional VHF. Whenever the traffic originates from the VHF side, the Radio ID is 256. Radio ID 256 is also used when the fire dispatcher hits the pre-alert tones, which is three beeps prior to their voice reporting the incident. Those beeps come from 256 and then their voice comes from a number between 9213000 and 9213020. Likewise, when there is a critical incident on the police primary, the dispatcher hits a button that transmits a beep every few seconds to remind all units to only transmit if their traffic is urgent and related to the incident. This beep every few seconds is also on Radio ID 256. I then created an alias I call "VHF or Tones". This comes in handy when looking at either the Broadcastify Calls or when recording these files for use with something like Trunking Recorder. If there is an incident, I scan the column that covers the "From" or "Source" and when I see "VHF or Tones" I can quickly find when something began, to catch up on the incident.
On Sunday, March 13, 2022 at 6:35:44 PM UTC-7 jpoi...@gmail.com wrote:
Reply all
Reply to author
Forward
0 new messages