DSDTCP - SDR# Plugin

[causeway74]

From @thewraith2008
All I will say about DSDtcp plug-in here is I have not don't really played around with it.
I did add a feature the the DSD Interface plug-in that has a 'Always mute' option which may be useful when scanning digital frequencies.
As I said, start a new thread and I'll be happy to discuss it there.


I use DSDTCP plugin to scan various ranges. Some frequencies in those ranges have DMR traffic and I will use the "mute this frequency" button to kill the sdr# audio and instead have the audio output from dsd+ for that channel. The problem is that when scanning resumes, the mute state of the previous channel is lost so I need to hit "mute this frequency" in the DSDTCP plugin window every time. There is an "open list" control in the plugin but this doesn't seem to be operational. Ideally a config file could store the muted digital channels in the background, and the button state be restored from that during scanning. Either a session memory for mute state or a permanent state via config file could be nice. I used to use DSD interface plugin but the DSDTCP seems much simpler.

 

[thewraith2008]

The DSD Interface and DSD TCP are basically the same plug-in, the only real difference is how the source data is served to DSD+.
In DSD Interface it's via a virtual cable and DSD TCP is via TCP.

The 'Mute this frequency' and 'open list' both worked when I tried it.

As I mentioned, I added the 'Always mute' to DSD Interface but I have now added it to the DSD TCP plug-in.

I have made both DSD Interface and DSD TCP plug-in available via the usual place where I have all the updated plug-ins stored. (see below)

I have not done much with these plug-in in awhile and they are provided as-is.

• They are updated with fixes and additional features from the standard version
• Both plug-ins are ONLY for DSD+ v1.101 Public release. (DSD Interface will work (limited) with Fastlane versions but only for v2.212)
• May work with newer versions of SDR# but this is not guaranteed (also may have issue with small audio buffer SDR# now uses)
• Will need to re-configure settings as they use different prefix settings keys
• These plug-ins have not been fully tested and may not be 100%
• These plug-ins are not the preferred way to interface DSD+ with an SDR. (use FMPx + DSDPlus)
• These plug-ins should be considered end of life.

Download - see relevant folders for each plug-in
NOTE: Use 7zip or WinRAR to extract files from the .7z file and read the .PDF or TXT file for installation and usage of files with SDR#.
NOTE: Don't select the Download as ZIP option in MEGA, just select standard download.

 

[causeway74]

Thanks @thewraith2008 - your work on this is absolutely brilliant. Will come back with feedback after some testing.

 

[TDR-94]

It's not working for me. I've tried it on v1716 and v1784. At first, without the Airspy R2 connected, I could open SDR# and then configure the DSD_tcp plugin. Now it doesn't matter if the Airspy R2 is connected or not. I can't open the DSD_tcp configuration at all or start it. I just get the following error, everytime I try to open the configuration.



If I install the original dsd_tcp plugin again, everything works like it did previously with it. No errors.

 

[thewraith2008]

Hello,

I just tried fresh installs of v1716 and v1784 on Windows 7 (32 bit) with no problem.

• No SDR.
• Add 2x DLLs and MagicLine to Plugins.xml.
• Start SDR#.
• Click 'Configure' and opened as expected.
• Set location of DSD+.
• Click 'Start DSD' and DSD+ opened as expected.
• Added Airspy R2 and started playing and repeated above with no issue (and DSD+ decoded OK as well).

What are the "Details" from the error? (see button from your image)

If you are using Windows 10 could there be an issue with the firewall blocking the TCP connection.

 

[TDR-94]

Hello,

I just tried fresh installs of v1716 and v1784 on Windows 7 (32 bit) with no problem.

• No SDR.
• Add 2x DLLs and MagicLine to Plugins.xml.
• Start SDR#.
• Click 'Configure' and opened as expected.
• Set location of DSD+.
• Click 'Start DSD' and DSD+ opened as expected.
• Added Airspy R2 and started playing and repeated above with no issue (and DSD+ decoded OK as well).

What are the "Details" from the error? (see button from your image)

If you are using Windows 10 could there be an issue with the firewall blocking the TCP connection.

Tried reinstalls, no difference. I went back to using the original dsdtcp, so I don't have the details from the error. The TCP connection works fine with this version and FMPA + DSDPlus.

 

[thewraith2008]

Strange.

I just fired up the Windows 10 (64 bit) and tried SDR# v1716 and the DSDtcp plug-in and all was good.

Without the details from the error you saw, I can't do much to look into the problem.

• All I know is it what the pop-up said "Input string was not in a correct format"
• I don't know where that error came from. ('Details' would have probably shown this)

 

[TDR-94]

