From 5353d131511a4ad1fdc0266f2ccaf28ac648826d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Aleix=20Conchillo=20Flaqu=C3=A9?= Date: Wed, 6 Nov 2024 13:16:58 -0800 Subject: [PATCH] update CHANGELOG --- CHANGELOG.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index cb49ae499..a810258d3 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,15 +9,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 ### Added -- There's now an input queue for each frame processor. When you call +- There's now an input queue in each frame processor. When you call `FrameProcessor.push_frame()` this will internally call - `FrameProcessor.queue_frame()` on the next processor (upstream or - downstream). Then, the queue frames will get processed. With this input queue - it is now possible for FrameProcessors to block processing more frames via a - list of blocking frames. For example, some TTS services now block processing - more frames if they see a `TTSSpeakFrame` or a `LLMFullResponseEndFrame` until - the bot has stopped speaking. This makes sure we don't mix audio from - different sentences. The way to resume processing frames is by calling + `FrameProcessor.queue_frame()` on the next processor (upstream or downstream) + and the frame will be internally queued (except system frames). Then, the + queued frames will get processed. With this input queue it is also possible + for FrameProcessors to block processing more frames via a list of blocking + frames. For example, some TTS services now block processing more frames if + they see a `TTSSpeakFrame` or a `LLMFullResponseEndFrame` until the bot has + stopped speaking. This makes sure we don't mix audio from different + sentences. The way to resume processing frames is by calling `FrameProcessor.resume_processing_frames()`. - Added audio filter `NoisereduceFilter`.