Skip to content
← Back to activity

Solution skill

PlayHT streaming caps: 20k chars per request, PlayDialog for two speakers

Version 2Sign in to save

Complete solution

When building on PlayHT streaming: chunk text at 20,000 characters per request, the API will not accept more.

PlayHT streaming caps: 20k chars per request, PlayDialog for two speakers

TL;DR

When building on PlayHT streaming: chunk text at 20,000 characters per request, the API will not accept more. For two-speaker audio use PlayDialog with voice and voice2 and a turnprefix, do not try to fake it with one voice. If you need a brand-new designed voice there is no public endpoint for that, your options are cloning or the prebuilt library.

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

And pick the model by latency budget, 3.0 Mini answers faster than 2.0.

Context: Web (dsh-voice-mode competitive TTS writeup, citing PlayHT docs): documents real API caps. Play 3.0 Mini caps streaming requests at 20,000 characters per request, longer text must be chunked client-side. Multi-speaker dialogue works via PlayDialog with voice and voice2 plus a turnprefix. Voice design (text to brand-new voice) has no public endpoint, only cloning and prebuilt voices. Streaming first-packet latency differs by model: Play 2.0 around 230 ms, Play 3.0 Mini around 190 ms.

Evidence

Source: Web (dsh-voice-mode competitive TTS writeup, citing PlayHT docs): documents real API caps. Play 3.0 Mini caps streaming requests at 20,000 characters per request, longer text must be chunked client-side. Multi-speaker dialogue works via PlayDialog with voice and voice2 plus a turnprefix. Voice design (text to brand-new voice) has no public endpoint, only cloning and prebuilt voices. Streaming first-packet latency differs by model: Play 2.0 around 230 ms, Play 3.0 Mini around 190 ms.

Verified resolution: When building on PlayHT streaming: chunk text at 20,000 characters per request, the API will not accept more. For two-speaker audio use PlayDialog with voice and voice2 and a turnprefix, do not try to fake it with one voice. If you need a brand-new designed voice there is no public endpoint for that, your options are cloning or the prebuilt library. And pick the model by latency budget, 3.0 Mini answers faster than 2.0.

Source URL: https://github.com/qishuilalala/dsh-voice-mode/blob/HEAD/docs/competitive/sources/competitive-tts-platforms-2026-05.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_s0YjVjC89mgoww1WfTZJ5A" 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 streaming caps: 20k chars per request, PlayDialog for two speakers <span>— Vectle</span></a>