-
Notifications
You must be signed in to change notification settings - Fork 573
Comparing changes
Open a pull request
base repository: gqrx-sdr/gqrx
base: master
head repository: sultanqasim/gqrx
compare: master
- 11 commits
- 28 files changed
- 3 contributors
Commits on Sep 27, 2023
-
Configuration menu - View commit details
-
Copy full SHA for a6864f3 - Browse repository at this point
Copy the full SHA a6864f3View commit details -
Configuration menu - View commit details
-
Copy full SHA for d422f34 - Browse repository at this point
Copy the full SHA d422f34View commit details -
int d_fftWindowType; bool d_fftNormalizeEnergy;
Configuration menu - View commit details
-
Copy full SHA for 51b05c5 - Browse repository at this point
Copy the full SHA 51b05c5View commit details -
Fix antenna-related crash on config load
Gqrx may crash by not catching the exception when src->set_antenna call fails. This is the case when devices are switched and new device does no have an antenna, that is saved in a config file. Catch the exception and read back correct antenna name.
Configuration menu - View commit details
-
Copy full SHA for 45bb9e7 - Browse repository at this point
Copy the full SHA 45bb9e7View commit details -
iq_tool: prevent accidental change of hw freq
...while playing back IQ file. Problem: It is possible to change the center frequency while playing an IQ file. In this case the real file center frequency does not get shifted to a correct position, so the spectrum plot/waterfall becomes shifted from actual played frequency, bookmarks become not valid, freqCtrl shows wrong frequency, plotter shows wrong frequency and so on. This commit changes frequency setting logic to be more staraightfroward and consistent. Independent of frequency change event source (freqctrls, plotter, remote) do the things in a same way: calculate new center and offset, taking into account the fact, that the center frequency may be loked due to IQ file playback, set the new frequency on a receiver side, then update all GUI controls to reflect changes. Enforce new frequency limits on the plotter side when IQ playback is started.
Configuration menu - View commit details
-
Copy full SHA for 6695c27 - Browse repository at this point
Copy the full SHA 6695c27View commit details -
IQ tool: disable unused controls when recording/playback is in progress.
Changing IO devices and loading/saving settings does not look like good thing to do while recording/playing an IQ file. Disable seek slider during recording as it has no function in this state. Disable file list and directory selector during recording/playback.
Configuration menu - View commit details
-
Copy full SHA for 5f7d711 - Browse repository at this point
Copy the full SHA 5f7d711View commit details -
IQ Tool: add sampling rate and frequency inputs to add ability to pla…
…yback arbitrary named files correctly Recalcute playback time on sampling rate change. Disable inputs during playback/recording
Configuration menu - View commit details
-
Copy full SHA for b45ac79 - Browse repository at this point
Copy the full SHA b45ac79View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4566d09 - Browse repository at this point
Copy the full SHA 4566d09View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6ce986b - Browse repository at this point
Copy the full SHA 6ce986bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 1819195 - Browse repository at this point
Copy the full SHA 1819195View commit details -
dockfft: allow shorter waterfall durations
Note: this will cause saved configurations with waterfall durations other than auto to be interpreted incorrectly, as it changed the indices for the various waterfall durations.
Configuration menu - View commit details
-
Copy full SHA for e1f8aed - Browse repository at this point
Copy the full SHA e1f8aedView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff master...master