DSDPlus

[mrpurrfect69]

Right ok here is where I am, starting from the command prompt
cd\
cd\dsd
dsdplus -O decodedaudio1.wav

Program starts as you can see in the image, when I hit R it still only records the raw audio & not the decoded audio, What am I doing wrong????

 

[Jay911]

Decoded audio is written to "decodedaudio1.wav" when you hit Esc at the end of the session. Hitting "R" only and always only writes raw audio continuously to a specifically-named raw audio file.

Try "dsd -h" for the help pages for some more information.

 

[Forts]

Don't hit R. It's only purpose is to record raw audio.

 

[mrpurrfect69]

So is it recording the moe it starts up with the dsdplus -O decodedaudio.wav inputted at the command prompt & just waiting for a voice transmission before the decoded audio is recorded ??? & then is it just a case of hitting the ESC button ????

 

[Forts]

You got it!

 

[mrpurrfect69]

Brill I'll give it ago will it still record as well as it been heard coming out the PC speakers as well ???

 

[Forts]

Yes it will.

 

[mrpurrfect69]

Has anyone else noticed this when streaming back via zello: (for example) Anything that is transmitted on slot 1 (America + South Pacific) it will stream back over zello but anything transmitted on slot 2 (Local) it won't stream the audio back over zello at all...... Any suggestions

 

[rjschilder]

I'm not sure if this was asked already (I tried reading all the posts).

If the author of DSDPlus is watching this thread (or anyone that can get in touch with him/her), would it be possible to decode any OpenSky systems? I live close to Milwaukee WI and the City of Milwaukee uses OpenSky. I would be more than happy to post raw audio samples of the datastream. Does anyone think this is worth pursuing?

-Ryan KC9GMY

 

[br0adband]

It would be interesting to see some miracle happen with DSD+ (or DSD, whichever) that allowed for monitoring OpenSky systems. While they are very rare compared to Motorola or other systems of any kind, I happen to live in a city - Las Vegas, NV - that went down the OpenSky path a few years ago and yes, it was a fiasco from start to the finish which should be approaching soon now that the Las Vegas Metro Police Dept (LVMPD) finally got a new system contracted with Motorola. I believe it'll be a 700 MHz P25 Phase 2 based rollout starting sometime before the middle of this year, but there's no word yet on whether or not they'll go through the trouble of encrypting all the traffic - I certainly hope they don't but it might happen.

Roughly $30 million down the tubes for the OpenSky mess, and now even more money spent to hopefully do it right the second time. Idiots should have just joined into the extremely well-functioning and quite capable S.N.A.C.C. system here in my area which handles pretty much everything else with respect to governmental, law enforcement, and fire/EMS traffic including McCarran Airport and several other agencies too.

Regardless, as has been noted here in many threads discussing OpenSky systems, the chances of it ever being fully capable of being monitored is between like, null and void, zip, zilch, nada, nothing.

But you just never know...

 

[bainino]

Hi

Uploaded raw audio of IDAS dPMR:

Zippyshare.com - idas-dpmr.wav

I don't know if it's encripted or open.

thanks

 

[rjschilder]

Not sure if anyone is interested, but i'm writing a repeater program that uses dsd+ for squelch (NAC, etc...). Just got it all working about 30 mins ago

http://forums.radioreference.com/di...ware/281568-p25-repeater-dsd.html#post2102318

-Ryan KC9GMY

 

[W4UVV]

