Fix: Ensure consistent audio MIME type in LiveRequestQueue#5584
Closed
9chait9 wants to merge 1 commit intogoogle:mainfrom
Closed
Fix: Ensure consistent audio MIME type in LiveRequestQueue#55849chait9 wants to merge 1 commit intogoogle:mainfrom
9chait9 wants to merge 1 commit intogoogle:mainfrom
Conversation
… for streaming stability.
adk-bot
added
the
live
Collaborator
|
Response from ADK Triaging Agent Hello @9chait9, thank you for creating this PR! Could you please include a |
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
2 participants
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.
Fixes #5552
This PR addresses the intermittent
APIError: 1007 None (Invalid Audio Format)occurring during active audio streaming with the Multimodal Live API. The fix explicitly sets themime_typeto "audio/pcm;rate=16000" when queuing audio blobs inLiveRequestQueue.send_realtime.This change ensures that the audio format information is consistently and correctly communicated, mitigating potential issues where the type might be implicitly lost or misinterpreted downstream, which could lead to server-side validation failures.