SdrDx Docs -> appsupport
         Previous <—> Next                  HomeContentsIndex                  Guide                 BETA DOCUMENTATION

Beta Address:

6 - Application and Device Support

6.1 - Routing Sound From SdrDx to Other Applications

6.1.1 - Under OS X

I have successfully used both SoundFlower (under OS X releases from 10.6.8 on up) and Rouge Amoeba's SoundSource (under OS X 10.12.6) to route sound from SdrDx to applications like Black Cat SSTV and fldigi.

6.1.2 - Under Windows

I have no information about doing this under Windows. Information contributions to help other users would be welcome.

6.2 - List of Applications

The following applications support SdrDx:

or Device
Function(s) added to SdrDx Platform(s)
Black Cat SSTVSSTV reception.OS X, Windows
DX ToolBoxBeacon identification, custom frequency labeling, mapping AM stations, one-click access to identification of on-the-air shortwave stations, many other additional features.OS X, Windows
RUMLogLogging, synchronization (tuning, demodulator mode) with amateur radio transceiversTargeted to OS X, Multiplatform, but some functionality not supported under Windows
ObsoleteVFO SuiteProvides 26 radio-style VFOs for SdrDx. Each VFO tunes independently, remembers mode, center frequency, more. Supports VFO swap and copy, remote display of frequency and mode for all 26 VFOs.OS X, Windows
SwDbShortwave Database: Allows you to create and maintain a database that is used by SdrDx to emplace old-radio-style station banners on the spectrum where you are tuned.OS X
SteppIR SDA 100 Tunable AntennaAllows the antenna to tune in synchrony with SdrDx frequency changes (write me about this, or check the comment section on the download page — we built it with a Python script.)OS X, Windows
Kenwood TS-990S TransceiverSdrDx can control the TS-990S, and the TS-990S can control SdrDx. There's a free script available from me that enables this. Just post a request on my blog.OS X, Windows

6.3 - To the Attention of Software Developers

On the next few pages, the UDP broadcast and TCP server interfaces are detailed. These interfaces provide a means for programs (and indirectly, hardware) outside of SdrDx to co-ordinate and control actions with SdrDx.

The UDP interface under OS X isn't recommended; after writing it, I found that Apple had left a bug in the OS (for years now) where a UDP socket can only be opened by one client on a single machine. This pretty directly defeats the purpose of a broadcast protocol, although it should work fine under Windows.

So instead, I recommend you use the TCP interface, which has several advantages (aside from not being essentially broken!)

TCP, via the usual mechanism of IP and port, allows you to work with SdrDx over any portion of a LAN or the WAN that you choose to. UDP only works on the LAN. When it works. (cough.)

TCP is an error-checked protocol. So you can be sure that what you got is what was sent. UDP isn't, and that can be a problem.

I hope that if you've got an idea, you'll just go ahead and implement it. I'll help if I can, and if you need a particular message or command, don't be shy about asking me to write it in. Generally speaking, I'm more than willing, presuming only it doesn't break existing functionality.

toc    index    guide    changes    keyboard    , previous    . next
Please consider supporting my SdrDx development efforts via a small donation.

         Previous <—> Next                  HomeContentsIndex                  Guide                 BETA DOCUMENTATION