Skip to content
Notifications
Clear all

Breaking: They quietly removed some of the older robotic voices from the library.

3 Posts
3 Users
0 Reactions
9 Views
(@martech_tester_2)
Trusted Member
Joined: 2 months ago
Posts: 35
Topic starter   [#174]

Hey everyone, I was doing my weekly voice model audit in PlayHT (yes, I keep a spreadsheet for this too, don't judge! 😅) and I noticed something pretty significant. It looks like they've quietly removed a batch of the older, more robotic-sounding voices from their library.

I first noticed because my standard "Test Batch #3" for new projectsβ€”which includes a few of those older voices as a baseline for "acceptable but not great" qualityβ€”came up short. Specifically, the male voice "US-Michael" and the female voice "US-Sarah-C" seem to be gone. I cross-referenced with my archive from last month, and at least five of those earlier generation voices are no longer listed. They aren't just deprecated; they're completely unavailable for new projects.

This is actually a really interesting move. On one hand, it's a clear quality play. Those voices were definitely showing their age compared to the newer Ultra and Generative models. Having them in the library could confuse new users or lead to disappointing results if someone accidentally picked one. It raises the overall floor of quality for the platform.

But on the other hand, it does bring up a few questions for those of us who use PlayHT at scale:

* **Backward Compatibility:** What happens to existing projects that used those voices? I checked one of my older drafts that had "US-Michael," and it seems to still play, but the voice is now labeled differently. Is it being silently mapped to a newer equivalent?
* **Consistency for Ongoing Series:** If you were using one of those voices for a long-running podcast or video series, does this force a re-record or a potentially jarring voice shift?
* **Pricing Transparency:** This isn't a *bad* change, but it's a significant library alteration that wasn't communicated. It makes me wonder what else in the stack (API parameters, pricing tiers) might change with similar quietness.

From a martech stack perspective, this kind of silent update affects reproducibility and asset management. It's a good reminder to always download and archive final audio assets, not just rely on the project staying editable in the platform forever.

Has anyone else spotted specific voices that have vanished? And more importantly, has anyone had to deal with the fallout in a live campaign or content pipeline? I'm curious if the transition for old projects is truly seamless. My spreadsheet is ready for updates!


Test everything, trust nothing


   
Quote
(@startup_ops_lead_jen_2)
Eminent Member
Joined: 4 months ago
Posts: 16
 

That's a solid catch. I used US-Sarah-C for some internal training clips last year because she was cheap and fit the budget. I'm a bit worried now about what happens to existing projects that have those voices embedded. Do they just stop working on the next render, or do they get grandfathered in? It's the kind of quiet change that can break a process if you're not watching.


learning daily


   
ReplyQuote
(@integration_ian)
Estimable Member
Joined: 3 months ago
Posts: 112
 

That's why you never hardcode a resource name into a process. It's a dependency.

Your test batch is broken because it points to a specific voice ID that no longer exists. If PlayHT provided an API for this, you'd point your process to a *voice category* (like "Standard Male US") and let their system resolve the current default voice for that category. That way, deprecations become configuration changes, not broken renders.

But most platforms don't design for that. They just yank the endpoint.


Integration is not a project, it's a lifestyle.


   
ReplyQuote