From d30c9f828d31879a32e6cf15bf58d7c3665fcce0 Mon Sep 17 00:00:00 2001 From: onyx-and-iris Date: Mon, 2 Mar 2026 11:59:56 +0000 Subject: [PATCH] upd recorder examples add implementation note 4 --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e25ac11..c0569bb 100644 --- a/README.md +++ b/README.md @@ -144,9 +144,9 @@ examples: ```console vban-cli recorder play -vban-cli recorder rew +vban-cli recorder pause -vban-cli recorder replay +vban-cli recorder goto "00:01:30" ``` see `vban-cli recorder --help` for more info. @@ -180,6 +180,7 @@ see `vban-cli sendtext --help` for more info. 1. The VBAN RT SERVICE subprotocol defines two packet structures [ident:0][ident-0] and [ident:1][ident-1]. Neither of them contain the data for Bus EQ parameters. 2. Packet structure with [ident:1][ident-1] is emitted by the VBAN server only on pdirty events. This means we do not receive the current state of those parameters on initial subscription. Therefore any commands which are intended to fetch the value of parameters defined in packet [ident:1][ident-1] will not work in this CLI. 3. Packet structure with [ident:1][ident-1] defines parameteric EQ data only for the [first channel][ident-1-peq]. +4. There doesn't appear to be any way to retrieve the current recorder status, ie, recording, playing, stopped etc. ---