If using the latest version (v2.2.8.0), the beep indicates a problem with frequency tuning.
- Request made to SDR# to tune to frequency, scanner checks that expected frequency has been tuned too. If not then beep.
Why is it occurring?
Possibly the 'Detect' value is too low (and the scan-rate is too quick) not giving the SDR#/dongle enough time to tune.
Call to RTL driver (if using RTL dongle) did not return successfully. (did not tune). The SDR# RTL frontend is a bit on the simple side when handling driver errors.
May occur when CPU load is high.
Some other reason that I haven't determined.
I added beep to detect when it occurred, but it rarely did for me so I have not investigated it more. This maybe due to the fact I use a custom SDR# RTL frontend/driver.
The beeps where used for different things in older versions, I don't remember what they are now. (maybe one was when Now play file write error)Ok,thanks.
I'm currently still using (v2.2.5.0) with v1716 and the Airspy R2, but I'll check those suggestions and see if I can narrow down when and if it happens again. Could setting the red line just below 10 also cause this?
Try looking at the option 'Noise protection delay' ON/OFF values.I've noticed that when I pause the Frequency Scanner on a frequency, that before every transmission, there is a short period/burst of noise right before you hear the beginning of the audio. Is there a setting that prevents the noise burst before the audio? I tried adjusting the Auto Mute controls,but that doesn't seem to make any difference.
If I don't use the Frequency Scanner and just have a frequency manually tuned, in SDRsharp, with the squelch setting adjusted, there is no burst of noise before every transmission like there is when the same frequency is paused in the Frequency Scanner.
Try looking at the option 'Noise protection delay' ON/OFF values.
OFF: This will delay the un-muting action of the SDR# mute after the scanner stops on an active frequency.
ON: This will delay the muting action of the SDR# mute after signal activity was seen.
'Noise protection delay' default ON/OFF values are 5/3.
From the issue your seeing, adjusting the OFF value should be all that is needed.
The 'crashes' can be more noticeable on NFM rather than AM when adjusting these values as AM can be a 'quieter'.
Should be noted that these options won't help if the 'crashes' are occurring on a frequency that is a repeater downlink and where repeated 'overs' are heard with the 'crash'. This issue is occurring on the repeater RX radio and transferred to the TX radio.