Skip to content

feat(model/qwen-tts) interface change to multimodal_conversation#58

Merged
kevinlin09 merged 1 commit intodashscope:mainfrom
songguocola:qwentts-refactoring
Sep 15, 2025
Merged

feat(model/qwen-tts) interface change to multimodal_conversation#58
kevinlin09 merged 1 commit intodashscope:mainfrom
songguocola:qwentts-refactoring

Conversation

@songguocola
Copy link
Copy Markdown
Contributor

No description provided.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @songguocola, I'm Gemini Code Assist1! 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 significantly enhances the MultiModalConversation interface by integrating Qwen Text-to-Speech (TTS) functionality. It allows users to generate spoken output directly from text input, expanding the capabilities beyond traditional multimodal conversations. The changes involve modifying the core call methods to accommodate new TTS-specific parameters and updating the data structures to properly handle and return audio outputs.

Highlights

  • Qwen TTS Integration: The MultiModalConversation interface now supports Qwen Text-to-Speech (TTS) capabilities, allowing for speech generation from text.
  • Flexible Input Parameters: The call method has been updated to accept a new text parameter for TTS, making the messages parameter optional. A voice parameter is also introduced for selecting the desired voice.
  • Enhanced Response Structure: The MultiModalConversationOutput now includes an audio field, which is an Audio dataclass containing details like audio data, URL, ID, and expiration time. Usage tracking also includes characters.
  • New Example Script: A new sample file, test_qwen_tts.py, has been added to demonstrate how to use the Qwen TTS feature, including both streaming and non-streaming modes.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adapts the multimodal_conversation interface to support qwen-tts, adding a text parameter and handling audio output. The changes are generally well-implemented. My review includes suggestions to add missing input validation to prevent API errors, refactor the input handling logic for better clarity, and fix incorrect print statements in the new sample file which would cause it to fail.

@kevinlin09 kevinlin09 merged commit 83ef4a9 into dashscope:main Sep 15, 2025
@songguocola songguocola deleted the qwentts-refactoring branch September 17, 2025 12:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants