For V4 I would like to have ........

Pat N6PAT

I have no use for V3 so I am looking towards V4

For V4 I would like to have FT8 built into SSDR. It's rapidly becoming the most popular mode on every band especially 160. Incorporating FT8 into SSDR would eliminate the interfacing issues with WSJT-X (need to restart DAX, decoding stops , etc.). Ideally this would tie into JTAlert or perhaps SSDR could have it's own version of JTAlert.

This is a feature I would be willing to pay the upgrade fee for.

KF4HR

Considering how many people do not like FT8 and how quickly digital mode technology is evolving, I'd be seriously surprised if Flex would consider adding FT8 to SSDR.  This is a feature I'd never pay for.

Pat N6PAT

FT8 is very ;popular. Most of the action on 160 is FT8 now. That goes for 60 meters as well. 30 meters is another band very active with FT8

Bill -VA3WTB

As long as it does not use any radio sesources, keeping in mind we are talking thin client here.

Perhaps just skip V4 features all together and work on many of the oustanding problems we have now. Then go back to working on features.

Pat N6PAT

I'll never understand why some people hate FT8 so much. It's just another mode. I'll bet RTTY was hated when it was first introduced.

FT8 is a wonderful way for deaf people to participate in ham radio. It's also great for those with speech problems like recovering **** victims to enjoy QSO's

Neil D Friedman N3DF

Also great for those of us with (of necessity) severely compromised antennas and power output. 

Pat N6PAT

How does downloading V3 and letting it sit in a folder without installing it keep you up to date?

Kevin

If/when/before I call for support on a V2 issue I will probably load up V3 to see if that fixes the problem. If it does, then it would be a matter of deciding whether the fix is more important than the loss of functionality. 

Kev

Roger_W6VZV

I think that this point is moot.  My understanding is that the developers of WSJT modes will only allow it to be incorporated into other software if it is on a no-pay basis.  That is why, for example, HRD/Digital Master does not include FT8.  If I'm wrong someone tell me.  Having said that, WSJT-X is so easy to use with the Flex I'm not sure that there would be much point in incorporating it into SDR.
de Roger W6VZV

KF4HR

I'll bet RTTY was hated when it was first introduced.

Pat you'd loose that bet.  RTTY was, and still is popular with hams, even decades ago when electro-mechancial devices were being used.  I consider RTTY a real communications mode, meaning you can carry on a real conversation, not just a brief data exchange.  (Yes, I know JS8Call allows more information.)

I'll never understand why some people hate FT8 so much.

Who said hate? Pat what you seem to be missing is, while some enjoy FT8, and that's great, there are others that feel that the FT8 mode is too impersonal, too robotic, too automatic, somewhat mindless, and/or generally boring and repetitious.

Bottom line, if you enjoy FT8, by all means go forth and exchange call signs and signal reports till your hearts content.  Just know everyone may not see things the way you do.   

David Decoons, wo2x

Another point of NOT including FT8 encode/decode into SSDR is WSJT-X includes several modes in addition to FT8. With the continued refinement of FT8 (v2 vs v1) it would be difficult for Flex to expend engineering resources to keep up with changes. 

Flex has made it easy to use third party software via DAX and CAT and WSJT-X works extremely well, including Fox/Hound mode so why reinvent the wheel?

Dave wo2x

Pat N6PAT

I suppose you could say the same thing about CWX.

There's a number of third party CW  keyboard coders available.

Or how about the Quick Record feature? There's lots of ways to do that outside SSDR,

Just because a function is available via third party applications doesn't mean it wouldn't be nice to incorporate the same functionality in SSDR.

David Decoons, wo2x

How often does the alphabet change? (CWX)

Recorder - if you want to do anything but quick record and playback you NEED to use third party software (Contest voice keyer with multiple selections, export recordings to a file)

The point is the FT8 protocol has changed several times, making older versions not compatible to newer versions. This would require extra engineering time to keep up with the changes. Flex would not release a new version the same day Joe Taylor and crew decide to change F/H mode. Imagine the uproar if a Bouvet Island DXPedition required a new version of FT8 protocol and Flex did not release a new version. 

As Roger mentioned above Joe Taylor has stated there are restrictions to allowing others to use his protocol in other programs. (We had the opportunity to have him as a guest speaker at NJDXA meeting).

Yes it would be convenient to have an all included but I prefer to leave as-is since it works so well. Using latest Windows 10 OS on an I7 8700k CPU I have not had any DAX dropouts in a long time.

Dave AA6YQ

I second Bill VA3WTB's suggestion: Flex's top priority should be eradicating the backlog of reported-but-uncorrected defects.

I further suggest that Flex

a. correct these defects in the next version of v3 (not v2)

b. make the next version of v3 (and all future "core versions") free

c. retire v2.

To enable this approach, Flex should add a license manager to the next version of v3 so that multiFlex would only be available to users who pay a $199 license fee; anyone who paid for the current v3 would receive a multiFlex license. Any future enhancements would similarly require purchasing a license.

It is entirely reasonable for Flex to charge for multiFlex. This is a significant new capability. A business is expected to generate a profit from the value it delivers to its customers.

