From: Mike Brady <4265913+mikebrady@users.noreply.github.com>
Date: Sat, 26 Nov 2022 18:45:34 +0000 (+0000)
Subject: Update RELEASENOTES-DEVELOPMENT.md
X-Git-Tag: 4.1.1~2^2~11^2
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a3151c3c55b6e2b61906bc57c1ed0d38b2cb17c7;p=thirdparty%2Fshairport-sync.git

Update RELEASENOTES-DEVELOPMENT.md
---

diff --git a/RELEASENOTES-DEVELOPMENT.md b/RELEASENOTES-DEVELOPMENT.md
index eb6720a4..2ef31714 100644
--- a/RELEASENOTES-DEVELOPMENT.md
+++ b/RELEASENOTES-DEVELOPMENT.md
@@ -1,4 +1,13 @@
+Version 4.1-dev-805-g50738c36
+====
+**Enhancements**
+* Very provisional additions to the metadata -- add some functionality for Shairport Sync to send information about what frame of audio is being played at a particular time. It can be set up to periodically generate a `phbt` (a Playing HeartBeaT) item comprising the RTP frame number of the audio being played at a particular instant -- the computer's system time in nanoseconds. The two numbers are presented as a string, e.g. `595422363/4697675115573193`. Set the interval in seconds with the new `metadata` setting `progress_interval` – 0.0 means no heartbeat is generated. 
+* Equivalent additions have been made to the native `DBus` interface: the `phbt` information appears as a `FramePosition` property and the update interval can be set using the `SetFramePositionUpdateInterval(Seconds)` method.
+
+Please note that this might all disappear or change radically.
+ 
 Version 4.1-dev-798-g803eddbd
+====
 **Docker**
 * Within the Docker container, launch Shairport Sync as `root` user rather than as the user `shairport-sync`. This is experimental, to investigate possible device access issues.