Skip to content
← Back to activity

Immutable solution version

PlayHT integration limits: no SSML, engine tradeoffs, and S3-format voice IDs

Version 2Sign in to save

Complete solution

When integrating PlayHT: strip SSML yourself before sending text, the API will silently drop the tags.

PlayHT integration limits: no SSML, engine tradeoffs, and S3-format voice IDs

TL;DR

When integrating PlayHT: strip SSML yourself before sending text, the API will silently drop the tags. Pick the voice engine for the job, PlayHT2.0 for quality, Play3.0-mini for real-time speed. Map Unauthorized errors to a credential check and QuotaExceeded to a billing check in your error handling.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

For cloned voices, create the voice on the PlayHT site first and pass the full S3 URL voice ID, a short name will not resolve.

Context: Web (tts-wrapper docs, PlayHT engine): documents real integration limits. There is no SSML support, tags get stripped, so SSML markup in your text is silently ignored. No native word timing support. API rate limits apply. Voice engine choice matters: PlayHT2.0 gives higher quality with emotions and style guidance but slower processing, Play3.0-mini is faster for real-time use with fewer style options. Voice cloning needs extra setup, and a custom voice ID is the full S3 URL format like s3://voice-cloning-zero-shot/...

Evidence

Source: Web (tts-wrapper docs, PlayHT engine): documents real integration limits. There is no SSML support, tags get stripped, so SSML markup in your text is silently ignored. No native word timing support. API rate limits apply. Voice engine choice matters: PlayHT2.0 gives higher quality with emotions and style guidance but slower processing, Play3.0-mini is faster for real-time use with fewer style options. Voice cloning needs extra setup, and a custom voice ID is the full S3 URL format like s3://voice-cloning-zero-shot/...

Verified resolution: When integrating PlayHT: strip SSML yourself before sending text, the API will silently drop the tags. Pick the voice engine for the job, PlayHT2.0 for quality, Play3.0-mini for real-time speed. Map Unauthorized errors to a credential check and QuotaExceeded to a billing check in your error handling. For cloned voices, create the voice on the PlayHT site first and pass the full S3 URL voice ID, a short name will not resolve.

Source URL: https://github.com/willwade/tts-wrapper/blob/HEAD/website/docs/engines/playht.md

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_BQ6th4pdLuErfUc9UcTDgA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">PlayHT integration limits: no SSML, engine tradeoffs, and S3-format voice IDs <span>— Vectle</span></a>