Writing this doesn't mean that I/we don't like the new SDR# or scanning features, but 'it is what it is' for now...
Many of you, some users that I know and I myself, experience the same problems with several installations on several computers.
After the introduction of the Telerik interface it is almost not possible to run SDR-Sharp on a basic dual core system (3.1 GHz, 4GB, HDD).
In my basic install, normally I have Frequency Scanner, Frequency Manager, OmniRig Sync, DigitalAudioProcessor, Accessibility Control.
These are to find in the "Community Package with Plugins" too, as promoted on the AirSpy site and that one has the same problems.
The Airspy site doesn't tell us/me that SDR-Sharp won't work with less specs and what the new specs should be, even on my i5 SSD HD laptop some problems still exist. SDR# doesn't work stable anymore on computers at Scouting, after the introduction of SDR-Sharp Telerik version 1732. The program won't close after exiting, the screen freezes and taskmanager is needed to get rid of that frozen screen.
I/we do use the FrequencyScanner plugin often, as a kind of basic plugin in most of our SDR# versions. Even when plugins are quit and the list of plugins is made to a minimum, then problems still exist.
Sorry to say, but when installing the original 1782 version (or earlier versions) on my i5 SSD HD laptop, there are problems to find.
Even with this minimal list of plugins it goes wrong: Band Plan, Zoom FFT, Extended FFT, Frequency Manager. After 3 times starting and exiting the program, one after eachother, the 4th time starting it and it exits direct and can't be started at new. Often restarting is needed when adding plugins and seeing if they work. A complete restart of he computer does the job, but then it all starts at new, before 1716 this was no problem and it all worked fine.
Hope the team will do many more testing and maybe give us a choice to go back to the classic layout too.
Here we are used to that classic one and standard list of plugins, and some users with less view capabilities need a trustful layout combined with some external switches (with use of the Accessibility plugin).
Again, sorry for now, we'll stick to 1732 after all the changes and problems we experience.
Many of you, some users that I know and I myself, experience the same problems with several installations on several computers.
After the introduction of the Telerik interface it is almost not possible to run SDR-Sharp on a basic dual core system (3.1 GHz, 4GB, HDD).
In my basic install, normally I have Frequency Scanner, Frequency Manager, OmniRig Sync, DigitalAudioProcessor, Accessibility Control.
These are to find in the "Community Package with Plugins" too, as promoted on the AirSpy site and that one has the same problems.
The Airspy site doesn't tell us/me that SDR-Sharp won't work with less specs and what the new specs should be, even on my i5 SSD HD laptop some problems still exist. SDR# doesn't work stable anymore on computers at Scouting, after the introduction of SDR-Sharp Telerik version 1732. The program won't close after exiting, the screen freezes and taskmanager is needed to get rid of that frozen screen.
I/we do use the FrequencyScanner plugin often, as a kind of basic plugin in most of our SDR# versions. Even when plugins are quit and the list of plugins is made to a minimum, then problems still exist.
Sorry to say, but when installing the original 1782 version (or earlier versions) on my i5 SSD HD laptop, there are problems to find.
Even with this minimal list of plugins it goes wrong: Band Plan, Zoom FFT, Extended FFT, Frequency Manager. After 3 times starting and exiting the program, one after eachother, the 4th time starting it and it exits direct and can't be started at new. Often restarting is needed when adding plugins and seeing if they work. A complete restart of he computer does the job, but then it all starts at new, before 1716 this was no problem and it all worked fine.
Hope the team will do many more testing and maybe give us a choice to go back to the classic layout too.
Here we are used to that classic one and standard list of plugins, and some users with less view capabilities need a trustful layout combined with some external switches (with use of the Accessibility plugin).
Again, sorry for now, we'll stick to 1732 after all the changes and problems we experience.
