DSD+ Fast Lane Short Decodes + DsdTune - Invalid command line paramater '-ds0'

[AB9NN]

I ran DSDTune to try and teak my system. I am getting 5 second or so calls on P25. They decode - messages scroll, etc. but audio is only a few seconds. Clear though! Smile. When I run DSDTune I get the following error:

Invalid command line paramater '-ds0'

Here are my command lines - I am specifically interested in P25 as SDTrunk decodes it quite nicely and I know the channels are active. My DSD+ FastLane and DSDTune, freshly downloaded, are in the same folder and DSDTune is run in that folder. To get my audio file I followed directions, started DSD+ and pressed R and waited for 30 seconds or so, then pressed it again. It did not specify clearly if this needed to be a voice transmission. Since I am only getting 5 second voice bursts very sporadically I think I am in a bit of a quandry.

CHDIR C:\_Files\SDR - Software Defined Radio\sdrsharp-x86\dsd+FASTLANE-P25

dsdtune -f1 -i DSDPlus-Raw-Input_2019-01-08@114440.wav -b p25_run.bat

C:\_Files\SDR - Software Defined Radio\sdrsharp-x86\dsd+FASTLANE-P25>dsdtune -f1 -i DSDPlus-Raw-Input_2019-01-08@114440.wav -b p25_run.bat
Checking option -ds
Running dsdplus.exe -o0 -O NUL -f1 -dsXXX ? DSDPlus-Raw-Input_2019-01-08@114440.wav
best value of 0 with -ds0
Checking option -dd
Running dsdplus.exe -o0 -O NUL -f1 -ds0 -ddXXX ? DSDPlus-Raw-Input_2019-01-08@114440.wav

To run DSD+ and try and decode P25 I run this batch file:

START 1-FMP-ControlChannel.bat
START 2-DSD-CC.bat
START 3-FMP-VoiceChannel.bat
START 4-DSD-VC.bat
START LRRP.EXE

That batch file runs these four batch files plus LRRP.exe:

FMP24 -i1 -o20003 -P0.0 -b9.5 -f853.9625 -rc

DSDPlus -e -fa -i20003 -rc -OM NUL

FMP24 -i2 -o20002 -P0.0 -rv -b9.5

DSDPlus -fa -rv -o1 -i20002 -OM NUL

I run two RTL-SDR dongles. I have freshly unplugged them and powered down the powered USB 3 USB extender - 7:1 USB extender plugged into my highest speed USB 3 port on the back of my Dell PC - Windows 10. Works like a charm for all other things!

 

[cg]

What version of DSDPlus are you using? There was an issue with short recordings in a previous version.

chris

 

[AB9NN]

DSD+ 2.155 Fast Lane Release

 

[cg]

The "Notes.txt" says the advanced decoder options (-mp, -dr, -dh, -ds, -dd, -dv) have no effect on P25 PSK signals when you use the TCP linking. I don't believe the DSDTune program has been kept updated to work on newer versions.
Does the DSDPlus set up including the use of the USB hub work with other signals?
Have you verified that there is no PPM adjustment needed?

chris

 

[AB9NN]

The "Notes.txt" says the advanced decoder options (-mp, -dr, -dh, -ds, -dd, -dv) have no effect on P25 PSK signals when you use the TCP linking. I don't believe the DSDTune program has been kept updated to work on newer versions.
Does the DSDPlus set up including the use of the USB hub work with other signals?
Have you verified that there is no PPM adjustment needed?

chris

Question before my answer - does the presedence of options matter - i.e. - can the input spec come after the output spec? I'm thinking that's probably OK but I'm not really sure. That means I'm just really guessing.

DSDTune not kept up to date - sounds like the major issue for the DSDTune issue but not the short audio bursts issue. DSD+ does not work with other signal. Other programs, however, running on the same hub and RTLSDRs do work. For example - P25 is decoded very nicely by SDTrunk - same configuration, requires two RTLSDRs, same hub, etc.. Since it decodes I think the PPM are probably within tolerance. I had adjusted on but that was on HF with a SpyVerter and that RTLSDR is not in the mix for this processing - two separate RTLSDRs.

 

[mtindor]

I have no input regarding your short audio burst issue.

