SDR# SDR# Plug-in: Frequency Scanner updated

[TDR-94]

I'm using the SDR# DSD plugin and it's UI and the SDR# volume is set to mute and I'm getting audio anytime the SDR# squelch threshold is reached and the DSDPlus scope display is also active. I'm assuming the audio is being output by DSDPlus.

That's while sitting on a single frequency in SDR#.

When a I start the Frequency Scanner I get unsquelched noise the entire time the Frequency Scanner is running. When I stop the Frequency Scanner the noise is squelched.

 

[slicerwizard]

I'm assuming the audio is being output by DSDPlus.

Notes.txt says raw audio monitoring was added in DSD+ 1.114, so that seems unlikely.

 

[thewraith2008]

What output audio device are you using from SDR# to DSD+. (see Audio > Output)

• This really should be a virtual cable so you don't hear the tuned frequency digital signal.

When using the DSD Interface plug-in:

• Select the output audio device (preferably a virtual cable) to use with SDR#/DSD+ via the Audio Device drop-box list in the plug-in side panel.
• Set the volume to a good level for DSD+.
• Problem here is that the plug-in offers to mute the frequency that SDR# is tuned too, but this is not going to work as expected because this muting needs to be done manually for every frequency that the scanner lands on.
• The top option (to directly output in SDR#) would be the one to use with the scanner so you don't hear the digital signal.

Remember that when you pass audio from SDR# to DSD+, you need to make sure the:

• DSP options (e.g. 'Filter Audio' or any other plug-ins that alter the audio stream) are OFF.
• The SDR# volume is set to a good level for DSD+.
• Squelch is OFF.
• Other?

Latest version (v2.2.13.0) can be found here: MEGA - Download
Release post here

 

[AM909]

(kind of OT) @TDR-94: If you're using the SDR# "DSD Interface" plugin to launch DSD+, the first checkbox at the top of the UI is "Enable aux audio output", which, when checked, sends SDR# audio to the speakers (and annoyingly doesn't retain it's state between sessions, so you have to un-check it every time you start it).

I use DSD+ Fastlane and recommend getting it if you can. I have SDR# audio gain set to 50 dB, and I do use it with squelch most of the time unless dealing with a weak signal because DSD+ periodically falses on white noise, which is annoying. If your DSD+ doesn't have the audio monitoring modes, then it's not an issue for you. I necessarily disable squelch when trying to decode certain short-duration idle pulses like IDAS and LTR (not decoded by DSD+, but by LTR Analyzer) because the squelch is not fast enough to avoid chopping off most of those short transmissions.

 

[TDR-94]

What output audio device are you using from SDR# to DSD+. (see Audio > Output)

• This really should be a virtual cable so you don't hear the tuned frequency digital signal.

When using the DSD Interface plug-in:

• Select the output audio device (preferably a virtual cable) to use with SDR#/DSD+ via the Audio Device drop-box list in the plug-in side panel.
• Set the volume to a good level for DSD+.
• Problem here is that the plug-in offers to mute the frequency that SDR# is tuned too, but this is not going to work as expected because this muting needs to be done manually for every frequency that the scanner lands on.
• The top option (to directly output in SDR#) would be the one to use with the scanner so you don't hear the digital signal.

Remember that when you pass audio from SDR# to DSD+, you need to make sure the:

• DSP options (e.g. 'Filter Audio' or any other plug-ins that alter the audio stream) are OFF.
• The SDR# volume is set to a good level for DSD+.
• Squelch is OFF.
• Other?

Latest version (v2.2.13.0) can be found here: MEGA - Download
Release post here

Are these settings correct?

 

[thewraith2008]

Are these settings correct?

It's one or the other, not both.

I would go with the left image (direct SDR# output to DSD+)

• Don't enable the check-boxes in DSD Interface.
• SDR# --> Cable In --> Cable Out --> DSD+

Remember, you will not hear anything from SDR# in the speakers this way.
The audio is decoded via DSD+ to speakers.
This way is only good for digital scanning decoding, not mixed analog/digital.

I have not don't this myself so I can't really speak for how well DSD+ will work this way. This is just how I think it needs to be setup.



Latest version (v2.2.13.0) can be found here: MEGA - Download
Release post here

 

[TDR-94]

It's one or the other, not both.

I would go with the left image (direct SDR# output to DSD+)

• Don't enable the check-boxes in DSD Interface.
• SDR# --> Cable In --> Cable Out --> DSD+

Are you referring to the auxiliary audio and mute this frequency check boxes on the DSD+ plugin?

 

[thewraith2008]

Yes



Latest version (v2.2.13.0) can be found here: MEGA - Download
Release post here

 

[Bourbon]

Question about the channel analyzer. Everything in the spectrum with the exception of buttons is incredibly small for me. Even if I zoom in, everything just becomes bold, not actually larger. The noise floor stays right on the bottom. Finding peaks for fine tuning isn't hardly possible.

I'd imagine I'm over looking a setting or an adjustment. If someone could point me in the right direction, Id greatly appreciate it.



This is zoomed, and unzoomed while scanning.

 

[TDR-94]

Yes



Latest version (v2.2.13.0) can be found here: MEGA - Download
Release post here

Seems to be working. Thanks!

 

[Bourbon]

Is there a way to raise the noise floor in the channel analyzer window? I can't seem to find a setting anywhere to achieve this.

 

[EricTViking]

Is there a way to raise the noise floor in the channel analyzer window? I can't seem to find a setting anywhere to achieve this.

From the docs:

"When the channel analyser window is stretched vertically, it does not scale any part of this area.
The only thing changed is the range available for a maximum signal.
There are no plans to scale this area at this stage."

 

[EricTViking]

If I understand correctly, when you select the "Scan only memorized – exclude new" mode, the scanner will still scan the entire range of frequencies but will only stop on frequencies that are in the Frequency Manager (in frequencies.xml)?

Would it be possible to mod the plugin so that it can be made to only scan the frequencies in Frequency Manager so instead of scanning a range of (say) 500 frequencies, you could get it to only scan (say) 5 frequencies that are within the range and also in Frequency Manager?

 

[TDR-94]

I now have SDR# also working with the DSD+TCP plugin, but I hear audio from both DSDPlus and SDR# when the Frequency Scanner stops on a modulated signal. Is there anyway to only route the audio through DSDPlus or completely mute the SDR# output?

 

[TDR-94]

Problem solved. Just needed to turn the volume slider all the way down in SDR#

 

[causeway74]

If I understand correctly, when you select the "Scan only memorized – exclude new" mode, the scanner will still scan the entire range of frequencies but will only stop on frequencies that are in the Frequency Manager (in frequencies.xml)?

Would it be possible to mod the plugin so that it can be made to only scan the frequencies in Frequency Manager so instead of scanning a range of (say) 500 frequencies, you could get it to only scan (say) 5 frequencies that are within the range and also in Frequency Manager?

If there was another flag added to the list of frequencies in the FreqMan list with a yes/no value for scan, I'm sure the plugin could be adjusted to allow users to scan only pre-specified freqs. This might be rather expensive resource-wise but could be a nice feature if we could pick lets say 20 freqs of interest out of a given range.

I now have SDR# also working with the DSD+TCP plugin, but I hear audio from both DSDPlus and SDR# when the Frequency Scanner stops on a modulated signal. Is there anyway to only route the audio through DSDPlus or completely mute the SDR# output?

@thewraith2008 do you have the rights to modify the DSDTCP plugin? If I am scanning a range and I land on a DMR channel, the control state of the "mute this frequency" button is lost when scanning recommences. Would there be any way to modify the plugin so that the control state is preserved for the length of the session? In other words if the scanner stops on 453.100, press "mute this freq", my choice to mute would be preserved and reinstated the next time I land on that freq in the session. Perhaps frequencies could even be perstisted in a config file?

 

[thewraith2008]

The Frequency Scanner plug-in will only allow memorized frequencies to be stopped on if selected to do so.
It won't just scan/tune to those frequencies, that's not how this scanner works.
If you want that, use the scanning feature in the FreqMan plug-in.


Some of the posts appearing here are getting a bit of topic and really don't have anything to do with the Frequency Scanner plug-in itself.
Just because you happen to be using the scanner plug-in with whatever you are doing doesn't mean it's relevant to this thread.
Start a new thread and discuss it there.

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.



Latest version (v2.2.13.0) can be found here: MEGA - Download
Release post here

 

[peluson]

Hi @thewraith2008 ,
You could include in the log generated by the frequency scanner, if DSD+ is activated, that it also include the type of mode detected (DMR, NXDN etc...) in a column.
Thank you

 

[thewraith2008]

There is no way the Frequency Scanner plug-in can know what DSD+ is decoding.



Latest version (v2.2.13.0) can be found here: MEGA - Download
Release post here

 

[PatrickPierre73]

thewraith2008 : I'd like to ask you about your Baseband Recorder plugin, but I don't know where to post my comment.