SDRuno Squelch Function (VID535)

[@gerfmon1]

Wish SDRUNO or one of the other SDR software packages would implement a "voice squelch" that would activate upon hearing human speech. A lot of commercial and military receivers use this method for squelch on HF frequencies. It generally does a good job of keeping static crashes and other noises from breaking the squelch threshold, while allowing even weak voice signals to be heard. I have an old Icom marine transceiver with voice squelch. I set it on a military HF frequency, flip on the squelch, and don't hear a thing until someone actually talks.

[@TinyBigJacko]

Very useful, Steve. Thank you. Makes so much more sense now that I understand the differences in the subtle details that I'm looking at when I adjust squelch. A thought occurs, though... If there is a fixed (or at least calculable) relationship between firstly the width of the FFT bins and the power-level evident in them, secondly, the width of the VFO filter and the power-level evident in it, and thirdly the power-level figure that the squelch control is using as its threshold, then would it not be possible to have the display (and/or the squelch line) be automatically converted to work or at least show, at the level appropriate for the currently-chosen bin or VFO settings? In essence, to hide all this bin-width related DBm difference with a bit of GUI magic and on-the-fly behind-the-scenes conversion in SDRuno's code, so that we're left with an interface that actually **does** have a squelch-line that matched the displayed noise-floor on the current SP1 window? That would make the squelch line's usefulness so much greater, in my opinion, and I think it would make life so much easier for those users (like me) who have often wondered 'why doesn't the squelch line match up with the noise I'm seeing', and who (like me) have probably taken more than a year to remember to get around to looking it up and discovering your fantastic explanation? :) Now that I know what's occurring, I can make rational decisions based on some known factors at last, of course, so your explanation is still valid and helpful. I just can't help thinking that this is where the UX side of GUI design kicks in; intuitively, people are going to think 'plonk the line just above the noise'... Question is, can the 'numbers' behind what you've so deftly explained, be condensed into code to put that line where our brains tell us it should be, per display-setup per session, rather than as dictated by the raw numbers out of the box, from whatever the squelch circuit is fed from? My codemonkey brain tells me probably yes, but like so many things, without knowing the codebase, I can't tell for sure, so will shy very clear of saying "just do this", because I know how annoying that is! :D 73

[@ansomeBob]

Very interesting, can we have more "Under the Hood" sessions, please? 1080p would also help us read the small detain in the various windows. Many thanks, keep up the good work, I'm loving my new radio.

[@KurtBergNielsen]

Thankyou