DSDPlus DSDPlus 2.443 available

[u2brent]

OK, My 2¢ on these recent updates.
Running CC/VC instances with 2 V3 dongles.
The "Added display of Algorithm ID and KID for encrypted P25 TDMA calls to event log and Current/Seen Groups window." as described in 2.395 is broke and has been since after 2.368. It simply ain't displayed in either instance any more. (I keep returning to 2.368 to avoid that annoyance.)

Also,

Despite Verbosity set to 0 (to avoid all those huge log files when not wanted) ain't yielding the expected results. Seems that the new "0" is the old "1" setting. It continues going on and on despite a "0" setting as previous versions.

Also the odd parsing effect is going on (as mentioned by many) in the VC log.

But not the CC log, IDK. Just thought it's worth a mention.

These minor issues are just enough of an annoyance to me to keep returning to 2.368 where these worked fine. IMHO.
The new Packet Data is interesting though!

So back to 2.368 I go again. LOL

Oh I forgot to mention those new log files also have no way of being turned off that I could see.

 

[dave3825]

These minor issues are just enough of an annoyance to me to keep returning to 2.368 where these worked fine. IMHO.
The new Packet Data is interesting though!

But then your missing those dotted quad sender IDs.

LRRP 1.25

Added support for dotted quad sender IDs.

Seriously tho,

The "Added display of Algorithm ID and KID for encrypted P25 TDMA calls to event log and Current/Seen Groups window.

simply ain't displayed in either instance any more.

I am running 2.443 What kind of system? I am on a phase 2 operating in phase 1.

 

[u2brent]

😆 that's funny .... Don't really use LRRP, Though.

It's PA Starnet P25 Phase 2 exclusively, no phase 1 is permitted AFAIK. I've not tried any others. It shouldn't matter the way I see it. And a two dongle setup, not 1R, CC & VC copies running.

 

[mtindor]

Console log issue fixed in 2.444

 

[RaleighGuy]

Console log issue fixed in 2.444

Confirmed it is working for me now as well

 

[u2brent]

Console log issue fixed in 2.444

Confirmed it is working for me now as well

Yeah, But, Not the VC console, as posted above.

 

[mtindor]

Not the VC console, as posted above.

Not the VC console, as posted above.

You’re confusing me. I’m not gonna look up in the thread I run one dongle and the logging works properly for cc and vc traffic, and appears to be just fine

Explain your exact scenario where it’s not working for you

 

[RaleighGuy]

Not the VC console, as posted above.

The original reported issue was no CR at the end of lines on NXDN console and log, both are working for me, if you have a different issue then report it to DSD+, but please do not tell me my issue (or issue originally posted here) wasn't corrected.

 

[mtindor]

OK, My 2¢ on these recent updates.
Running CC/VC instances with 2 V3 dongles.
The "Added display of Algorithm ID and KID for encrypted P25 TDMA calls to event log and Current/Seen Groups window." as described in 2.395 is broke and has been since after 2.368. It simply ain't displayed in either instance any more. (I keep returning to 2.368 to avoid that annoyance.)
View attachment 151728
Also,
View attachment 151729
Despite Verbosity set to 0 (to avoid all those huge log files when not wanted) ain't yielding the expected results. Seems that the new "0" is the old "1" setting. It continues going on and on despite a "0" setting as previous versions.

Also the odd parsing effect is going on (as mentioned by many) in the VC log.
View attachment 151731
But not the CC log, IDK. Just thought it's worth a mention.
View attachment 151732
These minor issues are just enough of an annoyance to me to keep returning to 2.368 where these worked fine. IMHO.
The new Packet Data is interesting though!

So back to 2.368 I go again. LOL
View attachment 151734
Oh I forgot to mention those new log files also have no way of being turned off that I could see.View attachment 151736

RE: Your ALG/KID issue

It's a single-dongle monitoring feature. If you are using separate CC/VC dongles it isn't going to work -- mainly because the CC side doesn't know which talkgroups to chase, so it isn't going to tune to ENC talkgroups -- so the VC side isn't going to bother displaying any AlgID/KID info.

DSDPlus displays AlgID/KID info when "limited ENC following" is enabled. And that can only be enabled in Combined CC/VC monitor. The option isn't even clickable/available when running CC and VC dongles.

As far as VC copy console still being messed up, I'm sure the author will investigate if possible.

As far as Packet data, if you don't like the logs then stop following packet data. Disable / LO data call following.

 

[u2brent]

