Merge pull request #2317 from pipecat-ai/mb/release-prep-0.0.77
Changelog update for 0.0.77
This commit is contained in:
22
CHANGELOG.md
22
CHANGELOG.md
@@ -5,16 +5,16 @@ All notable changes to **Pipecat** will be documented in this file.
|
|||||||
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
||||||
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
||||||
|
|
||||||
## [Unreleased]
|
## [0.0.77] - 2025-07-31
|
||||||
|
|
||||||
### Added
|
### Added
|
||||||
|
|
||||||
- Added `InputTextRawFrame` frame type to handle user text input with Gemini
|
- Added `InputTextRawFrame` frame type to handle user text input with Gemini
|
||||||
Multimodal Live.
|
Multimodal Live.
|
||||||
|
|
||||||
- Added `HeyGenVideoService`. This is an integration for HeyGen Interactive Avatar.
|
- Added `HeyGenVideoService`. This is an integration for HeyGen Interactive
|
||||||
A video service that handles audio streaming and requests HeyGen to generate
|
Avatar. A video service that handles audio streaming and requests HeyGen to
|
||||||
avatar video responses. (see https://www.heygen.com/)
|
generate avatar video responses. (see https://www.heygen.com/)
|
||||||
|
|
||||||
- Added the ability to switch voices to `RimeTTSService`.
|
- Added the ability to switch voices to `RimeTTSService`.
|
||||||
|
|
||||||
@@ -49,9 +49,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|||||||
- Added a new TTS service, `InworldTTSService`. This service provides
|
- Added a new TTS service, `InworldTTSService`. This service provides
|
||||||
low-latency, high-quality speech generation using Inworld's streaming API.
|
low-latency, high-quality speech generation using Inworld's streaming API.
|
||||||
|
|
||||||
- Added a new field `handle_sigterm` to `PipelineRunner`. It defaults to `False`.
|
- Added a new field `handle_sigterm` to `PipelineRunner`. It defaults to
|
||||||
This field handles SIGTERM signals. The `handle_sigint` field still defaults
|
`False`. This field handles SIGTERM signals. The `handle_sigint` field still
|
||||||
to `True`, but now it handles only SIGINT signals.
|
defaults to `True`, but now it handles only SIGINT signals.
|
||||||
|
|
||||||
- Added foundational example `14u-function-calling-ollama.py` for Ollama
|
- Added foundational example `14u-function-calling-ollama.py` for Ollama
|
||||||
function calling.
|
function calling.
|
||||||
@@ -124,7 +124,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|||||||
|
|
||||||
- Updated `SpeechmaticsSTTService`:
|
- Updated `SpeechmaticsSTTService`:
|
||||||
- Added support for additional diarization options.
|
- Added support for additional diarization options.
|
||||||
- Added foundational example `07a-interruptible-speechmatics-vad.py`, which uses VAD detection provided by `SpeechmaticsSTTService`.
|
- Added foundational example `07a-interruptible-speechmatics-vad.py`, which
|
||||||
|
uses VAD detection provided by `SpeechmaticsSTTService`.
|
||||||
|
|
||||||
### Fixed
|
### Fixed
|
||||||
|
|
||||||
@@ -167,8 +168,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|||||||
- Fixed an issue in `ElevenLabsTTSService` where the word/timestamp pairs were
|
- Fixed an issue in `ElevenLabsTTSService` where the word/timestamp pairs were
|
||||||
calculating word boundaries incorrectly.
|
calculating word boundaries incorrectly.
|
||||||
|
|
||||||
- Fixed an issue where, in some edge cases, the `EmulateUserStartedSpeakingFrame`
|
- Fixed an issue where, in some edge cases, the
|
||||||
could be created even if we didn't have a transcription.
|
`EmulateUserStartedSpeakingFrame` could be created even if we didn't have a
|
||||||
|
transcription.
|
||||||
|
|
||||||
- Fixed an issue in `GoogleLLMContext` where it would inject the
|
- Fixed an issue in `GoogleLLMContext` where it would inject the
|
||||||
`system_message` as a "user" message into cases where it was not meant to;
|
`system_message` as a "user" message into cases where it was not meant to;
|
||||||
|
|||||||
Reference in New Issue
Block a user