pipecat-alkove
Alkove for Pipecat: AlkoveFilter keeps the user's voice and removes the others and the noise (Focus), AlkoveVADAnalyzer finds where they speak (Cue). Both run on the bot's CPU, with no server and no key, with the chain of Alkove's web SDK; where speech starts and ends is Pipecat's VADParams.
Maintained by Alkove, not by the Pipecat team.
Install
pip install pipecat-alkove
The models (Focus 1.1 MB, Cue 1.1 MB) are downloaded once into the cache and checked by their sha256: the analyzer loads them when it is created, as Silero's does, the filter when the transport starts. Pass models=alkove.Models.load(["focus", "cue"], dir=...) to read them from your own folder.
Use
from pipecat.audio.vad.vad_analyzer import VADParams
from pipecat.transports.base_transport import TransportParams
from pipecat_alkove import AlkoveFilter, AlkoveVADAnalyzer
params = TransportParams(audio_in_enabled=True, audio_in_filter=AlkoveFilter())
vad = AlkoveVADAnalyzer() # VADParams(confidence=0.5) unless you pass params
Give the analyzer to your user aggregator (LLMUserAggregatorParams(vad_analyzer=vad)) or to a VADProcessor, as you would Silero's.
AlkoveFilterkeeps the closest voice, or withvoiceprint=the voice of that print;strength=andnormalize=work as in the web SDK. It works at the transport's input rate.FilterEnableFrame(False)gives the raw microphone back at the same delay;FilterUpdateSettingsFrame(settings={"strength": 0.5})and{"voiceprint": ...}change it while it runs. It returns the samples that are ready: a little less than the input at the start (Focus's 16 ms), then about the input's size.AlkoveVADAnalyzergives Cue's speech probability every 30 ms, at any input rate. Cue was tuned with a confidence of 0.5, so that is its default. BehindAlkoveFilter, it hears only the user.
example.py runs both on your microphone and prints when you speak.
Tested with pipecat-ai 1.13.0.
License
Apache-2.0. See NOTICE.
Metadata
Release files for pipecat-alkove 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pipecat_alkove-0.2.0.tar.gz | 9.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pipecat_alkove-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.7 kB
Release files / pipecat_alkove-0.2.0.tar.gz
| Download URL | pipecat_alkove-0.2.0.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d8d9f46b4ab1512c52897d7ab8827c9c2b8e683a475b47d90517ffe583af4d33
|
|
BLAKE2b-256 checksum How to use checksums |
228b311601e3bbb9949201c2cef5099ee9d9b9af970ad6626b0b682d19d29a1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logRelease files / pipecat_alkove-0.2.0-py3-none-any.whl
| Download URL | pipecat_alkove-0.2.0-py3-none-any.whl |
|---|---|
| Size | 10.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
79f4a4bc27868d304db10cd4d8892cec3b09e04a3f7de9972a4343b640043175
|
|
BLAKE2b-256 checksum How to use checksums |
5f670e9dee3d21573d39d090980df3ba06b468441d21641ce964ce0a508ffa0e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logSecurity for pipecat-alkove 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pipecat_alkove-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.