joeuser
The Wretched
Just to update, I did a system reboot Friday or Saturday. My DSDplus is still up & running - I have not lost text in the event log like I had in a couple days of use, after the initial install. So that may have been a glitch.
I am getting rapidly scrolling decode data in the console window from DSDPlus v1.51, but the Event Log window never shows anything after initial startup, except for DC or CC information on the bottom part of the window itself.
I get error indications on practically every decode line, regardless of input levels or any other settings. Most are "CACH ERR" messages.
LRRP is not seeing anything, either. The systems I am testing on seem to have no voice traffic at all.
I asked before if it was supposed to be decoding CC info but never got an answer as its not doing it for me. As you said just displays running info in window but nothing at all else on what information its getting from the control channel.
Don't know if its supposed to not do anything or if I have an issue.
Why aren't you choosing the appropriate input source? Have you tried anything to troubleshoot it like adjust levels, decode a nice, strong signal, etc?
Dave,I am getting rapidly scrolling decode data in the console window from DSDPlus v1.51, but the Event Log window never shows anything after initial startup, except for DC or CC information on the bottom part of the window itself.
I get error indications on practically every decode line, regardless of input levels or any other settings. Most are "CACH ERR" messages.
LRRP is not seeing anything, either. The systems I am testing on seem to have no voice traffic at all.
I have an all data frequency local to me that acts as above.
Do either of you have a different frequency to try?
Dave,
I usually see "cach err" if I am off freq or trying to decode a poor quality signal. Nonetheless, I would imagine that you would see something in the event log. Do you have other systems to try? Also, are you using an SDR or discriminator tap?
Screen shots don't provide much information, or at least not the most important information. Raw audio recordings reveal exactly what's wrong with a signal.I'll try another session and take some screenshots over the weekend.
Ran fine until my reboot this even. Solid! Never lost text, it shutdown gracefully.Just to update, I did a system reboot Friday or Saturday. My DSDplus is still up & running - I have not lost text in the event log like I had in a couple days of use, after the initial install. So that may have been a glitch.
Ran fine until my reboot this even. Solid! Never lost text, it shutdown gracefully.
Very happy! Would like to be able to resize the event log & source audio though!
-wsl<v>.<h> Source audio waveform window location [10.10]
-wss<h>.<w> Source audio waveform window size (min 50.200; 0 blocks) [200.300]
-wsp<num> Source audio waveform window update period (10-1000) [100]
-wcl<v>.<h> Channel window location [90.90]
-wch<num> Channel window font height [15]
-wss0.0 blocks creation of source audio windowI think these few lines are what needs to be adjusted, but I can't seem to get it right.
I would like neither to open.
Fixes for IDAS issues require raw audio samples. To date, very few IDAS samples have been uploaded.I can confirm that 1.51 is displaying erroneous free channels for IDAS trunking. Just about every frequency I decode spits out bogus channels, plus should not show 31 since it's not a valid voice channel. And as far as I know there should only be one (## + 0) or two free channels announced per frame (Per docs I've read).
.srt file handling is being reworked. Functionality will be restored at some point.First of all, many thanks to the developers!
One question: I noticed that the SRT files no longer contains the radioID. I am using DSDplus to monitor a MotoTRBO system and it was working fine before upgrading to the latest version.
Am I the only one experiencing this issue?
Thanks,
VA2HEB
MotoTRBO TMS (Short Message Service) is already supported. If you are referring to something else, please provide details.Is there plans to decode MOTOTRBO Text Messages on the Roadmap/Pipeline? I install and maintain TRBO systems and would like to use that function as a tool in my toolbox. Thank you, TT.
"NXDN" is ambiguous.In relation to NXDN, in particular trunked voice, any chance of having encrypted/scrambled users identified? ie, in the Event Log window, perhaps with a [e] and in Red colour?
DSD+ doesn't really care what level you use. Just avoid clipping.What Line-In level setting are people having the best results with? I'm finding it doesn't make much difference.
-wss0.0 blocks creation of source audio window
Channel window is required for proper program operation.