Skip to main content
Loss of provenance

A previous release had provenance metadata, but this release does not. View details.

laidline-pipecat

A Pipecat FrameProcessor that sits right after the TTS service. It marks every TTS audio frame with streaming AudioSeal and writes one Laidline evidence entry per utterance.

pip install laidline-pipecat   # pulls laidline[audio] and pipecat-ai>=1.12,<2
from laidline import MarkContext, Marker
from laidline_pipecat import LaidlineTTSProcessor

marker = Marker.from_config("laidline.yaml")  # in-process: keys, models and evidence stay on your host
pipeline = Pipeline(
    [
        transport.input(),
        stt,
        context_aggregator.user(),
        llm,
        tts,
        LaidlineTTSProcessor(marker, ctx=MarkContext(route="pipecat:support-bot", tenant="acme")),
        transport.output(),
        context_aggregator.assistant(),
    ]
)

What it does

  • Each downstream TTSAudioRawFrame is replaced by a copy carrying the marked PCM. The copy keeps the same length, rate, channels, pts, transport_destination, context_id and metadata. Every other frame passes through unchanged.
  • TTSStartedFrame opens an utterance. TTSStoppedFrame, InterruptionFrame, EndFrame, CancelFrame and processor cleanup close it. Closing writes one marked evidence entry with modality: audio, watermark.streaming: true, the payload and issuer id, the duration, your ctx, and the TTS context_id under extra.context_id. An utterance that changes sample rate part-way gets one entry per format.
  • It needs an in-process Marker with watermark.audio.enabled: true. A MarkClient raises TypeError, because the streaming path has no HTTP form. A Marker with audio watermarking disabled raises ValueError.
  • A marking failure raises out of process_frame. Pipecat reports it as an error and does not push the unmarked frame.
  • The embedder is AudioSeal's streaming card (watermark.audio.stream_kind: block, the only kind).

What it does not do

  • Audio below 16 kHz (an 8 kHz phone bot) is not marked: it passes through unchanged and the entry says watermark: null, watermark_skipped:rate_below_16k. The streaming mark does not survive below 16 kHz.
  • A stream carries no C2PA manifest (c2pa: null, warning manifest_skipped:streaming). The watermark and the evidence entry are the provenance for live audio.
  • For a recording you store, sign the file itself with marker.mark_audio(..., fmt="wav" | "flac" | "mp3" | "m4a"). This embeds a manifest and adds the batch mark. Laidline's /v1/audio/speech proxy in streaming mode stores a signed twin of a response only when watermark.audio.store_signed_twin is enabled and only for a stream that completed.

Survival

Measured 2026-09-27 on LibriSpeech test-clean, 500 speech clips. The detection threshold is 0.39, which gave a 0.75 % false-positive rate. Figures are the share of clips on which the streaming-mode mark (the one this plugin embeds) is still detected:

Transform Streaming mode
Opus 24 kbps 100 %
Opus 48 kbps 100 %
MP3 64 kbps 100 %
AAC 64 kbps 100 %
G.711 mu-law 0 %
8 kHz resampling 0 %
EnCodec 6 kbps 100 % detected, 0 % exact issuer
Mimi 0 %

The streaming mark survives an offline Opus transcode at 24 and 48 kbps (100 percent on 500 LibriSpeech clips); no WebRTC session, packet loss or jitter was tested. It does not survive a simulated phone leg (G.711 codec simulation). The streaming mark was not run over a real call. For phone deployments, provenance comes from the evidence entry and from C2PA on stored recordings, not from the watermark. For comparison, the batch (non-streaming) mark that mark_audio embeds survives simulated G.711 and 8 kHz at 100 %, and a real call with the batch mark: 99 % (100 Twilio number-to-number calls recorded at the callee, G.711 8 kHz, carrier routing unconfirmed and possibly on-net, measured 2026-09-27).

Mean embed SNR is 17.4 dB (5th percentile 8.7 dB), which is audible on some voices. Listen to your own voices before you ship.

The full numbers and method are in the benchmarks page ("Audio robustness"), and what was tested, and how, in https://laidline.com/docs/integrations/pipecat. Streaming sessions, detection and the operating threshold are in https://laidline.com/docs/integrations/audio.

Metadata

Release files for laidline-pipecat 1.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Loss of provenance

These files do not have provenance metadata, despite files in a prior release including this data.

We recommend further investigation before installing these files. View details.

Source distribution (sdist)

Source distribution for laidline-pipecat 1.0.1
File Size Uploaded Provenance Actions
laidline_pipecat-1.0.1.tar.gz 12.4 kB Without provenance Details for laidline_pipecat-1.0.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for laidline-pipecat 1.0.1
File Interpreter ABI Platform Actions
laidline_pipecat-1.0.1-py3-none-any.whl Python 3 none any Details for laidline_pipecat-1.0.1-py3-none-any.whl

Total release size: 26.2 kB

Release files / laidline_pipecat-1.0.1.tar.gz

Loss of provenance

This file belongs to a release without provenance metadata, despite a prior release including this data.

We recommend further investigation before installing this file. View details.

Download URL laidline_pipecat-1.0.1.tar.gz
Size 12.4 kB
Tags Source
SHA-256 checksum
How to use checksums
283b6728ab391cbf8be2c55b1b28bfcbca3dae85eff16c7a9f47f66790d28508
BLAKE2b-256 checksum
How to use checksums
2459af4499ffb357ce1f743944da37dfc0683dbbb3ea4c1d4b58269086236e7a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.7

Release files / laidline_pipecat-1.0.1-py3-none-any.whl

Loss of provenance

This file belongs to a release without provenance metadata, despite a prior release including this data.

We recommend further investigation before installing this file. View details.

Download URL laidline_pipecat-1.0.1-py3-none-any.whl
Size 13.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ee0b1a1e5e163b1aba26427b5d6a53b2133464b2fcb7a26df96eea9cd4845a24
BLAKE2b-256 checksum
How to use checksums
30347de06616574c4fc525e7105e420b2cf0e64994573aa4e91f4efce62aed10
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.7

Security for laidline-pipecat 1.0.1

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.

Loss of provenance

A previous release of these files had provenance metadata, but this release does not.

While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.

Release comparison

  • Removed 1.0.0 2 files With provenance
  • Added 1.0.1 2 files Without provenance

A 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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page