DSD+ 2.324

[dave3825]

NOTE! YOU SHOULD ALWAYS BACK UP YOUR CURRENT DSD+ FOLDER BEFORE APPLYING A FAST LANE UPDATE!

YOU SHOULD ALSO PERIODICALLY BACK UP YOUR DSD+ DATA FILES

DSD+ 2.324

Fixed decoding of P25 triple block PDUs.

Added reporting of P25 DVI-XL and DVP-XL encryption algorithms.

Fixed TIII stun/unstun message decoding.

Added decoding and reporting of additional DMR GPS/AVL messages.

Added DMR system disambiguation via DCC support in the DSDPlus.frequencies file.

This feature is primarily designed for Cap+ systems where sites share common frequencies.
DCC values can be appended to DMR channel entries in the DSDPlus.frequencies file.

Example:

Cap+, 1234, 3, 1, 454.7625, 0.0, 0, 12

Cap+, 1234, 7, 1, 454.7625, 0.0, 0, 14


If FMPx is manually tuned to 454.7625 and DSD+ detects a Cap+ datastream,
DSD+ will use the received digital color code to determine whether site 3
or site 7 is being monitored.

A DCC does not need to be added to a DMR frequency entry unless disambiguation is required.

You should edit the comment at the top of the DSDPlus.frequencies file
to reflect the new optional DCC field:

Old: ; protocol, network ID, site number, ... sort order

New: ; protocol, network ID, site number, ... sort order [, DCC]


FMP24 2.74

Added automatic detection of I/Q stream dropouts.
Added automatic enabling of extra CPU loading to stop I/Q stream dropouts.

Command line change:

-e0: Extra CPU loading disabled; FMP24 will report I/Q stream dropouts in console window
-e1: Extra CPU loading enabled
-e2: Automatic enabling of extra CPU loading if I/Q stream dropouts are detected

Default is -e2

Active key change:

Pressing E will cycle through the above three modes

 

[air-scan]

I can see less errors and can tell of a minor improvement of voice on a P25 PII TDMA system. I wonder if the triple block PDU's being fixed had something to do with it. I mean this system is built by L3 Harris. Some custom stuff L3 Harris does I dunno.

 

[BM82557]

My beef isn't new to V2.324 but I'm adding it here . Developers, could you please change the color of IPI private data calls to something easier on the eyes? --

 

[BM82557]

Just an FYI -- I reverted back to V2.303 because the latest version of FMP24 was using quite a bit more CPU than the prior version did. It was quite noticeable and was to the point of affecting my pc's response. Probably I will go back to V2.324 but disable FMP24 extra CPU loading instead of using the default.

 

[Reconrider]

Just an FYI -- I reverted back to V2.303 because the latest version of FMP24 was using quite a bit more CPU than the prior version did. It was quite noticeable and was to the point of affecting my pc's response. Probably I will go back to V2.324 but disable FMP24 extra CPU loading instead of using the default.

HOw do you disable that?

 

[GTR8000]

HOw do you disable that?

Right out of the release notes:

Added automatic enabling of extra CPU loading to stop I/Q stream dropouts.

Command line change:

-e0: Extra CPU loading disabled; FMP24 will report I/Q stream dropouts in console window
-e1: Extra CPU loading enabled
-e2: Automatic enabling of extra CPU loading if I/Q stream dropouts are detected

Default is -e2

 

[RaleighGuy]

HOw do you disable that?

Read Post #1 instructions are given there

 

[BM82557]

Just an FYI -- I reverted back to V2.303 because the latest version of FMP24 was using quite a bit more CPU than the prior version did. It was quite noticeable and was to the point of affecting my pc's response. Probably I will go back to V2.324 but disable FMP24 extra CPU loading instead of using the default.

Disabling CPU loading did the trick, machine is back to normal. That particular pc is a quad-core with 8 gig, running Win 7.

 

[CanesFan95]

What are " P25 triple block PDUs"?

And " I/Q stream dropouts"?

 

[CanesFan95]

It looks like -e1 doesn't work on AirSpy FMPA . So does this "extra CPU loading to stop I/Q stream dropouts" thing (whatever that means) work at all on AirSpy?