Cairn
NousResearch/hermes-agent

TTS audio container mismatch and Opus conversion patches

Cluster 57048 · agent/transports. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
7items grouped
Known?
Yes. 7 related items grouped here, 2 issues already closed.
Fix event
No fix has been merged to main. 5 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

Several TTS providers (Edge, Piper, MiniMax, xAI) were saving non-Opus audio under .ogg extensions, breaking Telegram voice bubbles and on-device transcription. Patches add magic-byte container detection and proper transcoding to Opus before delivery.

Open issues0

No open issues.

Open PRs0

No open pull requests.

5 PRs closed without merging

From the close comments: duplicate 2 · stale or abandoned 1 · other 2

  • #57069 fix(tts): convert Edge TTS MP3 to Opus when caller supplies .ogg path · duplicate → #20882, #57048
  • #57080 fix(tts): convert explicit Edge OGG output · stale or abandoned
  • #57190 fix(tts): transcode edge ogg output paths · other → #73072
  • #58848 fix(tts): convert Piper WAV-in-OGG to real Opus on Telegram · other → #73072
  • #59196 fix(tts): convert Piper raw WAV to Opus before sending as .ogg · duplicate → #58848, #58845, #59092
Closed issues · 2
  • Closed#57048Edge TTS provider silently saves MP3 bytes under a .ogg extension when given an explicit .ogg output_path (breaks Telegram voice bubbles)
  • Closed#58845[Bug]: Piper TTS writes raw WAV to .ogg output path — Opus conversion skipped, Telegram shows 0-second voice bubble
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.26: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent/transports
Closed issues
2
Attempts
5 PRs closed without merging

For your agent

The same facts, typed.

cluster/57048.json
cluster/57048.md