TTS Opus encoding quality fixes for Telegram voice
NousResearch/hermes-agent · cluster 18818 · agent
Data as of
Nothing open on GitHub. Fix merged in #73508. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #73508. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #73508. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests address suboptimal Opus audio encoding in TTS output, specifically targeting quality loss in Telegram voice messages. A related fix addresses platform-aware TTS delivery logic and a memory filtering concern.
Open issues0
Open PRs0
Fixes on record
-
#73508 fix(gateway): platform-aware auto-TTS voice delivery (opus platforms, streamed/global gap, captions)
files:
contributors/emails/[redacted:email],contributors/emails/[redacted:email],contributors/emails/[redacted:email],gateway/platforms/base.py,gateway/run.py,plugins/platforms/feishu/adapter.py,plugins/platforms/matrix/adapter.py,plugins/platforms/telegram/adapter.py,tests/gateway/test_auto_voice_reply_format.py,tests/gateway/test_base_auto_tts_output_format.py,tests/gateway/test_matrix_voice.py,tests/gateway/test_telegram_voice_caption_markdown.py,tests/gateway/test_voice_command.py,tests/tools/test_tts_opus_routing.py,tools/tts_tool.py
3 PRs closed without merging
From the close comments: done elsewhere 2 · merged via another change 1
-
#18861 fix(tts): improve Opus encoding quality for Telegram voice messages · merged via another change →
f440a44,#73508 -
#27472 fix(memory): filter Hindsight auto-retain noise · done elsewhere →
09d6603 -
#30066 fix(tts): optimize Opus output for Telegram voice · done elsewhere →
f440a44,#73508,#62040
Closed issues · 1
- Closed#18818TTS: Suboptimal Opus encoding for Gemini/Edge TTS causes quality loss in Telegram voice messages
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- agent
- Merged PRs
- #73508
- Closed issues
- 1
- Attempts
- 3 PRs closed without merging
- Fix link checked
- 28 Jul 2026