The correction of a defect, on the other hand, should be available without charge to anyone who purchased a Flex product now afflicted by that defect.

By always correcting defects in a free core version and selling licenses to new enhancements, Flex and its user community both win:

1. users are assured that defects discovered in Flex products they've purchased will be available at no charge

2. users can optionally purchase licenses for enhancements they consider useful

3. Flex can focus its support on a  single core release

4. Flex can develop new enhancements for which interested users pay to receive a license

Pat N6PAT

I doubt that Flex would offer a free core version when they don't even offer a trial period of new releases that they charge for.

In fact, I mentioned it in a post yesterday and they immediately deleted my post.

Dave AA6YQ

Providing a core release bearing defect repairs at no charge is not the same as offering a trial period for new enhancements.

The problem with a free trial of new enhancements is that nearly everyone will want to kick the tires, even those not serious about purchasing a license. Supporting all that tire-kicking is consumptive of support and development staff.

Pat N6PAT

What is the difference between potential buyers reporting bugs verses buyers reporting bugs? A bug regardless of the party reporting it should be fixed

Dave AA6YQ

You are assuming that users evaluating a new feature would only generate support costs if they encounter a defect, which Flex should be happy to correct. Unfortunately, the assumption is false: some users would attempt to assess the feature without having reviewed the documentation, and then contact Support for help -- but never purchase the enhancement because they weren't seriously interested.

Could marketing collateral - documentation and videos - should enable users to determine whether or not they are interested enough in new functionality to be willing to pay for it. If users are confident that any defects discovered will be promptly corrected at no charge, then there should be no hesitance in purchasing the new feature.

The frustration with the recent release of v3 has not been "I bought multiFlex thinking it would do X, but it doesn't do so". Users not in interested in multiFlex are frustrated because they must continue to live with uncorrected defects, some of which were corrected in v3. The fact that some 3rd party applications don't work with v3 is another source of user frustration. Both of these sources of frustration can be eliminated.

Pat N6PAT

Consider this: How many people that take a car for a test drive actually purchase the car? I'd guess a very small percentage. Yet, the dealerships use this in the hopes of attracting actual buyers which they do.

Somehow with all the time spent with people that do not buy the car they still manage to make a healthy profit. The same applies with Microsoft.

I'm not going to bore folks with this anymore.

Dave AA6YQ

One can't properly evaluate a car by reading documentation and watching YouTube videos; Tesla recently tried this, and quickly abandoned it. Cars also cost a lot more than new Flex features, and thus can support a higher "cost of sales" -  like salespeople who chaperone test drives.

Stan VA7NF

Most of my suggestions don't get much traction but here is an older one, revisited.

What is needed is an interface to 3rd party applications that are addressable in two places:
1) Through a standard format API data block, with content applicable to the particular application being implemented.  This could be any format data
2) Through a radio interface to a hosted application (such as USB to a local computer that can run the user application)

With that structure any 3rd party application can communicate from the operating position, remote or local, to the matching application running at the server site.  Think rotator control, decoders, loggers.  All without changing the SSDR in any way, other than creating the interface. 

Steve

I agree with Bill, just fix what has been broken for years, then consider adding new features.  One thing I would like to have fixed ASAP is the auto save function for profiles...give us the the option.  73's to all

Neil D Friedman N3DF

And location (grid square).  Now if only they could add the weather, your job and rig.

Pat N6PAT

If it's been broken for years in spite of new versions being released then I take that as a clear sign that there are no plans to ever fix it.

Bill -VA3WTB

I am not a Flex employee

Even though all versions of software continue to be supported by Flex I suspect soon V2 will become feature frozen if it has not been already.

In effect being retired....

Dave AA6YQ

Many software organizations make the mistake of prioritizing enhancements over corrections to defects that aren't "showstoppers". But the logic behind correcting all known defects is compelling; organizations can and do improve their software development processes.

The Flex user community's love-hate reaction to SmartSDR v3 as demonstrated by posts in this forum is a crystal-clear indication that such a change is required.

Mark_WS7M

I also have seen FT8 "change" meaning Joe Taylor is updating it with new modes and features.  I think it would be unlikely that Flex would want to get in that mix with an internal decoder.

If you are having lots of issues with DAX then something is wrong.  I had a period of instability but it is mostly gone.  I can fire up SSDR and DAX with WSJT-X and it runs all day long without issue.

Like the others in this comment I doubt flex will re-invent the wheel here.

Dave AA6YQ

From the FlexRadio FAQ:

"Will there be another release for SmartSDR version 2?"

"Yes, we will be releasing SmartSDR v2.5 later in 2019. SmartSDR v2.5 will be a maintenance release which will include a number of performance improvements and bug fixes."

https://www.flexradio.com/faq-smartsdr/

Steve K9ZW

I’d like to see a future version combine the product from several Flex-6000 radio servers together. I’d also wonder if the Maestro and M models could gain an ability to carry onboard software that now has to stand alone? 73 Steve K9ZW

Burt Fisher

Reminds of a woman instead of taking a shower cover up the aroma with perfume. Would you paint over a dirty wall or clean it first?

Pat N6PAT

Another feature on my wish list would be the ability to apply custom skins to SSDR. The 2.3.9 color scheme is pretty boring