Plug-ins versus SDRSharp.exe config

[danesgs]

I know "Thick as a brick" as Tull would say. I guess I just am doing something wrong. I add some lines to "plug-ins" and they work, I add others and they cause SDR console to barf. I have the DCS and DSD interface working, the frequency manager and scanner working. Some that I add just don't want to play such as CTCSS or adding more VFO's. etc. Call me "old school". My only programming ever done was inputing HEX code into a ET-18 robot when working for Heathkit in the 1980's or renaming garbage ASCII files to .com's or EXE's and running them on old 8088's to see what would happen. Yes, I know dangerous mindset LOL. I plan on writing an ebook on SDR dongles one of these days when i have it figured out.Its a lot of fun to tinker with. I guess my next step is to really look at both files and see the pointers to what they are trying to do. All the .DLL's are in the right locations (I think). I am using build 1328. "Levelmeter" works great BTW. hats off to all the people who write these things. Happy Holidays! Speaking of "Old School" I once played some James Brown while imaging a bunch of Dell laptops in a basement for DLA and the cat i was with said he was "Old School", well I LIKE Old school! Maybe cause I am.....
KJ4DGE

 

[DaveNF2G]

I can't offer much besides agreement and sympathy. I have noted the same inconsistency among plugins. The ones that have "installers" tend to be the best behaved. Some require more than just the sdrsharp.exe.config file to be modified.

 

[Flatliner]

You wrote "SDR console", but I'm assuming that you meant SDR# (SDR Sharp). "SDR console" belongs to the SDR-Radio.com program, generally a very well-behaved application.

SDR Sharp, on the other hand, relies on several third-party plugins to be particulally useful. Unfortunately, in my experience, these result in SDR Sharp more often crashing for one reason or another, when using several of these, otherwise, very useful plugins.

The issues may be bugs in the plugins themselves, issues with the SDR# API, or/and poor error handling of SDR# of detected problems, though probably a combination of all.