How do I stop SDRTrunk from recording the same transmission multiple times

[KD]

The department in my area often patches radio channels together, but not in the traditional method of patching, its set to the operator and cars will just broadcast the same over many talkgroups.

How do i stop SDRTrunk from recording every transmission (often up to 4 times) when I only want to monitor one talk group on a regular basis.

I only have one talkgroup set to listen and record, but Sdrtrunk will record the same conversation multiple times.

Setting Ignore duplicate call in the preferences doesn't work correctly, as SDRTrunk cannot decide which channel to record constantly (Like the note states in the settings) and will often record the TG I don't prefer.

Thanks,

[charley....@gmail.com]

I'm not quite understanding the issue, but you need to explicitly define each tg in your Alias list, and disable Record and Listen for each of those you don't want to hear or record.  They will still display in the Now Playing window.  If you want to hear those talk groups when they are not patched together, you will need to modify the Alias list to reflect the current operational situation.

[Steve Ries]

Try turning this on in the settings.
I think that will do what you need, to eliminate the issue.

Let us know if that resolves your problem.

[dave38...@gmail.com]

I'm not quite understanding the issue, but you need to explicitly define each tg in your Alias list, and disable Record and Listen for each of those you don't want to hear or record.  They will still display in the Now Playing window.  If you want to hear those talk groups when they are not patched together, you will need to modify the Alias list to reflect the current operational situation.

Try turning this on in the settings.
I think that will do what you need, to eliminate the issue.

Let us know if that resolves your problem.

I have both checked and I get duplicates. My system is linked to its old system via issi and uses patches. Duplicate tg detection and radio id detection does not work for me.

Still get thru and some times radio will only affiliate with either one tg, and not both, or one system and not the other. So selectively playing back thru TR is a pain.

[KD]

Sorry its a bit of a hard one to explain this issue.
The talkgroups I record are ingested into TrunkingRecorder for listening.

I have tested enabling the Radio ID duplicate call option but this did not work and here's why. (Per the warning/note)
As an example I have all talkgroups defined in SDRTrunk (tg; A, B, C, D) that are in my first photo.
I only want to record and listen to TG A, if I enable Radio ID duplicate detection
sometimes a radio call will come though but SDRTrunk will decide to record this call as TG B, not TG A.
Even though TG B doesn't have record set.

So this means in TrunkingRecorder when I have it set to view TG A only,
I'll miss calls as they are recorded by SDRTrunk as a different TG in this case TG B.


I guess my issue is SDRTrunk will record a TG that doesn't have the Record setting
set under the Alias because another TG that does have recording set carries the same radio traffic.

I hope this clears things up a little !

[charley....@gmail.com]

Can you provide screenshots of you Alias list(s) of the talk group configuration wrt this issue?  Also what specific systems and sites are you monitoring?

[charley....@gmail.com]

Expanding, I see three control channels being received.  Are any of these sites part of the same system or in any way related?  Your original screen shot cuts out this info.

[KD]

All sites are part of the same system yes.

The system isn't in the US.

What details do you want from the Alias configuration, there isn't much to it, one talk group is set to listen & record, the other is neither.

[KD]

I think some messages may have been deleted from this thread.

I've been looking at the Alias List, I've created a new list and built it fresh and the issue may have resolved itself.

I've looked at the data in the list and i can see a difference,

<alias name="BLACKLIST" color="-16777216" list="Trunking">
    <id type="priority" priority="-1"/>
    <id type="talkgroupRange" protocol="APCO25" min="1" max="65535"/>
  </alias>

<alias color="0" list="Trunking" name="BLACKLIST">
    <id type="priority" priority="-1"/>
    <id type="talkgroupRange" protocol="APCO25" min="1" max="65535"/>
  </alias>

Maybe this is causing an issue, As I've used the same list from early on SDRTrunk, over many version, there might be some corruption.

I'll have to rebuilt my whole list now to see if that might be the issue & report back.