Plan for sdr# plugin
Is there any plan to update sdr# native plugin v2.2 ?
(if I remember well 2.2 do not include the enhancements -- some or all -- around mirics api 1.8.1).
This forum is now suspended and will not accept any new posts or account registrations. For technical support relating to SDRplay hardware or software, please open up a support ticket via www.sdrplay.com/support
I find this statement rather unsettling. Whether or not the demand seems low and why is subject to interpretation and guesswork. Maybe the SDR# users among your customers are just patiently (and silently) waiting, having purchased the RSP in full confidence that this situation will be resolved soon. Or maybe you are seeing a declining demand because an increasing number of SDR# users is not even considering the RSP anymore due to the (seemingly endangered) SDR#1400+ support.Tech_Support wrote: demand for SDR# amongst our customer base seems to be quite low now, we feel compelled to dedicate our limited development resource to areas that will bring our users the most benefit overall
Dear Tech_Support, I think I did understand that part but this...Tech_Support wrote:Dear 13dka,
I think there may be a little misunderstanding here. The original post related to an update to the plugin to unlock the full feature-set of current SDRplay API, namely I/Q compensation and DC offset correction.
... is shocking news to me. I obviously misinterpreted what I saw in the various discussions about that elsewhere and thought SDR# just broke compatibility with the old ExtIO plug-in and you providing an interim version that kind of works with SDR# made me think that you are working on restoring full compatibility with SDR#. I'm afraid I'm not the only or the last guy who got that wrong.Tech_Support wrote:Unfortunately, there is NOTHING that we can do to restore the lost functionality associated with various features of SDR# (such as support for some popular plugins) that was lost after release 1400.
That's what I heard and the very reason why I never considered buying an Airspy. But later it looked to me (maybe I just dreamed that) like Youssef changed his mind, your work on a (somewhat) compatible plug-in reinforced that impression.Tech_Support wrote:The reason for this is that SDR# was re-coded to exclude various pieces of hardware, the SDRplay RSP1 being one of them.
Well, I even respect the right of anyone to make a complete <expletive> out of himself. You certainly don't need my assessment on how smart or dumb that move may have been, just so much: Like I mentioned above, it made me not even consider an Airspy for a while, for example because it created distrust, not only because "is their radio so bad that they need to do that?" and so on went through my brain but also because that's a question of conduct and mindset. Then it looked to me as if they just restructured their software to give themselves some head start, with an option for others to catch up later. The latest review on rtl-sdr.com and my experience with the RSP even indicate that the Airspy might be the better choice for my usage profile after all. But...Tech_Support wrote:This was a commercial decision taken by the authors of the software and it is entirely their right to do so and we fully respect that.
... if that's the truth I will not return my RSP1, make due with what I got and hope for the SDR#-plug-in authors to have mercy with us RSP users and start offering old versions of their plug-ins. But then IMHO any attempt on creating some merely basic functionality with SDR# is - more or less - a waste of resources if you can't get the things going that set SDR# apart from the other programs anyway.Tech_Support wrote:Please understand that no changes that we can make, either to our API or plugins (ExtIO or otherwise) can restore this functionality as the filters used to lock these features out are embedded within the main body of the code for SDR# and therefore unavailable to us as the program is closed source.
Tech_Support wrote:We have tried to make it very clear
...forever might the missing bit of information. I understand that this is hard to put in words elegantly and there's always a chance that this could become a "for the time being", but people may read the wrong things between the lines, like I obviously did.Tech_Support wrote:that there is limited functionality with the RSP and SDR# for release 1400 onwards...
I'm so fond of FB that my boss has to do the social networking for me.Tech_Support wrote:if you search this or our Facebook forum
I'm aware of only 2 (as I can't see HDSDR evolving):Tech_Support wrote:What I would say is that there are a number of alternative SDR packages that are evolving very rapidly and that as time progresses the software choices for the SDR community will get wider and better.