You’re confusing me. I’m not gonna look up in the thread I run one dongle and the logging works properly for cc and vc traffic, and appears to be just fine

Explain your exact scenario where it’s not working for you

Here is the direct link to the post, for those who can't be bothered with scrolling back a few.

DSDPlus - DSDPlus 2.443 available

OK, My 2¢ on these recent updates. Running CC/VC instances with 2 V3 dongles. The "Added display of Algorithm ID and KID for encrypted P25 TDMA calls to event log and Current/Seen Groups window." as described in 2.395 is broke and has been since after 2.368. It simply ain't displayed in either...

forums.radioreference.com

And I'm not typing it all over again. So there's that. Not sure what more is needed beyond what was already put forth. But OK, I get it. CC/VC aficionados are running separate copies, which is slightly different from you 1R copy folks. and Normal/full ENC following is an available option and is selected in both copies. As for the Alg quotes, it works just fine in the version I posted above as well. And there's a pic of the VC Groups window with the said info 2.368 at the bottom and the info is shown, I made a little effort to be clear and concise in that post, sorry if I've failed to deliver.

 

[u2brent]

RE: Your ALG/KID issue

It's a single-dongle monitoring feature.

This is simply an untruth, The VC event window shows all that info, it just isn't being displayed in the VC Group window.

 

[merlin]

I have a quick question.
When you enable .wav/MP3 recording, just where are these files saved??

 

[RaleighGuy]

I have a quick question.
When you enable .wav/MP3 recording, just where are these files saved??

In the DSD+/1R-record folder, usually in a folder with the date on it.

 

[u2brent]

Inside The 1R-Record or VC-Record folder inside the working DSD+ directory. Depending on which your running.

 

[u2brent]

The original reported issue was no CR at the end of lines on NXDN console and log, both are working for me, if you have a different issue then report it to DSD+, but please do not tell me my issue (or issue originally posted here) wasn't corrected.

You can clearly see in one of my screenshots I previously posted.... On a P25 Phase 2 system that the CC console is correct and the VC console with the cr missing/not present (looking like gobble-de-gook), is what I was referencing. I'm not calling anybody a liar, I'm simply pointing out that there is still an issue to be addressed. But this is all getting very tiresome. I almost wish I'd never posted anything at all. And for anybody not running separate CC/VC DSD copies there is no need to reply since this is not a 1R issue that I'm attempting to report, and should be dealt with with a different ideology, gee wiz folks.

 

[merlin]

Well, my hat is off to all those that developed and coded DSD+. Each of the supported protocols are mind boggling complex alone, then adding all the features and GUIs.
I find it perfectly acceptable such as it is. Spot a bug or problem, let the team know, they will fix it, but have patience.
I sure got my $25 worth.
(Just don't try to fix something that isn't broke)

 

[dave3825]

The only thing I noticed in 2.443 (may have started in 2.441) is discarded waveout blocks showing in red. I never had that before.

