Even though that need would only be used by a small percentage of the user base. The use of third party applications allows for the customization of what we see and what we do thru the API and leaves the radio's processor free to process and manage RF and communicate the results. it's job #1 .
With 3rd party the number of applications running is increased but if SSDR does the job or 3rd party does the job the the work effort by the PC will be about the same.
I use several 3rd party applications one gives me the ability to scan and have a squelch function. While not everyone wants to scan frequencies in HF or have a Squelch it's not something I would ask Flex to do. (Thanks Mark FRStack)
Shouldn't 90% of what Flex is working on improving RX, TX and the communications from the radio to the outside world. From there the API and the GREAT 3rd party guys take on a lot of the lifting it's WIN/WIN.
Building things into SmartSDR brings portability. This means that I can do the same thing from computer to computer, and even on an iPad, mac or even Maestro.
Also, something like squelch is a core radio function. That belongs in the radio software.
One of the reasons I like Flex over "the other guys" SDR is that the settings are kept in the radio and everything is in one place.
Or eventually not allowing third party software at all, then what do we do? Or every time a new mode comes along, complaints if they don't implement it immediately.
Then again, I demand that FlexRadio Systems have native Feld-Hell and ATV support! Definitely just kidding.
cause it is a combo of 3rd party apps and internet needed to make it work
i like that flex has focused on making radio performance the number one priority
all the other stuff left to other apps...
which could easily interface with the flex api's
on any platform too ( for example..ipad , iphone, PC laptop)
a simple thing as adding call signs can easily lead to feature creap
can you make font user defined, oh yea make color user defined
can you make it flash if i need them, for awards such as was, dxcc, vucc.county hunter
the list goes on and on for something that appears this simple...
so my opinion ( current value of 0.02 USD )..
let the radio be a radio
let the apps be intelligent hamradio assistants using the radio interface (api's)
let the the radio be a server to all kinds of intelligent apps
interfacing with me and the computer ( aka user interface of my choice) and the internet.
P.S. My personal use of external software boils down to this: N1MM for basic logging, WSJTx, for ft8, WoodBox SSmeters...and the rest can be left to those who desire it, in "outside" apps, as I have. If there is one thing I'd like to see, it'd be a full on version of SSDR for Linux. Jim KJ7S
Kenwood TS-2000 shack in the box Since 2000 thats 18 years now.
Must be money in the ts-2000 or Kenwood wouldnt be making them for over 18 years.
Good or bad is not the debate here of the kenwood.
SDR radio how much more improvements on a radio can be made on 'RX-TX'?
Ruff comparison but at some point SDR moves onto next level?
Records-tape-CD-digital relm of Mp3 and other types of audio formats.
For Analog radio going digital and back how mouch can we add?
Add more software to a shack in a box.!
External to SmartSDR thats fine too. Add to Smartsdr for me IMO i would like even more baked in.
We have to ask like Hamradio Deluxe how far do we want to go but at least one thing
Flexradio only has a few radios to program to unlike HRD.
Either way bring on the software.
More modes more software. Software defined radio!
IMHO a better approach would be for the various software that people want to use with the radio hardware be written to directly control the 6K hardware without needing to interface with SmartSDR at all. In fact SmartSDR, or other intermediary client would simply not be needed in any way for that kind of approach. The Flex API provides a means for implementing this fundamental rethink of how the radio hardware can be driven for different mode and operating activity specific purposes.
For example, picture a WSJT-X like program that natively controls the 6K radio hardware via the Flex API directly. Or perhaps for contesters a N1MM like program that directly drives the radio hardware. And in both cases those applications ARE the radio’s UI when they are being run. As such they can be fully optimized for what those programs do instead of having a general purpose UI client like SmartSDR in the middle of things. It isn’t truly needed. So the 3rd party application would no longer need to interface with the radio client software, but instead be the radio client software. And each then being highly optimized for its purpose. There are undoubtedly countless other specific operating styles, uses, and modes that this could applied to.
And with multi-client on the horizon some really cool station possibilities could potentially be implemented. There could a mix of SmartSDR client(s), Maestro(s), and specialized mode specific clients all of which are just different clients operating on a single 6K hardware box. Obviously all of it ultimately bounded by what the multi-client implementation will allow for.
I know I have floated this idea before about building the radio control and UI presentation directly into the specific applications instead of wanting or trying to build the specific applications into the traditional general purpose radio client such as SmartSDR. The trick and hard part of this is to get the authors of the various software application to even consider this approach. Or for the ham community in general to understand what the advantages of this approach would be. And therefore ask for it.
I can only dream.
- 4781 Conversations
- 1390 Followers
- 2785 Conversations
- 572 Followers
- 3304 Conversations
- 845 Followers
- 774 Conversations
- 144 Followers
- 2717 Conversations
- 781 Followers
- 430 Conversations
- 152 Followers
- 829 Conversations
- 227 Followers
- 639 Conversations
- 100 Followers
- 650 Conversations
- 94 Followers
- 717 Conversations
- 116 Followers
- 769 Conversations
- 114 Followers