AMBE feature support in Linux only

plugins/channelrx/demoddsd/readme.md

@@ -18,6 +18,8 @@ To enable this plugin at compile time you will need to have DSDcc installed in y
 
 <h2>DV serial device support</h2>
 
+&#9888; This is supported in Linux only since the AMBE feature plugin is supported in Linux only.
+
 You can use a serial device connected to your system that implements and exposes the packet interface of the AMBE3000 chip. This can be for example a ThumbDV USB dongle. You may also connect to an AMBE server instance over the network. This is supported via the [AMBE feature](../../feature/ambe/readme.md).
 
 If no AMBE features are active or the AMBE support is not engaged (B.19) AMBE decoding will take place with Mbelib. Possible copyright issues apart (see next) the audio quality with the DVSI AMBE chip is much better.

plugins/feature/CMakeLists.txt

@@ -40,6 +40,6 @@ if (ENABLE_LIMESUITE AND LIMESUITE_FOUND)
     add_subdirectory(limerfe)
 endif()
 
-if (LIBSERIALDV_FOUND)
+if (LINUX AND LIBSERIALDV_FOUND)
     add_subdirectory(ambe)
 endif()

plugins/feature/ambe/readme.md

@@ -4,14 +4,14 @@
 
 Control AMBE3000 serial a.k.a. DV serial devices or AMBE server addresses to use for AMBE digital voice processing.
 
+⚠ Note: this plugin is supported in Linux only.
+
 DV serial devices are supported using the [SerialDV](https://github.com/f4exb/serialDV) library that is a mandatory requirement for this feature to be compiled. Therefore you have to compile and install SerialDV in your system. Please refer to this project Readme.md to compile and install SerialDV. f you install it in a custom location say `/opt/install/serialdv` you will need to add this define to the cmake command: `-DSERIALDV_DIR=/opt/install/serialdv`
 
 To effectively use serial DV devices for AMBE decoding you will have to add at least one device to the list of AMBE devices (6) in use.
 
 Although such serial devices work with a serial interface at 400 kb in practice maybe for other reasons they are capable of handling only one conversation at a time. The software will allocate the device dynamically to a conversation with an inactivity timeout of 1 second so that conversations do not get interrupted constantly making the audio output too choppy. In practice you will have to have as many devices listed in (6) as the number of conversations you would like to be handled in parallel.
 
-Note also that hardware serial devices are not supported in Windows because of trouble with COM port support (contributors welcome!).
-
 ---
 ⚠ With kernel 4.4.52 and maybe other 4.4 versions the default for FTDI devices (that is in the ftdi_sio kernel module) is not to set it as low latency. This results in the ThumbDV dongle not working anymore because its response is too slow to sustain the normal AMBE packets flow. The solution is to force low latency by changing the variable for your device (ex: /dev/ttyUSB0) as follows:
 
@@ -28,7 +28,7 @@ Newer kernels do not seem to have this issue.
 
 <h3>1: AMBE server address and port or direct input</h3>
 
-Use this freeflow text input box to specify either the address and port of an AMBE server in the form: &lt;IPv4 address>:&lt;port> or any directly attached physical device address like a COM port on Windows.
+Use this freeflow text input box to specify either the address and port of an AMBE server in the form: &lt;IPv4 address>:&lt;port> or any directly attached physical device address.
 
 <h3>2: Import above address or device</h3>