[Feat] support AutoPipelineForText2Audio#13511
Conversation
Signed-off-by: Lancer <[email protected]>
7a7d032 to
4ac3e90
Compare
sayakpaul
left a comment
There was a problem hiding this comment.
Thanks! I think it'd be nice to also have an auto class for T2V ones.
| ``` | ||
|
|
||
| There are three types of [AutoPipeline](../api/models/auto_model) classes, [`AutoPipelineForText2Image`], [`AutoPipelineForImage2Image`] and [`AutoPipelineForInpainting`]. Each of these classes have a predefined mapping, linking a pipeline to their task-specific subclass. | ||
| There are four types of [AutoPipeline](../api/models/auto_model) classes, [`AutoPipelineForText2Image`], [`AutoPipelineForImage2Image`], [`AutoPipelineForInpainting`] and [`AutoPipelineForText2Audio`]. Each of these classes have a predefined mapping, linking a pipeline to their task-specific subclass. |
There was a problem hiding this comment.
(nit): We could bullet them at this point, I think.
There was a problem hiding this comment.
Good point, updated this section to a bullet list for readability
Signed-off-by: Lancer <[email protected]>
Thanks for the suggestion. I’ll add the video auto classes, including T2V/I2V, in a follow-up PR, and keep this one scoped to text-to-audio. |
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
|
@bot /style |
|
Style bot fixed some files and pushed the changes. |
* [Feat] support AutoPipelineForText2Audio Signed-off-by: Lancer <[email protected]> * upd Signed-off-by: Lancer <[email protected]> * Apply style fixes --------- Signed-off-by: Lancer <[email protected]> Co-authored-by: dg845 <[email protected]> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
What does this PR do?
support AutoPipelineForText2Audio for ext2Audio model
audio.wav
Before submitting
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.