mudler / mudler/LocalAI

API to list TTS voices

Open
#11,604 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
49.2k
Forks
4.5k
Avg merge
1d 3m
Merged PRs (30d)
239

Description

Is your feature request related to a problem? Please describe.

With TTS models, i would like to know which languages / voices / gender i can use with each model, without digging the whole documentation and sometimes don't find the answer

Describe the solution you'd like

I would like to have an API endpoints that request at least for a specified model, ideally for all installed models, which languages, voices and gender are available

Maybe something like this (i don't really care about the format) :

{
	[model]: {
		[language]: [
			[voice_name, gender]
		]
	}
}

Example for pocket-tts :

{
	"pocket-tts": {
        "de_DE": [
            [
                "MALE",
                "juergen"
            ]
        ],
        "en_US": [
            [
                "MALE",
                "alba"
            ],
            [
                "MALE",
                "bill_boerst"
            ],
            [
                "MALE",
                "charles"
            ],
            [
                "MALE",
                "george"
            ],
            [
                "MALE",
                "javert"
            ],
            [
                "MALE",
                "jean"
            ],
            [
                "MALE",
                "marius"
            ],
            [
                "MALE",
                "michael"
            ],
            [
                "MALE",
                "paul"
            ],
            [
                "MALE",
                "peter_yearsley"
            ],
            [
                "MALE",
                "stuart_bell"
            ],
            [
                "FEMALE",
                "anna"
            ],
            [
                "FEMALE",
                "azelma"
            ],
            [
                "FEMALE",
                "caro_davy"
            ],
            [
                "FEMALE",
                "cosette"
            ],
            [
                "FEMALE",
                "eponine"
            ],
            [
                "FEMALE",
                "eve"
            ],
            [
                "FEMALE",
                "fantine"
            ],
            [
                "FEMALE",
                "jane"
            ],
            [
                "FEMALE",
                "mary"
            ],
            [
                "FEMALE",
                "vera"
            ]
        ],
        "es_ES": [
            [
                "FEMALE",
                "lola"
            ]
        ],
        "fr_FR": [
            [
                "FEMALE",
                "estelle"
            ]
        ],
        "it_IT": [
            [
                "MALE",
                "giovanni"
            ]
        ],
        "pt_PT": [
            [
                "MALE",
                "rafael"
            ]
        ]
    }
}

Describe alternatives you've considered

Manually digging the documentation for each model and try to find the answer

Additional context

Related to this question #11600

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing TTS API and model integration, then read related issue #11600 and the linked pocket-tts README for metadata examples. Done means an endpoint can report languages, voices, and gender for a specified model and ideally all installed models, with a documented response format.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.