SSDR 1.4 before the rapture or after the second coming

Neither After all bugs have been discovered and fixed

Come On man please wait hi hi

Sadly Eric you are correct.

FlexRadio may need to learn the hard way.

When you make a promise to customers, you must keep to it.

Without us they have no business, they need to remember that.

Right now they have lost all credibility to deliver on time.

We are still with you Flex at the moment, but you are pushing our patience too far.

I learned that in the new Flex the magic happens entirely into the rig.
The client can be as thin as an Arduino and your Flex still can work.
At the moment this is simply not possible for other sdr rigs.

tedious

Your right Howard, but most these guys will never understand this .lol I think some of these guys are visiting from the Anan group and they likely don't even own a Flex. I hear them trash Flex every day.

As a customer and long term software developer that has worked on very large complex projects I have some comments for the thread.

They are correct that discoveries are made along the way when developing a piece of software of this complexity. Your best understanding of the problem is when the last line of code has been written. It is rare that all issues are foreseen and scheduled in advance.

While the remote feature is cool there are other features that should have been cleared off of the table first (e.g. ATU memories). This part of the discussion I get and everyone has their own priority list. Personally, I miss the binaural audio feature of PowerSDR as it opened the "sound stage" and reduced listening fatigue.

Relying on the Open Source community is double edged and has it own pluses and minuses on a project by project basis. The bottom line is that Flex Radio is a business and for it to continue it requires a trusting customer base. This is really hard to achieve in this "I want it now" world. Deliver early with a bug ridden product and failure is ensured, deliver late with a solid product and you get better respect from me.

Please listen, get the basic functionality (e.g. memories, noise reduction etc.) off the table then add the edge cases like remote. If someone wants remote operation there are lots of solutions in place until it is offered by the mothership.

Almost done, for me the binaural audio feature would be really cool and used during each session. The "every day" items are what is important for a piece of hardware of this level.

The problem is this remote effects almost everything in the radio, remote needs to be in now to see what it is effecting. After this is nailed down and understood other features can be added after understanding how they will be effected.

Tim, keep on testing - a stable product is required.

As a customer and after the refactoring has completed I would personally like to see the date schedule return with "approximate" scheduling. I cannot relate to FRS how important this is. Are the dates written in stone - no, but these forums are an excellent source of information for prioritizing features if you can filter out the "noise".

Richard, I started SDRs with a 1500 two years ago, and quickly upgraded to a 6500. My opinion is that by waiting for the software to be "perfect" before purchase you are only denying yourself the pleasure of the best receiver out there. The only major functionality I miss is the Noise Blanker, and by careful adjustment of NB and AGC-T I can make do. But I all other areas the 6500 is a superior rig that has gotten better with every release. I don't refuse to eat a good steak just because it might have a small **** of **** in the wrong place. I cut around it and enjoy. But I know people who do. And others who won't eat a banana if it has a single small spot on the peeling.

Tim, 1.3.8.126 is stable, running well, have had abt. 1k digital QSO's until now with my new 6500. I'm looking forward to 1.4 but not biting my fingernails - yet. BTW my mustache is not kool-aid dyed. I still use salt water, as a sailor....

Almost, just around the next corner, and over the next hill, next light, oops got to stop for gas sorry.

Tim this is only meant to be constructive and not wining.. I think delays happen.. stuff happens..  but when a release is months past due, it could be good to sort of give regular customer updates to keep the qrm down.  maybe a weekly or bi-weekly status and or a release date has been revised to **** because of the major rework involved in completely changing the interface..and here is what is going on behind the scenes.  Solid communication and transparency is the best bet when dealing with a technical customer base IMHO.  Also an open beta program would be another way to keep down the qrm.. Elecraft has used this model for years.. offering beta versions of software to the customer base with a disclaimer that it is not fully ready for prime time.  something to consider.

Thanks for your work and you are doing a great job and these are just suggestions.   Hopefully we will have a lot of happy campers once this gets done.