> dsdplus -h
<snip>
Advanced decoder options:
-ds<num> Scaling factor (55-75; not used with D-Star or ProVoice) [-ds64]
-dd<num> Damping level (1-100; not used with D-Star or ProVoice) [-dd10]
-dv<num> Viewport size (1-30; not used with D-Star or ProVoice) [-dv20]

Notice, if you are using -ds<num> the number has to be between 55-75. Also notice that there is no -dr (rolloff) option. If you are using two dongles, two copies of FMP24, and two copies of DSDPlus, all with appropriate TCP Linking, I'd really suggest that you remove any tuning parameters such as -ds##, -dd##, -dv##.

While you are at it, you might as well clean up the dsdplus arguments by omitting -fa (which is the default action if no -f? switch is specified. Doesn't hurt to have it in there, but it clutters it up and serves no useful purpose.

 

[AB9NN]

I have no input regarding your short audio burst issue.

> dsdplus -h
<snip>
Advanced decoder options:
-ds<num> Scaling factor (55-75; not used with D-Star or ProVoice) [-ds64]
-dd<num> Damping level (1-100; not used with D-Star or ProVoice) [-dd10]
-dv<num> Viewport size (1-30; not used with D-Star or ProVoice) [-dv20]

Notice, if you are using -ds<num> the number has to be between 55-75. Also notice that there is no -dr (rolloff) option. If you are using two dongles, two copies of FMP24, and two copies of DSDPlus, all with appropriate TCP Linking, I'd really suggest that you remove any tuning parameters such as -ds##, -dd##, -dv##.

While you are at it, you might as well clean up the dsdplus arguments by omitting -fa (which is the default action if no -f? switch is specified. Doesn't hurt to have it in there, but it clutters it up and serves no useful purpose.

I did remove the -fa - agree on clutter. I also noticed - and maybe this a timing issue and because I am starting them all from one batch file, but I get the following error that "seems" to clear itself. Am I thinking about this correctly? Here is the output:

Mono audio decoding initiated; press Esc to exit...
TCP connect error = 10061
[No connection could be made because the target machine actively refused it]

Initiating TCP connection to 127.0.0.1:20002...

Seems like it tried to connect and then did. Not sure why the first attempt failed. Thinking because the batch file started it too fast and it wasn't ready for a connection. Could not be a firewall or virus prevention program issue, could it?

 

[mtindor]

That is to be expected. But, as you have noted, it recovers nicely. It's nothing to worry about as long as in the end both copies of FMP24 are properly connected to their DSDPlus counterpart.

I dont start from a batch file. I start manually, FMP24-CC.bat, FMP24-VC.bat, CC.bat, and VC.bat. But I start them pretty quick too. Never have any issue, even if I happen to get the initial message about the target machine actively refusing the connection.

 

[AB9NN]

Here's a little batch file I cobbled together via some Google searches on help sites to make stopping the running processes a little less annoying in Windows 10. Nice while tweaking settings, etc.

taskkill /F /IM FMP24.exe
taskkill /F /IM FMP24.exe
taskkill /F /IM DSDPlus.exe
taskkill /F /IM DSDPlus.exe
powershell -Command "Stop-Process -Name cmd"

 

[slicerwizard]

I ran DSDTune to try and teak my system. I am getting 5 second or so calls on P25. They decode - messages scroll, etc. but audio is only a few seconds. Clear though!

Could be a monitoring threshold issue. Make sure the threshold is set to 100 in VC DSD+.

When I run DSDTune I get the following error:

Invalid command line paramater '-ds0'

You're running an old version of DSDTune and it does nothing for TCP linked PSK signals anyway.

Question before my answer - does the presedence of options matter - i.e. - can the input spec come after the output spec?

Doesn't matter.

I also noticed - and maybe this a timing issue and because I am starting them all from one batch file, but I get the following error that "seems" to clear itself. Am I thinking about this correctly? Here is the output:

Mono audio decoding initiated; press Esc to exit...
TCP connect error = 10061
[No connection could be made because the target machine actively refused it]

Initiating TCP connection to 127.0.0.1:20002...

Seems like it tried to connect and then did. Not sure why the first attempt failed. Thinking because the batch file started it too fast and it wasn't ready for a connection.

Exactly. It's a non-issue.

Here's a little batch file I cobbled together via some Google searches on help sites to make stopping the running processes a little less annoying in Windows 10. Nice while tweaking settings, etc.

taskkill /F /IM FMP24.exe
taskkill /F /IM FMP24.exe
taskkill /F /IM DSDPlus.exe
taskkill /F /IM DSDPlus.exe
powershell -Command "Stop-Process -Name cmd"

And what if DSD+ is in the middle of writing a data file when you kill it?

 

[DaveNF2G]

Part of the delay in decoding is caused by using the -fa option. It takes a little time for the program to detect the protocol in use. If you specify a protocol to decode and the transmission is in fact using that protocol, then decoding should be just about instantaneous.

 

[AB9NN]

Could be a monitoring threshold issue. Make sure the threshold is set to 100 in VC DSD+.
You're running an old version of DSDTune and it does nothing for TCP linked PSK signals anyway.

Doesn't matter.

Exactly. It's a non-issue.

And what if DSD+ is in the middle of writing a data file when you kill it?

If it's writing a file - I presume there would be a corrupt file on the system or it would remain open? Should that matter? Would DSD+ start with a fresh file the next time it starts along with FMP24?

 

[AB9NN]

Changed from -fa to nothing and it seemed like it got worse. Changed back to -fa and got short audio burst. Changed to -f1 and am running now. Question on Windows 10 SOUND panel. Both Recording and Playback tabs should have VB Cable set as the default and be the only ones checked and DSD+ / FMP24 will be the ones to route the audio to my Desk Speakers while VB Cable does the routing between DSD+ and FMP24?

 

[AB9NN]

Solved. Seems to work. Put it back into scan mode and seems to be decoding. Thanks!

 

[slicerwizard]

If it's writing a file - I presume there would be a corrupt file on the system or it would remain open? Should that matter? Would DSD+ start with a fresh file the next time it starts along with FMP24?

It would work with whatever damaged groups or radios file your kill command left it with. This may not be a concern for you, but others might not care to lose thousands of IDs.

Question on Windows 10 SOUND panel. Both Recording and Playback tabs should have VB Cable set as the default and be the only ones checked and DSD+ / FMP24 will be the ones to route the audio to my Desk Speakers while VB Cable does the routing between DSD+ and FMP24?

VB Cable should be uninstalled unless you actually need it for something. Data routing between FMP24 and DSD+ should be done via TCP link.

Having VB Cable as the default device just makes life difficult - what if you play a video? The audio will go to VB Cable instead of your speakers, which is pointless.

 

[dave3825]

This may not be a concern for you, but others might not care to lose thousands of IDs.

Another reason I run out of Onedrive. Something breaks, all I have to do is boot up the laptop without wifi, find the file, and recover it...

 

[AB9NN]

It would work with whatever damaged groups or radios file your kill command left it with. This may not be a concern for you, but others might not care to lose thousands of IDs.

VB Cable should be uninstalled unless you actually need it for something. Data routing between FMP24 and DSD+ should be done via TCP link.

Having VB Cable as the default device just makes life difficult - what if you play a video? The audio will go to VB Cable instead of your speakers, which is pointless.

Thanks. Learning! If you stop the programs manually do you not run the risk of stopping them while they are doing some write function in the background that you may not be aware of? I do use VB cable for WxToImg and some other work so I will keep that. Good clarity on not needing it for this work. I did notice that when I changed the inputs and outputs on VB Cable after DSD+ and FMP24 were shut down I would get an audio burst so I was thinking something was "not quite right".

 

[slicerwizard]

If you stop the programs manually do you not run the risk of stopping them while they are doing some write function in the background that you may not be aware of?

I often see DSD+ write data and audio files as part of its shutdown procedure, so it seems to know how to write (or finish writing) when you click on an X.

 

[cg]

I right click the black Command Prompt icon in the Task Bar and choose "Close all Windows". It closes each part of the program saving things as it goes.

chris

 

[AB9NN]

When I right-click each - either the running window floating or down on the task bar - I only get "Close" - not Close "All" windows. Therefore, it only closes one window at a time and it takes quite a few clicks to close them all in Windows 10. Can it be a configuration issue?