You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running the latest version, compiled from source under Linux Ubuntu 20.04.
I have selected a scanning range of 144-146MHz.
The scanner is scanning at 20MHz with 15MHz lowpass filter for bandwidth as normal.
It is scanning 151Mhz then 156Mhz back and forth.
At such a low bandwidth (2 MHz) this is unnecessary. It could happily scan the entire bandwidth at 4MHz and take up much less CPU and USB.
I understand completely the reason it is scanning 151.5MHz, with 15MHz bandwidth this would scan 144MHz through 159MHz.
Scanning at 156.5MHz as well does not cover any of the wanted bandwidth, instead it covers 149MHz through 164MHz and is simply wasting resources.
I would suggest that if the scan range fits inside the bandwidth then reduce the bandwidth until it just fits and then stop changing frequencies. This will save CPU usage and USB bandwidth requirements.
The text was updated successfully, but these errors were encountered:
I am running the latest version, compiled from source under Linux Ubuntu 20.04.
I have selected a scanning range of 144-146MHz.
The scanner is scanning at 20MHz with 15MHz lowpass filter for bandwidth as normal.
It is scanning 151Mhz then 156Mhz back and forth.
At such a low bandwidth (2 MHz) this is unnecessary. It could happily scan the entire bandwidth at 4MHz and take up much less CPU and USB.
I understand completely the reason it is scanning 151.5MHz, with 15MHz bandwidth this would scan 144MHz through 159MHz.
Scanning at 156.5MHz as well does not cover any of the wanted bandwidth, instead it covers 149MHz through 164MHz and is simply wasting resources.
I would suggest that if the scan range fits inside the bandwidth then reduce the bandwidth until it just fits and then stop changing frequencies. This will save CPU usage and USB bandwidth requirements.
The text was updated successfully, but these errors were encountered: