Skip to content
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

Frequency doesn't save/reload correctly #606

Closed
Rua opened this issue Jan 23, 2022 · 3 comments
Closed

Frequency doesn't save/reload correctly #606

Rua opened this issue Jan 23, 2022 · 3 comments

Comments

@Rua
Copy link

Rua commented Jan 23, 2022

With center tuning enabled, if I tune to a certain frequency, say 90.9 MHz, and then exit, the frequency is correctly saved in config.json. But if I then start SDR++ back up again, the frequency is slightly off, 90.904 in my case. It's not restoring the saved frequency correctly.

With center tuning disabled, config.json does not even contain the correct frequency. If I center at 90.9, then tune down to 90.7, and exit, config.json will contain 90.9 instead of 90.7, so it seems to be saving the center frequency rather than the tuned frequency. Reopening SDR++ will then put it on 90.904 as above.

@AlexandreRouma
Copy link
Owner

the frequency saved in the config.json is NOT the frequency your VFO is at. It's the center frequency.
THe offset of each VFO is stored separately.
The frequency soetimes being off after a restart is a known issue

@Rua
Copy link
Author

Rua commented Jan 23, 2022

Then it seems that it's not restoring the VFO frequency if center tuning is disabled, but rather setting the VFO to the center frequency.

@AlexandreRouma
Copy link
Owner

AlexandreRouma commented Jan 23, 2022

The frequency soetimes being off after a restart is a known issue

with some sources they start out at a lower samplerate which causes the vfo manager to put the VFOs back in view

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants