Repository navigation
Add support for Voxtral-4B-TTS-2603 to transformers - #45401
Closed
sachinkumarsingh092 wants to merge 13 commits into
Closed
sachinkumarsingh092 wants to merge 13 commits into
sachinkumarsingh092 wants to merge 13 commits into
Conversation
Signed-off-by: Sachin Singh <sachinkumarsingh092@gmail.com>
Signed-off-by: Sachin Singh <sachinkumarsingh092@gmail.com>
Signed-off-by: Sachin Singh <sachinkumarsingh092@gmail.com>
Signed-off-by: Sachin Singh <sachinkumarsingh092@gmail.com>
Signed-off-by: Sachin Singh <sachinkumarsingh092@gmail.com>
Signed-off-by: Sachin Singh <sachinkumarsingh092@gmail.com>
Signed-off-by: Sachin Singh <sachinkumarsingh092@gmail.com>
Signed-off-by: Sachin Singh <sachinkumarsingh092@gmail.com>
Signed-off-by: Sachin Singh <sachinkumarsingh092@gmail.com>
Signed-off-by: Sachin Singh <sachinkumarsingh092@gmail.com>
Signed-off-by: Sachin Singh <sachinkumarsingh092@gmail.com>
Signed-off-by: Sachin Singh <sachinkumarsingh092@gmail.com>
Contributor
|
[For maintainers] Suggested jobs to run (before merge) run-slow: auto, voxtral_tts |
2 tasks done
Contributor
|
View the CircleCI Test Summary for this PR: https://huggingface.co/spaces/transformers-community/circle-ci-viz?pr=45401&sha=bdac96 |
Member
|
hi @sachinkumarsingh092, are you still working on this? if not, would you mind if i rebased your commits (preserving your git author status and contributions) and continued in a new PR? |
Author
|
That'd be great. Thanks for the help. |
grisaitis
added a commit
to grisaitis/transformers
that referenced
this pull request
Sep 7, 2026
The original PR updated configuration_auto.py and processing_auto.py, but main has since moved those mappings into auto_mappings.py. This commit adds the voxtral_tts entries there so AutoConfig / AutoProcessor resolve correctly. Original PR: huggingface#45401
grisaitis
added a commit
to grisaitis/transformers
that referenced
this pull request
Oct 6, 2026
The original PR updated configuration_auto.py and processing_auto.py, but main has since moved those mappings into auto_mappings.py. This commit adds the voxtral_tts entries there so AutoConfig / AutoProcessor resolve correctly. Original PR: huggingface#45401
Collaborator
|
Thanks for the PR, and sorry it didn't make it in! It has been inactive for a long time and the codebase has changed a lot since (v5), so closing it. Feel free to open a fresh PR against |
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.
What does this PR do?
Fixes #45027
Voxtral-4B-TTS-2503 currently does not have support for inference via transformers library and only uses vllm-omni. This PR adds that.
Paper: https://arxiv.org/abs/2603.25551v2
Huggingface card: https://huggingface.co/mistralai/Voxtral-4B-TTS-2603
Code Agent Policy
The Transformers repo is currently being overwhelmed by a large number of PRs and issue comments written by
code agents. We are currently bottlenecked by our ability to review and respond to them. As a result,
we ask that new users do not submit pure code agent PRs at this time.
You may use code agents in drafting or to help you diagnose issues. We'd also ask autonomous "OpenClaw"-like agents
not to open any PRs or issues for the moment.
PRs that appear to be fully agent-written will probably be closed without review, and we may block users who do this
repeatedly or maliciously.
This is a rapidly-evolving situation that's causing significant shockwaves in the open-source community. As a result,
this policy is likely to be updated regularly in the near future. For more information, please read
CONTRIBUTING.md.Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.