Unitrunker Release 30 (updated with Hot Fix)

[Whelen]

The text below was copied from the rtl-sdr web site where I purchased the dongles.

Decoding Digital Voice (P25/DMR/Mototrbo/NXDN/ProVoice)

Decoding of unencrypted digital voice signals like P25/DMR/Mototrbo can be set up in the same way as the analog system shown above. However, instead of outputting audio to the speakers, audio should be output to a virtual audio pipe such as Virtual Audio Cable (VAC) or VB Cable using the Digital Output audio selection in Unitrunker. Then DSD+ should be used to listen to the audio pipe. Audio will only be piped to the Digital Output during a digital call.

Unitrunker Digital Audio Output
Unitrunker Digital Audio Output
DSD+ is a program that is capable of decoding digital voice protocols such as P25, DMR/Mototrbo, NXDN and ProVoice. It is not capable of decoding encrypted digital voice channels. DSD+ is similar to DSD 1.6, but it has vastly improved decoding in terms of voice quality. You can find the latest download for DSD+ in this RadioReference forum thread. As the thread is long, a direct download to version 1.51 is linked here.

To run DSD+ simply double click on DSDPlus.exe. This will open up several windows. DSD+ will listen to the default sound device in the Windows audio recording properties.

Make sure that the Deemphasis option in Unitrunker is turned OFF for the voice receiver to make it work with DSD+.

 

[Jay911]

DSD+ can indeed monitor a MotoTRBO system, but Unitrunker has no role in that.

If you want to use DSD+ with an SDR dongle, run SDRsharp and pipe its output to the virtual audio cable, and tell DSD+ to listen to that VAC line.

 

[Whelen]

OK, that makes sense. I will give that a try. Thanks for all of the help!

 

[nlurker]

I am now seeing this new bug too. It appears to show an incorrect source id when the current transmission has none, but in the top half only. The bottom half is correct.

UniTrunker, did you acknowledge this bug? I am seeing it consistently all the time now. It used to be blank when a transmission has no source id, but the latest version (where is the version number displayed?) shows an incorrect source id which seems to be repeated from a recent different transmission.

 

[SCPD]

nlurker - this will be fixed in the next release.

You can see the version by clicking on the "?" tool button.

 

[joeuser]

nlurker - this will be fixed in the next release.

You can see the version by clicking on the "?" tool button.

Just curious, when do you think the next version may be released? I'm not asking for a concrete data, just a rough idea - if that's even possible...

 

[nlurker]

nlurker - this will be fixed in the next release.

You can see the version by clicking on the "?" tool button.

Thank you!

 

[kayleesdad]

date stamp event files

Up and running, works great as always!

I was wondering about the date stamp in the event files. it seems to be 5 hours ahead of time. Is there a way to adjust the date stamp?

As an example, the last i-call was at 05:13:33 am as reflected in the call history tab, rather than 10:13:33 am:

20150306101329,1,Call,I,15326,I,15361,2,Ana
20150306101333,1,Call,I,15361,I,15326,4,Ana

I guess it's not that hard to subtract 5, but I thought I'd ask!

Thanks!

 

[SCPD]

Up and running, works great as always!

I was wondering about the date stamp in the event files. it seems to be 5 hours ahead of time. Is there a way to adjust the date stamp?

As an example, the last i-call was at 05:13:33 am as reflected in the call history tab, rather than 10:13:33 am:

20150306101329,1,Call,I,15326,I,15361,2,Ana
20150306101333,1,Call,I,15361,I,15326,4,Ana

I guess it's not that hard to subtract 5, but I thought I'd ask!

Thanks!

It is in UTC. As far as I know .. it cannot be changed.

 

[melbournefan]

What about support for one dongle if all CC's are on the same band