-
Notifications
You must be signed in to change notification settings - Fork 378
Description
Description
Issue Description
When updating a speaker's voice_id via the Update Speaker API, the change does not take effect when calling the Dub Segment API. Despite the voice_id being successfully updated (confirmed via the Get Dubbing Resource API), the generated audio still uses the default clip-clone voice instead of the specified voice from the voice library.
Steps to Reproduce
Call Update Speaker API to modify voice_id to a specific voice from the voice library.
Verify the update using Get Dubbing Resource API (confirms voice_id is correctly set).
Call Dub Segment API (e.g., dubbingId: NmAplV31y4jhQXqso46t).
Observe that the output audio still uses clip-clone instead of the specified voice.
Expected Behavior
The Dub Segment API should generate audio using the updated voice_id from the speaker settings.
Actual Behavior
The generated audio ignores the updated voice_id and defaults to clip-clone.
Code example
No response
Additional context
No response