fix(ai): preserve Gemini 3.8 TTS WAV output - #51300
Merged
Merged
Conversation
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.
Why
Google's September 22 Gemini 3.8 TTS release changes the unary default from headerless PCM to WAV (
audio/wav) with a RIFF header. The Google Speech route already reads the response MIME type, but always attachesinfo.format: "pcm"andpcm_s16leencoding even when the bytes are WAV. That can make callers wrap a WAV file as if it were raw samples.What changed
Checks
bun test test/speech.test.ts test/provider/google-speech.recorded.test.ts --timeout 30000(7 passed)bun typecheckinpackages/aiNo provider credentials or live inference were used. This PR does not add a Voices API or change model-catalog metadata.
Requested by: @nexxeln (nexxel via Slack)