diff options
| author | Mike Brady <mikebradydublin@icloud.com> | 2020-06-02 19:43:01 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-06-02 19:43:01 +0100 |
| commit | 72e5274fca4f6a215596b0743b29ecdea33e6e40 (patch) | |
| tree | 76642276cd2dc30bcf1eb5f0edc348290b0c0415 | |
| parent | dfe48c28feeef27fb5a46815b2d584e539d45f7b (diff) | |
Update RELEASENOTES-DEVELOPMENT.md
| -rw-r--r-- | RELEASENOTES-DEVELOPMENT.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/RELEASENOTES-DEVELOPMENT.md b/RELEASENOTES-DEVELOPMENT.md index 0273021..abc9cb0 100644 --- a/RELEASENOTES-DEVELOPMENT.md +++ b/RELEASENOTES-DEVELOPMENT.md @@ -3,7 +3,7 @@ Version 3.3.7d7 **Enhancements** * Logs and statistics can now be directed to the system log (default), `stdout`, `stderr` or to a file or pipe of your choice using a new setting, `log_output_to` in the `diagnostics` section of the configuration file. This is very useful when the system log is disabled or diverted. * Audio data from the `pipe` back end and metadata from the metadata pipe are now written using standard blocking `write` commands rather than a slightly complex non-blocking write function. Pipes are now opened in non-blocking mode and changed to blocking mode when successfully opened. -* Separate threads for the metadata subsystems. Until now, all metadata was processed on a single thread. This included supplying the metadata pipe and the multicast stream and supplying metadata for the mqtt interface and for the `dbus` and `MPRIS` interfaces. Unfortunately, that meant that a problem with any one of these subsystems could propagate into the others. Now they all run on separate threads. If one thread blocks, it will not interfere with the other subsystems. +* Separate threads for the metadata subsystems. Until now, all metadata was processed on a single thread. This included supplying the metadata pipe and the multicast stream and supplying metadata for the `mqtt` interface and for the `dbus` and `MPRIS` interfaces. Unfortunately, that meant that a problem with any one of these subsystems could propagate into the others. Now they all run on separate threads. If one thread blocks, it will not interfere with the other subsystems. **Bug Fixes and Enhancements** * Fixed a bug calculating the instantaneous synchronisation error. This bug could occasionally cause Shairport Sync to lose synchronisation and maybe even to mute for a few seconds before resynchronising. It was caused doing modulo arithmetic incorrectly and it's been there for a while. |