Are you adding the new MagicLine in with the original dsdtcp MagicLine, to the Plugins? I just replaced the original with the new one. Is there a particular order in the Plugins that's required to place the DSDtcp MagicLine?

 

[thewraith2008]

The two MagicLines are the same because they are the same plug-in.

Adding the line twice in Plugins.xml did not cause any problems here.
Adding the line in different places in Plugins.xml did not cause any problems here.

You should have been able to replace the 2 DLLs and it should have worked.

• The Pack.dll should be exactly the same anyway.

You can look in Event Viewer to see last crash SDR# had related to that: "Input string was not in a correct format"

 

[dave3825]

It was mentioned in plug in summary that,

DSD TCP [v1.0.1.0]
- Use SDR# as input source via TCP to DSD+ and a UI configuration. (support ONLY for DSD+ v1.101 public release)

Is that still the case or does it work with Fastlane now too?

 

[thewraith2008]

The DSDtcp plug-in is only for DSD+ public release v1.101.
- The TCP output from this plug-in is not compatible with fastlane releases of DSD+.

I messed around with the DSD Interface plug-in and using DSD+ Fastlane (via audio input) but this was awhile ago and I saw no real reason to continue with it as most of DSD+ FL features only work when using FMPx + DSDPlus.

 

[TDR-94]

The two MagicLines are the same because they are the same plug-in.

Adding the line twice in Plugins.xml did not cause any problems here.
Adding the line in different places in Plugins.xml did not cause any problems here.

You should have been able to replace the 2 DLLs and it should have worked.

• The Pack.dll should be exactly the same anyway.

You can look in Event Viewer to see last crash SDR# had related to that: "Input string was not in a correct format"

I'm running system checks and repairs on my PC. To try and rule out any Windows update issues, that might have incurred during an update Tuesday.

 

[TDR-94]

System check did find some files that needed to be repaired. I haven't re-tried the DSDtcp plugin yet.

 

[TDR-94]

Still a no go. Here are the details.

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseDecimal(String value, NumberStyles options, NumberFormatInfo numfmt)
at SDRSharp.DSDtcp.DialogConfigure.StringToDecimal(String value)
at SDRSharp.DSDtcp.DialogConfigure.ParseArguments()
at SDRSharp.DSDtcp.DialogConfigure..ctor(DSDPanel panel)
at SDRSharp.DSDtcp.DSDPanel.ConfigureButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

[thewraith2008]

Hello,

In your SDR# folder (where crash is occurring. e.g. v1716) is a file called 'SDRSharp.exe.Config'.
Open it with notepad and find the following two entries:

• <add key="DSDtcp.Arguments" value=......."
• <add key="DSDtcp.AuxArguments" value=......."

Copy both lines exactly and post them here please.

 

[TDR-94]

Here you go.

<add key="DSDArguments" value=" -v2 -O NUL -I0 -i1 -o1 -g0 -u3 -dr0 -dh0 -ds64 -dd10 -dv20 -M15 -fa" />
<add key="DSDAuxArguments" value="-wsl10.10 -wss200.300 -wsp100 -wel50.50 -wes400.500 -weh15 -wcl90.90 -wch15" />

 

[TDR-94]

Nevermind, those were the wrong ones. Here are the DSDtcp ones.

<add key="DSDtcp.Arguments" value=" -v2 -O NUL -I0 -i20001 -o2M -g0 -u3 -dr0 -dh0 -ds64 -dd10 -dv20 -M15 -fa -UA50 -UI50 -e -weh15 -wch15 -E" />
<add key="DSDtcp.AuxArguments" value="-wsl10.10 -wss200.300 -wsp100 -wel50.50 -wes400.500 -wcl90.90" />

 

[thewraith2008]

Hello,

Thanks for the info.

The "DSDtcp.Arguments" line is where the problem is occurring in the plug-in.
The line itself is OK, it's the parsing of the 'CH' option for the 'Output audio device'. (-o2M)
Anything but 'Auto' will see this problem.

You would have opened the 'Configure' least once and set it but after you closed it, you would not been able to open it again.

I've copied this code across from the DSD Interface plug-in so it's most likely seen there too.

Also I noticed that the -O option for the WAV output file did not allow for the 'M' or 'S' switches either.
- Will try and use -O M test.wav instead of -OM test.wav
- This would see DSD close straight away as it would have been invalid if you tried to use those switches.)

I'll fix and uploaded it as so as I get a chance.

 

[thewraith2008]

I remember now.

Plug-in would not work with audio device indexes > 9, I fixed that but forgot about the M,L,R switches that could be used with the -i/-o option.
Fiddlesticks.

 

[TDR-94]

Glad to help. Thanks!