Skip to content

fix: Qwen3 TTS - handle mixed types in spkId and spkIsDialect for CustomVoice model#146

Merged
lucasnewman merged 1 commit intoBlaizzy:mainfrom
Ichigo3766:fix/custom-voice-config
Apr 9, 2026
Merged

fix: Qwen3 TTS - handle mixed types in spkId and spkIsDialect for CustomVoice model#146
lucasnewman merged 1 commit intoBlaizzy:mainfrom
Ichigo3766:fix/custom-voice-config

Conversation

@Ichigo3766
Copy link
Copy Markdown
Contributor

The Qwen3-TTS CustomVoice config.json has:

  • spk_id: {"ryan": 3061, ...} (single Int per speaker, not [Int])
  • spk_is_dialect: {"ryan": false, "eric": "sichuan_dialect", ...} (Bool or String)

The Base model had empty dicts {}, so these bugs were never hit. Added SpkIdValue and SpkDialectValue flexible decoders to handle both variants without breaking the Base model path.

The Qwen3-TTS CustomVoice config.json has:
  - spk_id: {"ryan": 3061, ...}  (single Int per speaker, not [Int])
  - spk_is_dialect: {"ryan": false, "eric": "sichuan_dialect", ...}  (Bool or String)

The Base model had empty dicts {}, so these bugs were never hit.
Added SpkIdValue and SpkDialectValue flexible decoders to handle both
variants without breaking the Base model path.
@Ichigo3766 Ichigo3766 changed the title fix: handle mixed types in spkId and spkIsDialect for CustomVoice model fix: Qwen3 TTS - handle mixed types in spkId and spkIsDialect for CustomVoice model Apr 9, 2026
Copy link
Copy Markdown
Collaborator

@lucasnewman lucasnewman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@lucasnewman lucasnewman merged commit 56d0811 into Blaizzy:main Apr 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants