sanoTTS is an open-source GPLv3 family of tiny neural text-to-speech models released by the Ampixa/ampixa account, with project listings claiming fully local operation without an NPU and real-time inference on an approximately $3 ESP-class microcontroller. The release claims a 294K-parameter, 337 KB complete stack plus larger variants, multilingual support, and benchmark results competitive with models several times larger. The supplied snippets support the broad constrained-edge claim, but model-size descriptions vary—from 294K in the release claim to 745K–1.8M in the Hugging Face excerpt—and the performance and “smallest” assertions appear to be project-authored rather than independently verified.
2026-10-05T16:00:12Z
Lokutor has turned from pattern-corroborator into a direct competitor on a ~two-week shipping cadence (Oído ASR → Ito → ItoTTS), and its self-published UTMOS eval placing ItoTTS above sanoTTS is the first outside-team benchmark contact with the model — but it is competitor-authored with the evaluated sanoTTS variant unspecified, so the 294K/337 KB, real-time and tiny-variant quality claims remain single-source. ItoTTS's own lukewarm launch (10 pts, ratio slipping to 0.86, HN at 2/2 with an untested-on-hardware question) keeps this a dormant two-horse MCU-TTS evaluation race: low heat, watching, promotion still gated on an independent run, integration, or measurement of the tiny variant itself.
2026-10-05T15:30:48Z
evidence attached: reddit.post.1wy8ske — Lokutor's ItoTTS is the first direct MCU-TTS competitor, its own eval ranking above sanoTTS on UTMOS — corroborating competition and momentum in the microcontroller-TTS episode (same team as the Oído case).
2026-10-02T15:49:23Z
Ito upgrades Lokutor from cross-task to same-task support: two independent teams (Ampixa, Lokutor) now have shipped on-device neural TTS artifacts on ESP-class MCUs, which is as strong as the pattern layer gets without touching the claim — but Ito's 4.9 MB streaming footprint on the same chip family (~15x the claimed stack, PSRAM-class, launched to ~zero traction) leaves the specific 294K/337 KB, real-time and tiny-variant quality assertions single-source, so the case stays watching with promotion still gated on an independent run or integration of the tiny variant itself.
2026-10-02T15:25:28Z
evidence attached: hn.story.49934308 — Ito's streaming neural TTS (4.9MB, no NPU/cloud) on the ESP32-S3 from the Lokutor org is a second, independent on-device TTS artifact bearing directly on whether neural TTS on microcontrollers is becoming practical.
2026-10-02T06:46:09Z
The velocity-spike alerts resolved into nothing: they were the Oído post's vote tail crossing percentile thresholds, and all three posts now sit at ~zero engagement with no new comments, evidence, or validation. The case's meaning is unchanged — the tiny-neural-speech-on-cheap-MCU pattern has second-team support, but sanoTTS's 294K/337 KB, real-time and tiny-variant quality claims remain project-authored — so it stays a dormant low-heat evaluation candidate; third-party integrations (audio.cpp, Home Assistant Voice were both requested in comments) remain the most plausible route to independent validation, so expiring now would be premature.
2026-09-30T12:38:28Z
The independent Lokutor/Oído result (Whisper-tiny-beating 13M-param ASR on a $5 ESP32-S3) is the first second-team evidence for the tiny-neural-speech-on-constrained-hardware pattern, but it runs a different task in a far larger memory regime (8 MB PSRAM vs the claimed 337 KB synthesis footprint), so the case now reads as one instance of an independently evidenced pattern rather than a corroborated claim. sanoTTS's specific 294K/337KB runtime, real-time and tiny-variant quality assertions remain unverified and keep the case at watching with high uncertainty.
2026-09-30T12:26:35Z
evidence attached: reddit.post.1wu2jjy — Independent team's Whisper-tiny-beating 13M-param ASR on a $5 MCU substantiates the same tiny-neural-speech-on-constrained-hardware pattern from a second source.
2026-09-20T09:25:55Z
A new anatomy viewer reportedly exposes actual intermediate tensors from the shipped int8 model synthesizing a sentence, making the tiny variant more inspectable than the release claims alone. This is a useful implementation artifact, not independent confirmation of usable real-time TTS within a microcontroller’s memory budget.
2026-09-20T09:21:27Z
evidence attached: reddit.post.1wlbhw8 — The interactive inspection of real shipped sanoTTS tensors materially contextualizes the existing compact microcontroller-TTS release.
2026-09-09T15:35:31Z
Only engagement has changed; there is still no technical evidence establishing usable real-time speech within the microcontroller’s memory budget. Retain the release as a dormant evaluation candidate, keeping the tiny variant’s deployment claims separate from quality scores for larger variants.
2026-09-07T14:35:10Z
This staleness check supplies no new evidence, leaving sanoTTS a dormant evaluation candidate rather than a validated microcontroller speech stack. The unresolved questions remain total runtime memory, real-time performance, and usable speech quality for the 294K variant—not the reported quality of larger models.
2026-09-05T14:25:50Z
The refreshed discussion adds integration requests, not completed implementations or independent validation, leaving the case’s meaning unchanged. The 337 KB artifact remains an evaluation candidate; its runtime memory and usable speech quality on microcontroller hardware are not established by benchmarks for larger variants.
2026-09-05T05:23:22Z
The refreshed discussion still supplies requests for integrations, not completed integrations or independent hardware validation. Keep sanoTTS as an evaluation candidate, with the tiny model’s runtime memory and speech quality distinguished from benchmark claims for larger variants.
2026-09-04T18:26:33Z
The latest refresh is still repetitive deployment interest, with no independent benchmark, microcontroller reproduction, or downstream integration. The case remains dormant pending technical validation; further comment-only changes should not trigger repricing.
2026-09-04T14:36:35Z
The refreshed comments remain repetitive deployment interest and add no independent benchmark, microcontroller reproduction, or downstream integration. Suppress further discussion-only repricing until technical evidence tests the creator-authored footprint, quality, or hardware claims.
2026-09-04T11:29:12Z
The refreshed discussion adds no independent hardware run, benchmark, or downstream integration, so the case’s meaning remains unchanged. Further comment-only movement is repetitive amplification and should be ignored until technical evidence tests the creator-authored claims.
2026-09-04T10:30:20Z
Another comment-only refresh adds no independent hardware reproduction, benchmark, or integration, so the case remains dormant despite continued deployment interest. Revisit only when technical evidence tests the creator-authored footprint, quality, or microcontroller claims.
2026-09-04T09:32:38Z
The refreshed comments remain repetitive deployment enthusiasm and add no independent benchmark, microcontroller reproduction, or downstream integration. The case should stay dormant as an evaluation target until technical validation changes its meaning.
2026-09-04T08:28:04Z
The latest discussion is still repetitive deployment interest rather than independent validation, so the case’s meaning has not changed. Keep it as an evaluation candidate and ignore further comment-only movement unless a hardware reproduction, benchmark, or integration appears.
2026-09-04T07:41:25Z
The refreshed comments add no independent hardware reproduction, benchmark, or integration and do not change the case’s meaning. Treat further discussion-only movement as noise until technical validation appears.
2026-09-04T05:27:24Z
The refreshed discussion adds no independent hardware reproduction, benchmark validation, or downstream implementation; it remains repetitive deployment interest around creator-authored claims. Further comment-only updates should not change the case absent technical evidence.
2026-09-04T04:28:49Z
The refreshed comments remain repetitive deployment interest and feature requests, with no independent hardware reproduction, benchmark, or integration. The release remains a relevant evaluation candidate, but its central footprint, quality, and microcontroller claims are still creator-authored.
2026-09-04T03:33:18Z
The refreshed comments remain deployment enthusiasm and feature requests, adding no independent hardware reproduction, benchmark, or integration. The artifact remains a relevant evaluation target, but its footprint, quality, and $3-microcontroller claims are still creator-authored.
2026-09-04T02:26:00Z
The refreshed comments remain requests and enthusiasm rather than an independent hardware run, benchmark, or integration. The artifact stays a relevant evaluation candidate, but its core size, quality, and $3-microcontroller claims remain creator-authored.
2026-09-04T00:28:22Z
The refreshed discussion remains deployment enthusiasm and feature requests, not an independent microcontroller run, benchmark, or downstream implementation. The release is still a relevant evaluation target, but its central footprint, quality, and hardware-performance claims remain creator-authored.
2026-09-03T23:34:33Z
Refreshed comments continue to show deployment demand but add no independent benchmark, hardware reproduction, or integration. The case remains a promising evaluation target whose central footprint, quality, and microcontroller claims are still creator-authored.
2026-09-03T22:43:17Z
The refreshed discussion adds deployment interest but no independent benchmark, hardware reproduction, or implementation evidence. The case remains an intriguing evaluation target, while repetitive amplification without validation cools its near-term temperature.
2026-09-03T22:29:12Z
grounded: converges/medium — The release converges with Scott’s hardware-aware local-inference work and directly extends his local speech-engine laboratory toward microcontroller-class depl
2026-09-03T22:25:27Z
case created — The released artifact targets an unusually constrained local-inference regime with concrete size, language, quality, and hardware claims.