-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for legacy voices. #140
Comments
Actually I did it :) But it can be done more elegant, with say option for legacy voices in config. How is done: |
@patrik-malina thanks |
@patrik-malina I think I found a non-breaking way to add support for legacy with the " (Legacy)" suffix... Can you give this prerelease a try? It should show the (Legacy) suffix next to the old voices, and selecting them that way (with the suffix) should work, as well as specifying the name without the suffix directly in config should work as well. This also updates the default model, feel free to give that a try as well to see if it's faster. |
@carleeno Can confirm, that this works. Thank you. |
System Health details
/
Checklist
Describe the issue
I'm having problem using legacy voices. Used Jeremy voice:
Could not find voice with name {}, available voices: ['Sarah', 'Laura', 'Charlie', 'George', 'Callum', 'Liam', 'Charlotte', 'Alice', 'Matilda', 'Will', 'Jessica', 'Eric', 'Chris', 'Brian', 'Daniel', 'Lily', 'Bill']
I thing this need to implement in code (i'm not coder):
curl --request GET \ --url 'https://api.elevenlabs.io/v1/voices?show_legacy=true'
Reproduction steps
/
Debug logs
Diagnostics dump
No response
The text was updated successfully, but these errors were encountered: