The problem: I remarked we have been spending a lot of time lately on problems that could be solved with much less effort if we all agree to adopt a minimum of discipline. As this mailing list grows, there will be less and less people interested in reading about problems they have already discussed, solved, and beaten to death in this same mailing list. Here's a quick reminder for everyone having problems with SDR software and computers. Unless you describe exactly what you are doing, in which context, with the exact hardware and software configuration, the odds of someone giving helpful advice are close to zero. The social media (and mailing lists) have the undesirable ability to amplify noise because there are naturally more people who have opinion than people who have actual knowledge. So please, read this post carefully. What do I do first? Use common sense. Determine if it is a support topic or a general discussion: Airspy Hardware related => Contact the support; Everything else goes to the list. For support related questions, prepare your list of "Steps to Reproduce" and send it by mail to The Support. For general discussion/best practices, try to avoid duplicates: Use the search bar to find an existing topic/answer/advice that solves your problem or improves your life. Don't jump on other's threads. Statistically, "Mee too" is never an actual "Mee Too". You are just making things difficult for all. Use separate threads for separate problems. A "segfault" has nothing to do with the noise from your Plasma TV or PC PSU. Try to keep the content technical. People from different cultures will read and ignore your untranslatable joke, but will definitely understand the tech stuff. How to report a problem: Steps to Reproduce Be precise Include exact data used during testing for easy reference, including hardware, OS and user software versions The steps have to be in the exact order Mention pre-requisites when applicable: Software dependencies, glibc, modified kernel, etc. Do not write composite steps. The devil is in the detail. Always recheck your steps to reproduce on a new system with the default configuration Make sure the sentences are short and unambiguous Thanks for reading to the end!

FMSuite 2.2 can be downloaded from http://www.freqmgrsuite.com/ using the link at the top right of the page. As always, feel free to email me or make a comment on the web site above if you have questions or issues. Special thanks to prog, jdow, and Edward McDonald for suggestions and directions, and to beta testers Ignacio, Paolo, and Edward for their valuable feedback. Change Log All Plugins Theming has been implemented where possible. Note that only Dark Mode / Light Mode settings are used, not individual colors, due to compatibility issues with some Microsoft controls. Improved the reliability of multitasking. Replaced obsolete or deprecated Microsoft features with current technology. Replaced icons and images that would have been invisible in Dark Mode themes. Fixed the case where permissions to file "FMSuiteException.txt" was denied. Replaced tab controls with radio buttons because theming is incompatible with Microsoft tab controls. All software was upgraded to the current Microsoft .NET Core 5 platform. Data Tools Upgraded the Data Tools Zip file processing to a built-in Microsoft function. Removed the "Custom" delimiter option and replaced it with the "Pipes" option due to reliability issues. Frequency Manager + Scanner Moved Scan Decisions and Frequency Data Display plugins out of Frequency Manager + Scanner and into their own plugins. Removed Scan Decisions and Frequency Data Display options from the Preferences dialog as they are now defunct. Removed the Automatic Frequency Rejection feature in favor of new features in SDR#. Fixed a case where the scanner could get stuck if the radio doesn't change frequency when requested. Changed the "Locked" or "Lock" labels to "Ignore", "Ignored", or "Ign" to remove confusion with the word "Lock" as used by hardware radio scanners. When scanning sometimes a radio will not tune to a requested frequency. To indicate this an error popup will appear and recommend actions. It is unclear whether this issue is caused in SDR# or in the radio.

Check the latest SDR# release with a new UI rendering architecture that supports layer composing from multiple plugins using multiple threads. These changes bring a 265% improvement in the UI processing time on average. The plugin API is still the same, but the custom layer painting callbacks will be run from different threads, not just the main UI thread. The resulting *scalability* allows even more features to be enabled at the same time without compromising the user experience. If some third party plugin misbehaves, it may be time to update it, but in general, the change is transparent for most plugins. Get the update from: https://airspy.com/download

*Usage:* just extract it in SDR# folder replacing the older file and run it as always.