saioke
Member
- Joined
- Apr 18, 2010
- Messages
- 311
- Reaction score
- 148
So, since I've began using Rdio Scanner, I've had this issue that happens occasionally. Sometimes when it imports calls, rdio-scanner ingests them, but they have this unusual noise that replaces the actual call audio - Here's an example.
This happens a lot more often on short calls, or calls that are over 50 seconds long or so. But, there's really no rhyme or reason why I can see it happening.
DSD+ Fast Lane is my software of choice, and I can confirm that the call that gets recorded is completely clear and listenable straight from the recording folder. So, it's not a DSD+ decoding issue. Something wrong happens when rdio-scanner imports it. This also happens whether I have dirwatch enabled, or use a third party program like Trunking Recorder to ingest the audio first.
Has anyone experienced this before and know what causes it or how to fix it?
Edit: Actually, this may be DSD+ Related after all. I've discovered that the calls that do this:
have a string of extra characters at the end. So, rdio scanner doesn't import it. The call above that one is the "noise" I spoke about earlier and it's what rdio-scanner actually ingested. This one however, isn't ingested. I think I know why - perhaps the call is keyed up then released, and then the officer keys up again to speak his business, and this all happens within a second. So, these are treated like duplicate calls? But then, is there a way to get rdio-scanner to import these calls with the extra string?
This happens a lot more often on short calls, or calls that are over 50 seconds long or so. But, there's really no rhyme or reason why I can see it happening.
DSD+ Fast Lane is my software of choice, and I can confirm that the call that gets recorded is completely clear and listenable straight from the recording folder. So, it's not a DSD+ decoding issue. Something wrong happens when rdio-scanner imports it. This also happens whether I have dirwatch enabled, or use a third party program like Trunking Recorder to ingest the audio first.
Has anyone experienced this before and know what causes it or how to fix it?
Edit: Actually, this may be DSD+ Related after all. I've discovered that the calls that do this:

have a string of extra characters at the end. So, rdio scanner doesn't import it. The call above that one is the "noise" I spoke about earlier and it's what rdio-scanner actually ingested. This one however, isn't ingested. I think I know why - perhaps the call is keyed up then released, and then the officer keys up again to speak his business, and this all happens within a second. So, these are treated like duplicate calls? But then, is there a way to get rdio-scanner to import these calls with the extra string?
Last edited: