-
Notifications
You must be signed in to change notification settings - Fork 545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion to change USB/LSB step size #920
Comments
I had a look back at the commit history to see how the tuning step has evolved. Originally the tuning step was 10 Hz for all modes. Then a72891b (included in version 2.2) implemented per-mode tuning steps:
And finally, SSB was changed to 100 Hz and Demod off to 1000 Hz in c916933 (included in version 2.4). I'm not sure what motivated the change, but perhaps 10 Hz was too low to allow convenient tuning with the mouse wheel. It also seems there was a preference to use powers of 10, which have the benefit of only changing one frequency digit. (I'm not sure this is important, though.) Reducing the SSB step to 50 Hz seems like it might be a reasonable choice since it's not too much lower than the long-standing 100 Hz step, but it still allows a tuning error of ±25 Hz which is quite noticeable to my ear. What do you think about going back to the old 10 Hz step? I'm not convinced that making the tuning step user-configurable is worth the added complexity, so my inclination is to either reduce the tuning step (to 50 or 10 Hz) or leave it untouched. |
Sometimes I want 10Hz SSB tuning step, but more often I want 500Hz SSB tuning step. |
I want to make per-mode tuning step user-configurable, not only SSB. |
I suggest to change the frequency step size for USB and LSB from 100 Hz to 50 Hz.
This makes a noticable improvement when tuning signals for best voice quality.
I make this change every time I download the software, in file src/applications/gqrx/mainwindow.cpp:
case DockRxOpt::MODE_LSB:
...
click_res = 50;
(same for USB)
Of course even better would be to have some setup of custom step size per mode in the user interface but that would involve more work.
The text was updated successfully, but these errors were encountered: