Skip to content
This repository has been archived by the owner on Oct 27, 2022. It is now read-only.

Pause recording when signal is below squelch threshold #4

Open
wants to merge 16 commits into
base: master
Choose a base branch
from

Conversation

GeoNomad
Copy link

@GeoNomad GeoNomad commented Apr 5, 2015

Useful for monitoring channels with infrequent transmissions such as ham repeaters or fire department communications.

If squelch is 0, no change.

Also set help screen to normal window instead of maximized. (A personal preference, I guess).

Added signal strength bar graph.

Changed squelch to operate of damped level for smoother operation.

Added keyboard shortcut m to mute volume.

GeoNomad added 8 commits April 5, 2015 07:16
If recording and the squelch level is set, the recording will not
include the noise between transmissions. Good for monitoring
infrequently used channels such as ham repeaters and fire department
communications.
and remove commented out code
Pressing m or M reduces volume to 0.
Signal Bar shows signal strength.

Changed squelch to operate on damped signal level. Quieter when set
close to trigger level. Doesn't drop out on weak signals.
Shows signal strength bar graph.
fighting cache, I think
@jtarrio
Copy link
Contributor

jtarrio commented Apr 6, 2015

Yes, I forgot to make squelch work for recordings too (my previous try at squelch worked in a different way that muted the audio in the recording automatically). I'll make a few experiments to ensure that there's a bit of silence in between separate transmissions, because if it stops recording as soon as the audio is squelched, the resulting recording could be quite frenetic, with all those quick-witted, fast-talking cops and firefighters :)

@GeoNomad
Copy link
Author

GeoNomad commented Apr 6, 2015

The latest version of my squelch uses a dampening calculation to prevent the quick on and off pulsing of the squelch. Real radios sometimes have time delays for when to shut the receiver off again. There are many ways to skin this cat :)

GeoNomad added 8 commits April 6, 2015 15:54
Prelude to a preset scanning function.
Prelude to preset scanner.
Clicking on the signal strength bar graph now sets the squelch level.

The signal strength can be displayed numerically by hovering the mouse
over the signal strength bar graph.
1. Added squelch to the parameters saved with each preset station.

2. Changed default checkbox when importing presets to show "Delete these
presets" with boxes prechecked. It was not intuitive before that it
would not delete the current presets unless the box was manually
checked.
This use assumes that each file is a different set of presets most of
the time. Not an overlay.

3. Display the squelch setting saved in the preset manager.
1. PgDn now selects the previous preset in the list.

2. f keyboard shortcut now works. (was in help but not working)

NOTE: using PgUp or PgDn too quickly can cause multiple decoder
instances. Looking for a good way to block this...  For now, users
should be careful.
A rudimentary test of preset scanning. Shift-PgDn will start a scan of
the preset list. If the signal exceeds the squelch level, scanning will
pause.

Just a kludge for testing. But it seems to work, surprisingly.
Click on "Squelch:" to temporarily open squelch and monitor frequency.
Preset scanning stops.
Click again to resume preset squelch setting and continue scanning
presets.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants