Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: WhatsApp voice messages are unplayable when using Microsoft Edge TTS — WebM/Opus not accepted, requires OGG/Opus [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#81522•Fetched 2026-05-14 03:31:15
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
2
Author
warcoldwarcold
Participants
clawsweeper[bot]clawsweeper[bot]warcoldwarcold
Timeline (top)
labeled ×2closed ×1commented ×1mentioned ×1

Microsoft Edge TTS outputs WebM/Opus audio, but WhatsApp PTT only accepts OGG/Opus — so voice messages sent via WhatsApp arrive as broken, unplayable attachments.

Error Message

Recipients receive a broken audio attachment on every voice message. No error on the sender side — the PTT dispatch succeeds, but WhatsApp rejects the WebM container on the receiving end.

Root Cause

Microsoft Edge TTS outputs WebM/Opus audio, but WhatsApp PTT only accepts OGG/Opus — so voice messages sent via WhatsApp arrive as broken, unplayable attachments.

Fix Action

Fix / Workaround

Voice messages should arrive as normal, playable PTT audio notes in WhatsApp. If the TTS outputs WebM and the channel needs OGG, that remux should happen automatically in the pipeline before dispatch.

Microsoft Edge TTS → WhatsApp PTT dispatch

Recipients receive a broken audio attachment on every voice message. No error on the sender side — the PTT dispatch succeeds, but WhatsApp rejects the WebM container on the receiving end.

Code Example

Recipients receive a broken audio attachment on every voice message. No error on the sender side — the PTT dispatch succeeds, but WhatsApp rejects the WebM container on the receiving end.
RAW_BUFFERClick to expand / collapse

Bug type

Crash (process/app exits or hangs)

Beta release blocker

No

Summary

Microsoft Edge TTS outputs WebM/Opus audio, but WhatsApp PTT only accepts OGG/Opus — so voice messages sent via WhatsApp arrive as broken, unplayable attachments.

Steps to reproduce

  1. Configure TTS with Microsoft Edge TTS using format: webm-24khz-16bit-mono-opus.
  2. Have the bot send a voice/PTT message on WhatsApp.
  3. The recipient gets a broken attachment they can't play instead of a normal voice note.
  4. This only affects WhatsApp PTT — text messages and Discord audio are completely unaffected.

Expected behavior

Voice messages should arrive as normal, playable PTT audio notes in WhatsApp. If the TTS outputs WebM and the channel needs OGG, that remux should happen automatically in the pipeline before dispatch.

Actual behavior

The raw WebM file from Edge TTS is sent directly to WhatsApp as PTT. WhatsApp doesn't accept WebM containers for voice notes — recipients see a broken file that won't play.

OpenClaw version

OpenClaw version: v2026.5.7

Operating system

Kali Linux

Install method

npm global (npm install -g openclaw)

Model

N/A — TTS output/channel format mismatch, not model-specific.

Provider / routing chain

Microsoft Edge TTS → WhatsApp PTT dispatch

Additional provider/model setup details

TTS config used: provider: microsoft, format: webm-24khz-16bit-mono-opus, voice: es-MX-DaliaNeural

Logs, screenshots, and evidence

Recipients receive a broken audio attachment on every voice message. No error on the sender side — the PTT dispatch succeeds, but WhatsApp rejects the WebM container on the receiving end.

Impact and severity

  • Affected: Anyone using Microsoft Edge TTS (or any WebM-outputting TTS) with WhatsApp
  • Severity: Medium — voice messages broken, text still works fine
  • Frequency: 100% when TTS format is WebM-based
  • Consequence: Bot can't send voice notes on WhatsApp

Additional information

Fix: remux WebM → OGG using ffmpeg before dispatching to WhatsApp. No re-encoding, just a container swap — near-instantaneous:

ffmpeg -i input.webm -c:a copy output.ogg

Applied in the WhatsApp speech provider before PTT dispatch. Can be made conditional:

if (channel === 'whatsapp' && format.startsWith('webm')) { /* remux */ }

ffmpeg is standard on any Linux deployment.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Voice messages should arrive as normal, playable PTT audio notes in WhatsApp. If the TTS outputs WebM and the channel needs OGG, that remux should happen automatically in the pipeline before dispatch.

#model compatibility#GPU setup#container setup#orchestration issue#cache issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING