Is there a trick to using Rdio-Scanner with DSD+ Fast Lane?

[saioke]

I enjoy using Rdio-Scanner, but I haven't been able to get it to work properly unless I use Trunking Recorder to upload my calls coming in from DSD+ Fast Lane. I don't think it's ideal to run Trunking Recorder just for that purpose though. For one, it uses 100+mb ram and on Windows 11 you need all that you can get. For another, I don't like having another program sitting in the task bar. Also, trunking recorder doesn't seem to upload audio calls unless they're in .mp3 format.

I would really like to get Rdio-Scanner working so I don't have to use Trunking Recorder. In the Rdio-Scanner admin panel, I created a dirwatch, linked my dsd+ folder, using .wav extension. have it set so that audio files to go to a system, talkgroup is left blank because well, I don't want all talkgroups to show as one particular talkgroup. "type" is set to "DSD+ Fast Lane".

Okay, so setup there is done, so I should be receiving calls, right? Nope. "Incomplete call data - Talkgroup" appears in the rdio-scanner cmd terminal. Now, if I disable "add talkgroup aliases to per-call file names" and "Add radio aliases to per-call file names" under the "output" tab in DSD+ Fast Lane, it will actually begin to upload calls... To another system with a 840 ID, not my original one with id 120. Also, calls will upload without talkgroup information. Okay, that's fine. I'll just add/edit the talkgroups I want manually in this new 840 system created by rdio-scanner. Getting somewhere!

Everything appears to work now, but NOW I have an issue where occasionally, calls will fail to upload with the "no talkgroup" error again, especially if they're 3 seconds long or below. I can go to the dsd+ recordings folder to find that yes, they exist, and rdio-scanner didn't import/delete them like it's supposed to. Some are choppy, which is understandable. I don't think Trunking Recorder will upload call recordings if they're choppy either. But, a few had clear voices so I'm not so sure that it should be happening.

For example:

Talkgroup 51540 is a sucess, with rdio-scanner claiming such: "newcall: system=840 talkgroup=51540 file=213032_001_P25_BEE00.348-3.79_GC_51540_0.wav success"

But next, the same talkgroup will speak a reply, following with the error "dirwatch.ingest: no talkgroup, C:\Users\blah\OneDrive\Desktop\dsd+\1R-Record\20250609\213025_002_P25_BEE00.348-3.79_PC_0_0.wavnotifications"

So, the one that says "no talkgroup" doesn't even have the talkgroup ID listed in the .wav file. But, the one above it does. That seems to be the issue. Any ideas why DSD+ wouldn't include the talkgroup ID in "some" audio recordings? I feel like this issue could be fixed if Rdio-Scanner allowed you to upload calls with the TG and Radio Aliases enabled in DSD+. But for some reason, only Trunking Recorder has the ability to upload calls that contain those options. That being said, I don't recall Trunking Recorder ever failing to upload any calls because the call had missing metadata information?

Perhaps this could be fixed with a rdio-scanner custom mask, but I wouldn't know where to begin with that. Anyone have this issue? Maybe you fixed it with a custom mask that I can copy?

 

[saioke]

After doing some more research and despite some of these call recordings seem clear to understand, I believe that they're failing to be ingested because of poor decoding/errors detected in the voice comms, which causes the .wav file DSD+ generates to save without proper metadata, so Rdio-Scanner sees them and says "hey, this recording has no talkgroup."

I've been having some poor signals this past week due to the weather. That's likely why. Ultimately, I think Rdio-Scanner and DSD+ is working fine after all. But I still have no explanation as to why sometimes Rdio-scanner will upload a call and that call will show as the talkgroup ID despite having the talkgroup information in rdio-scanner. But, this happens rarely. Could maybe also be due to detected errors during decode I'm going to guess.