Failing to Capture UIDs Again

[Dewey3]

Greetings! Since the issue in #674 was fixed, I have purposely not updated since the beginning of September. In order to not fall too far behind, I just updated to 4.5.0 last week. I must unfortunately report that this latest version has the return of the problem where the UIDs as displayed by Rdio-Scanner are failing to change during "rapid-fire" transmissions.

[Dewey3]

This is just a brief bump of the topic as the latest version, commit 6fcc7f67cf16ca1af949d2b8326fa99299ad24e5 (master) (2-7-2023) is still failing to capture the UIDs for the quick back-to-back transmissions. The last known working copy for me was the commit 10a276385124ef48e7ad6a3493236082c360ec0e (master) (9-15-2022) version. Is there anything I can do to assist in re-fixing this?

[rosecitytransit]

If it'll help, you can set verbosity=10 here to see raw P25 voice channel metadata which should include the src ID in use; it may be best to only do it with one recorder set as the data isn't tagged.

[Dewey3]

Thanks. Not sure if I quite understand what will happen here. I had the UID problem before and it was fixed back in August or September with the help of @tadscottsmith but newer releases seem to have broken it again. Unfortunately, I don't know where the break is occurring, but I do know that I don't see the same problem when decoding with Unitrunker or monitoring on the BCDx35HP or SDS series scanners.

[rosecitytransit]

Changing the setting and rebuilding will turn on a bunch of debug messages that show exactly what is being received in a voice call. Voice calls contain not only the actual voice but meta data like the talk group, unit ID and emergency/priority/etc flags about the call.

If you really wanted, I could possibly log in to your machine (or go over things together via Skype or whatever) and see what's happening.

[Dewey3]

That is how @tadscottsmith was able to help me out, I gave him an account to remote in and work with it how he needed. Are your saying the same, which is no problem, but it may be the weekend before I can setup the remote access?

[rosecitytransit]

That's fine, just let me know when you have time

[tadscottsmith]

That won't actually fix anything, it'll just spit out a bunch of logs.

@Dewey3 Just to confirm, you're seeing this issue again in v4.5.0 or later?

[Dewey3]

That won't actually fix anything, it'll just spit out a bunch of logs.

@Dewey3 Just to confirm, you're seeing this issue again in v4.5.0 or later?

@tadscottsmith : yes, the last version that worked for me was the 9/15/2022 release of v4.3.2. Since then, the UIDs are again being skipped on those quicker back-to-back-to-back-to-back transmissions. The latest version I've built is the 2/7/2023 release of v4.5.0, and it's still not catching the UIDs for the quick changing transmissions.

[rosecitytransit]

Correct that it won't change anything, but it'll help identify what's happening

…

On Mon, Mar 27, 2023, 12:58 PM tadscottsmith ***@***.***> wrote: That won't actually fix anything, it'll just spit out a bunch of logs. @Dewey3 <https://github.com/Dewey3> Just to confirm, you're seeing this issue again in v4.5.0 or later? — Reply to this email directly, view it on GitHub <#760 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFAB7DIORCWYRAEATBVIYFTW6HWOJANCNFSM6AAAAAATNWHTBU> . You are receiving this because you commented.Message ID: ***@***.***>

[robotastic]

Closing this and tracking in #836