-
Notifications
You must be signed in to change notification settings - Fork 258
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 offset not saved in Session file #235
Comments
This was actually removed on purpose because it conflicted with the new device settings saves (offset is saved per-device in regular or named configurations). There will need to be some cleanup and rework before the named config could be swapped at runtime or saved to the session; for now you can use named configs to keep things separate, for OSX it's:
Cheers! |
When i load a new config it copies the default config into the new file. config.xml -> config-SDRplay.xml |
This is what you get when you save a session.
This is the generated session file.
Why not save all the data into one session/config file? Like this you can create use case based session files. |
For now the config and session are separate entities; they can't both contain device settings at the moment because device settings are not interchangeable at runtime and won't be until some related issues such as refreshing devices is also resolved -- in the future it should be possible to save device settings but we'd need to decide if that's even a thing we should do and what settings make sense. For this specific issue we actually need to debate whether the offset needs to be saved per-device per-session. My primary argument is that to keep the offset with the per-device configuration is simply because with my setup here I move up-converters between devices; after changing devices I would be required to load, reset the offset and re-save each related session file with the updated device offset. Moving additional device settings into the session would further fragment the ability to maintain the current configuration state in one place. Additionally if I save the offset with the session file and disregard the device; jumping between multiple devices with different up-converter configurations and loading sessions would result in that offset needing to be adjusted each time the session was loaded for a different device. As it stands now I can set the up-converter offset once (per-device, per-configuration file) and any sessions adhere to the current device configuration and there's no chance of fragmentation or mismatching device settings. If you're simply attempting to use offset as 'PPM' adjustment that's partly my bad -- it needs to be implemented in SoapySDRPlay as it's currently missing -- I just haven't had the need to adjust PPM on my SDRPlay so far it's been spot on :) |
Going to close this one up, my rant was based on some false assumptions of the use case here (saving IF offsets I believe); I think we're going to cover this off in #70 and it's business as usual. |
Not there...
The text was updated successfully, but these errors were encountered: