[Firebase AI] Add Live API transcripts

[a-maurice]

Description

Provide details of the change, and generalize the change in the PR title above.

Add the ability to receive input and output transcripts from the Firebase AI Live API.

---

Testing

Describe how you've tested these changes.

Running tests locally.

---

Type of Change

Place an x the applicable box:

• Bug fix. Add the issue # below if applicable.
• New feature. A non-breaking change which adds functionality.
• Other, such as a build process or documentation change.

---

[gemini-code-assist]

Summary of Changes

Hello @a-maurice, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces comprehensive support for audio transcription within the Firebase AI Live API. It enables the system to capture and provide both input and output speech transcripts during live sessions, enhancing the interactive AI experience by making the spoken content directly accessible. This is achieved through new configuration options and updates to the API's response structures.

Highlights

• Transcription Support: Added the capability to receive input and output transcripts from the Firebase AI Live API.
• New Configuration Struct: Introduced a new AudioTranscriptionConfig struct for defining speech transcription settings.
• LiveGenerationConfig Update: Extended LiveGenerationConfig to include optional inputAudioTranscription and outputAudioTranscription parameters.
• API Request Handling: Modified LiveGenerativeModel to correctly extract and apply transcription configurations during the ConnectAsync call.
• Response Structure Enhancement: Updated LiveSessionResponse and LiveSessionContent to expose InputTranscription and OutputTranscription properties, along with a new Transcription struct for the transcribed text.
• Documentation Update: The docs/readme.md file was updated to include this new feature in the upcoming release notes.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds support for receiving input and output transcripts from the Firebase AI Live API. The changes introduce new configuration structs (AudioTranscriptionConfig) and response types (Transcription) to handle this functionality. The implementation correctly adds the new fields to the API requests and parses them from the responses. My review focuses on improving the maintainability of how the transcription configurations are passed to the backend. The current method of adding them to one dictionary and then moving them to another is a bit complex and brittle. I've suggested a refactoring to simplify this logic, making the code cleaner and more robust. Overall, this is a great addition of a new feature.