You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the system I am listening to gets busy, I end up with a lot of what sounds like duplicate calls in my recordings. What's actually happening though, is when a call ends on the trunked system I'm listening to, it's assigning another talkgroup to the same frequency within the 1 second I have set in my config. Trunk-recorder continues the existing call as though it's the original talkgroup, but also spins up another recorder for the new call so the same conversation gets recorded twice.
On September 1st at 13:35 we had a working structure fire. A responding ambulance got into a pretty hefty accident and there was so much traffic that there were calls recorded as many as 3-5 times under various unrelated talkgroups. Recordings are available under the "Cache" OpenMHz feed.
This issue is ultimately locking all of my recorders (which I've seen all recording the same frequency at once in the past) so I'm missing other calls.
To me, It doesn't seem like TR is recognizing the change in TG ID's so it's not stopping the original recording when a new one starts on the same frequency.
I am listening to this system via the Logan Peak site.
To aid in troubleshooting we've already done in discord, this comment from tadscottsmith states:
There could be a flaw in the logic somewhere as well. On first glance it looks like the P25 since_last_write() logic might have been updated, where the analog recorder hasn't.
When the system I am listening to gets busy, I end up with a lot of what sounds like duplicate calls in my recordings. What's actually happening though, is when a call ends on the trunked system I'm listening to, it's assigning another talkgroup to the same frequency within the 1 second I have set in my config. Trunk-recorder continues the existing call as though it's the original talkgroup, but also spins up another recorder for the new call so the same conversation gets recorded twice.
On September 1st at 13:35 we had a working structure fire. A responding ambulance got into a pretty hefty accident and there was so much traffic that there were calls recorded as many as 3-5 times under various unrelated talkgroups. Recordings are available under the "Cache" OpenMHz feed.
This issue is ultimately locking all of my recorders (which I've seen all recording the same frequency at once in the past) so I'm missing other calls.
To me, It doesn't seem like TR is recognizing the change in TG ID's so it's not stopping the original recording when a new one starts on the same frequency.
I am listening to this system via the Logan Peak site.
My original config;
The text was updated successfully, but these errors were encountered: