I'm grateful this discussion is going on. This was my aim when i opened the subject "SDRplay and SWL usage".
This is a "large" argument to discuss and it is open to any topics related to "listening" with SDRplay.
I feel the discussion -- finally -- is now taking off... very good!!!
My comment about the latest 2 or 3 post about ppm correction... absolutely agree!
This is an other issue about sdr#-sdrplay-plugin (currently -- and
for a long time -- v1.3 build 1014).
I wrote to sdrplay team about other problems. Mainly the fact that the sdr# plugin works in a strange way different
from other plugin we use with rtl-srd/funcube and so on... My issue at that time was mainly that if you use different sampling rate
you do not fulfill the available space on the screen, you have the frequencies compressed in a little portion, so you need to use zoom, but zoom is not saved from time-to-time in sdr#, you need to re-set zoom from run-to-run of the program, an you do not have a numeric figure of the zoom in sdr# so from run-to -run is not easy to have reproducible
"shapshot" (suppose you want to take regular snapshot of a signal to see changes, and so on).
Etc. etc.etc. They kindly answered they will take into account my suggestion for the next release...
So to summarise according to me there are 3 big issue on the table:
-- ACG control sometimes is a "pain"
-- ppm correction missing... why sdrplay didnt SIMPLY copy what other have made before?
-- fulfillment of the waterfall/spectrum specially for the 200/300/... khz BW used for swlling
All that said, I add that I (and I suppose all of you) I am perfectly clear that the plugin is offered free of charge etc. etc. etc. and that sdr# is offered free of charge etc. etc. etc. and in the end no one is obliged to give us something better that what we already have...
please, try to excuse me for my english...