Extracted from event log.

    Line 18433: 2023/11/22  22:19:21  Freq=770.943750  NAC=015  281 discarded WaveOut blocks
    Line 18454: 2023/11/22  22:20:40  Freq=770.943750  NAC=015  2548 discarded WaveOut blocks
    Line 18514: 2023/11/22  22:25:57  Freq=773.818750  NAC=015  988 discarded WaveOut blocks
    Line 18571: 2023/11/22  22:30:53  Freq=773.543750  NAC=015  221 discarded WaveOut blocks
    Line 18595: 2023/11/22  22:35:52  Freq=774.281250  NAC=015  78 discarded WaveOut blocks
    Line 18616: 2023/11/22  22:38:00  Freq=770.943750  NAC=015  299 discarded WaveOut blocks
    Line 18661: 2023/11/22  22:41:06  Freq=773.818750  NAC=015  13 discarded WaveOut blocks
    Line 18680: 2023/11/22  22:44:40  Freq=770.943750  NAC=015  637 discarded WaveOut blocks
    Line 18695: 2023/11/22  22:48:13  Freq=770.943750  NAC=015  260 discarded WaveOut blocks
    Line 18735: 2023/11/22  22:57:59  Freq=770.943750  NAC=015  13 discarded WaveOut blocks
    Line 18753: 2023/11/22  23:05:37  Freq=774.281250  NAC=015  13 discarded WaveOut blocks
    Line 18764: 2023/11/22  23:07:04  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 18771: 2023/11/22  23:08:50  Freq=773.543750  NAC=015  143 discarded WaveOut blocks
    Line 18788: 2023/11/22  23:16:30  Freq=770.943750  NAC=015  13 discarded WaveOut blocks
    Line 18816: 2023/11/22  23:24:53  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 18840: 2023/11/22  23:28:06  Freq=773.543750  NAC=015  26 discarded WaveOut blocks
    Line 18907: 2023/11/22  23:41:46  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 18913: 2023/11/22  23:46:31  Freq=770.206250  NAC=015  26 discarded WaveOut blocks
    Line 18921: 2023/11/22  23:49:54  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 18955: 2023/11/22  23:59:26  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 18966: 2023/11/23  00:02:56  Freq=773.543750  NAC=015  13 discarded WaveOut blocks
    Line 19010: 2023/11/23  00:13:50  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 19156: 2023/11/23  00:53:14  Freq=773.818750  NAC=015  13 discarded WaveOut blocks
    Line 19192: 2023/11/23  00:56:28  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 19340: 2023/11/23  01:24:41  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 19349: 2023/11/23  01:30:12  Freq=773.543750  NAC=015  78 discarded WaveOut blocks
    Line 19377: 2023/11/23  01:36:54  Freq=773.818750  NAC=015  13 discarded WaveOut blocks
    Line 19398: 2023/11/23  01:41:01  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 19411: 2023/11/23  01:42:16  Freq=770.206250  NAC=015  39 discarded WaveOut blocks
    Line 19437: 2023/11/23  01:50:17  Freq=770.206250  NAC=015  26 discarded WaveOut blocks
    Line 19442: 2023/11/23  01:52:30  Freq=774.281250  NAC=015  65 discarded WaveOut blocks
    Line 19457: 2023/11/23  01:55:29  Freq=770.943750  NAC=015  13 discarded WaveOut blocks
    Line 19612: 2023/11/23  02:17:03  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 19644: 2023/11/23  02:20:23  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 19650: 2023/11/23  02:21:35  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 19655: 2023/11/23  02:23:51  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 19680: 2023/11/23  02:32:34  Freq=773.543750  NAC=015  247 discarded WaveOut blocks
    Line 19694: 2023/11/23  02:34:20  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 19708: 2023/11/23  02:36:36  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 19801: 2023/11/23  02:55:49  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 19814: 2023/11/23  03:01:35  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 20035: 2023/11/23  04:08:39  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 20045: 2023/11/23  04:19:02  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 20074: 2023/11/23  04:30:08  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 20094: 2023/11/23  04:35:55  Freq=773.818750  NAC=015  13 discarded WaveOut blocks
    Line 20127: 2023/11/23  04:46:27  Freq=774.281250  NAC=015  13 discarded WaveOut blocks
    Line 20183: 2023/11/23  05:18:07  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 20247: 2023/11/23  05:46:02  Freq=773.543750  NAC=015  221 discarded WaveOut blocks
    Line 20277: 2023/11/23  05:59:26  Freq=774.281250  NAC=015  13 discarded WaveOut blocks
    Line 20291: 2023/11/23  06:08:17  Freq=773.818750  NAC=015  143 discarded WaveOut blocks
    Line 20297: 2023/11/23  06:10:41  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 20298: 2023/11/23  06:11:44  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 20345: 2023/11/23  06:21:15  Freq=770.206250  NAC=015  26 discarded WaveOut blocks
    Line 20395: 2023/11/23  06:30:14  Freq=770.206250  NAC=015  13 discarded WaveOut blocks
    Line 20449: 2023/11/23  06:38:59  Freq=774.281250  NAC=015  767 discarded WaveOut blocks
    Line 20505: 2023/11/23  06:48:36  Freq=773.543750  NAC=015  156 discarded WaveOut blocks
    Line 20533: 2023/11/23  06:52:09  Freq=770.943750  NAC=015  26 discarded WaveOut blocks
    Line 20572: 2023/11/23  06:58:19  Freq=770.206250  NAC=015  26 discarded WaveOut blocks
    Line 20595: 2023/11/23  07:02:30  Freq=774.281250  NAC=015  1352 discarded WaveOut blocks
    Line 20637: 2023/11/23  07:10:08  Freq=770.206250  NAC=015  13 discarded WaveOut blocks

 

[RaleighGuy]

Won't format right UGH!

Do you still see the issue in the newest version 244?

 

[dave3825]

Won't format right UGH!

Alert says you quoted me, but not seeing a quote ?

 

[RaleighGuy]

Alert says you quoted me, but not seeing a quote ?

View attachment 151757

formatting issues so I removed the quote