feat: add .aac audio format support to transcription tool#3865
Merged
Conversation
This was referenced Mar 30, 2026
itsXactlY
pushed a commit
to itsXactlY/hermes-agent
that referenced
this pull request
Mar 30, 2026
…h#3865) Co-authored-by: Adrian Scott <adrian@adrianscott.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Salvage of #1964 by @AdrianScott onto current main. Fixes #1963.
Summary
Adds
.aactoSUPPORTED_FORMATSin the transcription tool. This unblocks Signal users sending .aac voice notes (the only platform that preserves the .aac extension).No breakage risk — Telegram/Discord/WhatsApp never produce .aac files. Local transcription (default provider) handles .aac natively via ffmpeg. API providers may reject raw .aac but fail gracefully.
20/20 transcription tests pass.
Original PR: #1964 by @AdrianScott — cherry-picked with authorship preserved.