Direct TCP/IP audio

  • 1
  • Question
  • Updated 3 years ago
There are several radio control programs available that bypass SmartSDR CAT and communicate with the Flex via TCP/IP directly or using an API. Are there any programs that get and send audio data directly, bypassing SmartSDR DAX? Obviously non-Windows programs do, but are there any Windows based programs that do?
Photo of Mark Erbaugh

Mark Erbaugh

  • 516 Posts
  • 45 Reply Likes

Posted 3 years ago

  • 1
Photo of Andy M5ZAP

Andy M5ZAP

  • 195 Posts
  • 40 Reply Likes
Hi Mark,

Writelog contesting software does if you install the writelog flex driver, but I had a few problems with it in the last RTTY contest. One of the advantages in Writelog using IP comms is that the audio drive levels for digital modes are set automatically by the ptotocol no adjusting levels to prevent over driving is necessary.

In fact you can close the SmartSDR Cat and Dax programs when using writelog with the flex driver if you so desire.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9198 Posts
  • 3558 Reply Likes
Not many.  Like only one I know of (see above).  We wish more software developers would convert their programs to using the VITA-49 audio data from the radio and bypassing the Windows sound interface altogether.
Photo of Andy M5ZAP

Andy M5ZAP

  • 195 Posts
  • 40 Reply Likes
Tim,
SmartSDR 2.xxx will be remote control over WAN (flex insider) will ver 3.xxx be logging and data or is that too much to cover and you will be leaving logging and data modes to 3rd party developers.?
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9198 Posts
  • 3558 Reply Likes
Any question of this type related to if and when a particular feature will be in a future release of software will always receive the same answer.  Which is..

It is the policy of FlexRadio Systems not to comment or speculate about future products or software features before their release is imminent.  

The impetus behind this policy as it relates to software features is that we employ a "just in time" methodology for working on features; meaning we do not do long range detailed planning.  And if a feature is planned and coded for a release, it has to pass alpha testing before we have a level of confidence that the feature will be included in a particular release.  The other reason we refrain from doing long-range planning is that priorities can change within the long-term window and that can lead to unrealized expectations, so we no longer do that.  
(Edited)