SShortSingh.
Back to feed

Small TTS Models Post Strong Benchmarks, but Latency Claims Are Being Misreported

0
·3 views

A blog post found that a widely repeated figure of 13.7ms time-to-first-audio for Zyphra's ZONOS3-Mini does not appear in the technical report, which lists 85ms on an H100 and 80ms at eight concurrent requests. The author argues the inflated number spread because it sounded more impressive than the paper's actual result. Several small text-to-speech models were released in mid-November 2025, including tiny-voca, Inflect v3 and sanoTTS, with the author noting that tiny-voca was trained entirely on synthetic audio generated by a larger model. Benchmark comparisons across these models are not directly matched, since they use different test panels and metric variants. The piece concludes that 'real time' performance varies by hardware and that reported figures often disagree with the underlying papers.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingHacker News ·

Researcher Uses AI to Survey Theoretical Astrophysics Literature

A blog post describes an experiment in which an AI system was asked to read and analyze the body of work in theoretical astrophysics. The author, Casey Handmer, shares the results on his personal site, which is hosted under a physics section. The Hacker News submission received few votes and no comments at the time it was captured. The source material available provides only the link and metadata, so the specific findings and methodology cannot be verified here.

0
ProgrammingDEV Community ·

Moodle 5.1 moves web root to public/; nginx config must follow

Moodle 5.1 relocated the web-accessible files into a public/ subdirectory, which is now the dirroot. Servers still pointing their document root at the install root will expose source files such as config.php, composer files, vendor/, and .git. The article recommends checking what PHP reports for root, dirroot, wwwroot, and dataroot against the web server configuration. It also suggests probing the public hostname to confirm sensitive paths return 404 while index.php and pluginfile.php remain reachable. The dataroot should stay outside both directories and must not be moved into public/.

0
ProgrammingDEV Community ·

Doofinder and Queryra tested on WooCommerce search: plain-language queries show gaps

A developer compared Doofinder, an established Spanish site-search service, with Queryra, his own hosted WooCommerce search plugin. He tested six live Doofinder-powered stores on 9 November 2026 by typing exact product names, typos, everyday-language needs, price limits and exclusions. Doofinder handled exact names and typos well but often failed on everyday phrasing, and in no store did it apply a typed price limit. The author's own demo store, which uses a smaller and partly self-chosen set of queries, produced stronger results for Queryra, a comparison he acknowledges is not like-for-like. The article also quotes Doofinder's marketing and documentation claims about NLP and semantic search, which the author contrasts with the observed results.

0
ProgrammingDEV Community ·

Who Owns Security? Why Responsibility Is Shared Across Three Core Areas

Many organizations spread security responsibility so thinly that nobody feels fully accountable, leaving gaps that attackers can exploit. Security is commonly divided into physical, technical (cyber), and administrative areas, and a strong program must cover all three rather than relying on software alone. Accountability is layered across senior leadership, the security function, plant and operations management, engineering, IT teams, employees, and vendors. The article notes that the merging of IT and operational technology (OT) has created a gray zone where tasks such as patching industrial systems often fall through the cracks. It recommends a responsibility matrix that assigns an owner, supporting party, and escalation contact for each key activity.