While I'm not absolutely 100% certain of this, based on what W4UVV is saying so far, he's (or she's, sorry) simply unable to do anything from the keyboard except Esc or Control-C meaning the - I R etc keys as listed in the readme/user guide don't work at all. Call me crazy but that's what I'm reading in what W4UVV has said.

W4UVV: DSD (the original, not DSDPlus/DSD+) defaults to decoding all detected formats which would be the switch -fa (as listed in the options.txt file:

Decoder options:
  -fa           Auto-detect frame type (default)

which is pretty much what DSDPlus/DSD+ does too: it attempts, by default, to decode any format thrown at it by frame types.

As for all the options that W4UVV seems to be hoping for, DSDPlus is a different beast: it does all those automagically for the most part. It's possible to force it to do specific decode options (like decode only NXDN 4800 vs NXDN 9600) but they're not possible options once the decoder is actually running - they have to be set from the command line directly when you run the instance of the decoder or else it's going to listen for everything and decode as found unless a switch tells it not to.

Least that's how I'm understanding stuff so far...

Anyway, here's something: has anyone noted the need for some really excessive precision with respect to decoding NXDN? I've apparently only got two options for NXDN here in Las Vegas: the Luxor which I suspect is a bit too far away from me in downtown to get anything from since I have a ton of buildings and casinos and whatnot in the direct signal path (including a huge building right next to me that blocks pretty much all my ability to get traffic from McCarran Airport), and The D which used to be Fitzgerald's - they are using NXDN hardware but I can't even find a license for it yet with the proper emissions.

Having said that, the issue for me is that when I'm detecting the NXDN activity on a frequency (by hearing the data stream in one speaker), I have to manually retune the ppm aspect of SDR# to get an actual decode from DSDPlus and it's a bit frustrating at times. For example I can get the Fremont Street Experience MOTOTRBO content (Security) at 464.100 and it's spot on and I mean when I look at the zoomed in waterfall I've got my RTL stick calibrated to 57 ppm at 464.100 and it's perfect for DSDPlus decodes, rarely if ever will I see any errors whatsoever. Same situation with another MOTOTRBO system at 463.3375 (Trump International Hotel) - again the waterfall shows a dead-center frequency match (I use 470.309 to calibrate this stick I'm using, I have another stick that calibrates to 50 ppm).

While I can get content at 463.3375 and 464.100 dead-center and never have issues with decoding, whenever I'm grabbing NXDN content from The D on 463.6225 I have to retune the ppm to 59 to get a decode at all: if it's 58 or 60, I get zip, nada, zilch, absolutely nothing whatsoever even though the signal comes in booming since I'm just 3 blocks away and practically line of sight with their antennas on top of the their facility.

It almost seems like they're transmitting on frequencies that keep sliding up and down the scale somewhat, it's the weirdest thing I've encountered yet with this SDR kick I'm on. It's not the sticks as noted because I calibrate them every so often in a session just to ensure they're working right and that 50/57 ppm corrections I've noted a pretty much solid as far as a non-TCXO can be - as noted the other frequencies right there in the same range (within 1 MHz) all tune perfectly so, I'm not sure what the hell is going on. When I do get a "lock" on the signal I get great decodes, DSDPlus is really amazing in that respect, but it's somewhat irritating to have to keep retuning that ppm more frequently.

Is anyone else having issues with NXDN that make a decode so prone to being so spot on with the frequency/ppm? Just curious... guess I'm gonna need a frequency counter and go take a walk down to The D sometime.

Correct...no keyboard recognition using DSDPLUS except "CTRL C" and "ESC". I finally solved the mystery. I reinstalled DSDPLUS at the c:\ root directory level. All is good. Both dsd 1.6.1 and DSDPLUS working great and with keyboard recognition.

John
W4UVV.

 

[Audiodave1]

It would be interesting to see some miracle happen with DSD+ (or DSD, whichever) that allowed for monitoring OpenSky systems.

Regardless, as has been noted here in many threads discussing OpenSky systems, the chances of it ever being fully capable of being monitored is between like, null and void, zip, zilch, nada, nothing.

But you just never know...

I sent in some samples of the wonderful Pennsylvania statewide "ClosedSky" system for potential work a year or so ago. Such a rare bird so I would not expect support...But I can always wish!

 

[ronenp]

DSD plus on p25 Control CH

Hi there
what is the info the DSDPlus provide while listening to P25 Control Ch ?
I can see NAC and in the next line i see number like that 360 SC=500.333 the 360 is stable but the 500000 keeps growing all the time
what is this 360 and the other number ? is there any DOC ?
how can i see the site number (in case of Trunked station) and system ID ?
Thanks for any Info
Regards
R

 

[mtindor]

Hi there
what is the info the DSDPlus provide while listening to P25 Control Ch ?
I can see NAC and in the next line i see number like that 360 SC=500.333 the 360 is stable but the 500000 keeps growing all the time
what is this 360 and the other number ? is there any DOC ?
how can i see the site number (in case of Trunked station) and system ID ?
Thanks for any Info
Regards
R

DSDPlus is a voice decoder, not a trunked system monitoring application.. If you want to see trunked system specifics, use something like Unitrunker.

There are no docs on the numbers you see when monitoring a P25 control channel. Your guess is as good as anyone elses.

M

 

[highmaster2]

Just a (hopefully) basic question...

Have read this thread a couple of times, but still not clear on the whole concept. I have an AR8200 getting the detector/discriminator tap from an AOR accessory cable (gray wire). I have that going into to both L & R channels to the Microphone jack on my laptop (no Line In). I am running DSD+ forced to decode DMR/TRBO. I have the input set to Microphone and the output set to speakers. Right now all I hear is what sounds like a control channel - from the scanner, not the laptop speakers. What other hardware/software do I need to decode & hear voice on a TRBO system? I'm running Win7 Pro 64. I'm trying to monitor Pell City, AL PD.

Thanks much for any help and clarification.

 

[mtindor]

Have read this thread a couple of times, but still not clear on the whole concept. I have an AR8200 getting the detector/discriminator tap from an AOR accessory cable (gray wire). I have that going into to both L & R channels to the Microphone jack on my laptop (no Line In). I am running DSD+ forced to decode DMR/TRBO. I have the input set to Microphone and the output set to speakers. Right now all I hear is what sounds like a control channel - from the scanner, not the laptop speakers. What other hardware/software do I need to decode & hear voice on a TRBO system? I'm running Win7 Pro 64. I'm trying to monitor Pell City, AL PD.

Thanks much for any help and clarification.

If you are using the -i and -o switches in DSD+ to force the of the proper input and output, and you are hearing the control channel, my guess is that in your sound properties you hvae something like a "What You Hear" or an option to "listen" to the input signal.

You're setup is probably correct other than the fact that you have your sound properties set [probably not intentionally] to play back the mic-in to your output device [speakers]. And it's a matter of just turning that off.

After that, you must keep in mind that a TRBO control channel could go on for days without any voice traffic being sent on it. The agency might be using it predominantly for AVL data or something like that. Or the agency might not be active on the weekend. And you need to determine if it's a standalone TRBO repeater or Cap Plus / Connect Plus. If you're monitoring a channel that is spewing TRBO 24/7, then it is probably a Connect Plus control channel. It can have voice activity on it, but in this scenario it would be likely that there are other frequencies a part of the system that are used for most voice.

Look at your Recording Properties in the control channel, specifically the properties for your mic-in. Look for any boxes that mention "listen". Remove the checkmark from listen. Look at your mixer controls, and look for a slider for "What You Hear" or something like that. Mute it and see if the control channel noise goes away.

As far as I can imagine, the only way you are hearing the control channel input in your speakers is if your audio device recording properties are specifically set to play back the input on the output. And that really shouldn't be the default.

You might also want to run DMRDecode (latest build is 73 I think) simultaneously, as it will provide you with information about the particular system you are monitoring -- at minimum it'll give you information about the Color Code in use. If there are active talkgroups, it'll show you the TGIDs. If you're monitoring a ConnectPlus system, it will tell you if the frequency you are listening to is a CC or a VC and it will tell you the Network ID.

Mike

 

[highmaster2]

Thanks for the quick response. Note: I am hearing the sound from the scanner - not the laptop. I did mute the microphone playback in Windows just to be sure. However, I am not even sure what I should be hearing. Should I be hearing the "control noise" at all? What I hear is the "control noise" in bursts of 1 - 2 seconds at varying intervals. If all is working correctly, should I only be hearing the decoded voice when there is some? Using the discriminator tap, does the volume even have to be up to work? If I knew more how things work when set up properly, I could maybe understand the troubleshooting path a little better. Have downloaded DMRDecode. I see the level meter fluctuate to reflect the same level shown by DSD+, but that's all it tells me - no color code, system, etc. Thanks again for your help.

 

[mtindor]

Thanks for the quick response. Note: I am hearing the sound from the scanner - not the laptop. I did mute the microphone playback in Windows just to be sure. However, I am not even sure what I should be hearing. Should I be hearing the "control noise" at all? What I hear is the "control noise" in bursts of 1 - 2 seconds at varying intervals. If all is working correctly, should I only be hearing the decoded voice when there is some? Using the discriminator tap, does the volume even have to be up to work? If I knew more how things work when set up properly, I could maybe understand the troubleshooting path a little better. Have downloaded DMRDecode. I see the level meter fluctuate to reflect the same level shown by DSD+, but that's all it tells me - no color code, system, etc. Thanks again for your help.

If you are hearing the sound from the scanner, then I suspect you should turn down the volume on the scanner. There is nothing of interest to hear [scanner-side] unless you know what a TRBO signal sounds like and you want to quickly search/tune and find one, or unless you want to troubleshoot. I'm not familiar with the AOR 8200, but I suspect that the speaker volume on the AOR is probably separate from the discriminator output -- and if so, then turning the volume down so you don't hear the raw TRBO digital transmissions isn't going to hurt anything. I'd guess you'd have to check that though.

If you are hearing the bursts, then I don't think it's a ConnectPlus channel but rather either a Cap Plus or standard TRBO repeater. I only listen to ConnectPlus around here, so i'm not familiar with how the others should be. But if you're hearing bursts, you're hearing raw audio. You need to mute that (at the volume control if the sound is coming from the scanner, or in your playback properties, if the sound is coming out of your speakers).

The only thing that will come out of DSD+, as far as audio goes, is unencrypted, decoded voice. Depending upon what you are trying to decode with DSD, you might hear "encrypted" audio, which sounds like you would expect -- R2D2 for lack of a better word.

So if you're hearing anything at all that any normal user would hear on a regular scanner when they tune to that TRBO frequency, you are hearing raw audio -- and you need to mute it.

Depending upon the agency who operates the TRBO, there may be a ton of traffic, there may be little traffic, there may be traffic only during normal business hours, it may be encrypted, etc.

So don't expect that just because you hear a TRBO signal, there is automatically voice being transmitted at that very time.

In DMRDecode, depending upon your setup, you may have to select the option to Invert the signal. You dont' need to do that in DSD+ -- it will automatically do it. But if you are monitoring with DMRDecode and you are not seeing anything useful except for constant claims that there is voice data [which you aren't hearing], you probably need to invert the signal. It's in one of the menus in DMRDecode.

Assuming your audio level in is okay, DMRDEcode should show something . It might not pick up on the beacons because the beacons are over before DMRDecode gets a chance to lock on and start decoding. but on a transmission of any decent length, DMRDecode will lock on [if the signal quality is good and is not weak], and you'll be able to see some information in DMRDecode.

Yeah, I think should be able to just turn down the volume on the scanner. The discriminator audio level out of the scanner will be constant, nonsquelched, and at the same audio level regardless of the setting of your volume knob.

Mike

Mike