Skip to content

@github-actions github-actions released this Dec 8, 2019

From a code perspective, this release is the same as v0.4.0.

However, binaries for all platforms are now generated automatically. Additional architectures like ARM64 and i386 for Linux and Windows have been added.

The remoteAudio binaries are now additionally compressed to make them even smaller.

Assets 9

@dh1tw dh1tw released this Nov 14, 2019

It has been 1,5 years since the last release. It's really time for a new release. There have been a few modifications under the hood, but the focus was mainly on eliminating bugs and improving stability.

WARNING: There have been some changes in the syntax of the config file and in a few flags. Please check your config file carefully and change the affected parameters accordingly! Best practice is to compare it with example config file located in the master trunk of the repository.

Added features

  1. Transport layer NATS has proven to be an extremely reliable transport protocol. It's so good that I have discarded MQTT in favor of NATS. Get the latest version of the NATS Broker (nats-server) here.

  2. Sound APIs Windows and Linux come with one or more sound APIs. You can specifically select a particular sound API. On Windows the latency has dramatically dropped by switching from MME to WSAPI. The latter is now by default used in remoteAudio on Windows.

  3. VOX I've added a VOX activation, in case someone needs it

Build process
Several issues (#21 , #17) were reported with problems related to building remoteAudio from source. At the root, all these problems were related due to broken dependencies or broken dependencies of dependencies. Fortunately, the Golang team has added dependency management with Go 1.13. remoteAudio is now also a go module with frozen dependencies. That way it should be much easier to build remoteAudio on your machine. Just make sure to use >= Go 1.13.

Assets 7

@dh1tw dh1tw released this Apr 2, 2018 · 81 commits to master since this release

Bug fix release:

  • WebUI loads now correctly (e.g. at localhost:9090/)
Assets 7

@dh1tw dh1tw released this Apr 2, 2018

first alpha release of the completely rewritten remoteAudio application. Here the main new features:

  • Transport has changed from MQTT to NATS (you need the gnatsd broker)
  • Support for multiple audio servers
  • Audio servers are detected automatically
  • Server can start streaming on startup (via pflag)
  • As an alternative to the WebUI a REST API has been incorporated into the client

breaking changes:

  • no more MQTT (until v5 is supported)
  • several pflags have changed. Please delete the config file and use the pflags until the final version has been released. Some of the pflags might again change until then.

how to use remoteRotator:

# start audioserver (with a public broker temporarily installed on a VPS)
$ ./remoteAudio server nats -u= -Y=ts480

# start client
$ ./remoteAudio client nats -u=

**examples of the REST API:**

# get & set rx volume
$ curl localhost:9090/api/rx/volume
$ curl  -X PUT -d "{\"volume\":100}" "localhost:9090/rx/volume"

# get & set volume
$ curl localhost:9090/api/tx/volume
$ curl  -X PUT -d "{\"volume\":100}" "localhost:9090/tx/volume"

# get & set ptt
$ curl localhost:9090/api/tx/state
$ curl -X PUT -d "{\"on\":true}" "localhost:9090/tx/state"

# get list of available audio servers
$ curl localhost:9090/api/servers

# get details of audioserver "ts480"
$ curl localhost:9090/api/server/ts480

# start the audio stream from the ts480
$ curl -X PUT -d "{\"on\":true}" "localhost:9090/api/server/ts480/state"

# if you have several audio servers (e.g. ts480 and ft1000mp) you can select for example the ft1000mp
curl -X PUT -d "{\"active\":true}" "localhost:9090/api/server/ft1000mp/active
Assets 7

@dh1tw dh1tw released this Mar 7, 2017 · 192 commits to master since this release

  • bugfix (Windows version only):
    • Issue6: Windows Release missing dlls
Assets 6

@dh1tw dh1tw released this Mar 5, 2017 · 193 commits to master since this release

  • Added Windows release
  • bugfixes:
    • Issue1: If --user-id is not set, a random user-id should be generated
    • Issue3: explicit --config file is overwritten by default file
Assets 6
You can’t perform that action at this time.