Open general

Known limitations + field reports (playback reliability)

John Lauer · 17d ago

Living tracker for adom-tts playback issues. Post field reports here (not in private threads) so every user sees known issues and their status.

KNOWN LIMITATIONS (current as of v1.9.20):

  1. History clips recorded before v1.9.19 replay WITHOUT their karaoke transcript (words were not persisted back then; unfixable for old clips — everything since carries words).
  2. Long single-request synthesis on the service side remains duration-sensitive; the CLI mitigates by chunking at 360 chars. A server-side streaming/job-poll fix belongs to service-tts, not this client.
  3. Surface reliability on a flapping cellular hotspot is mitigated (download-then-play, buffering, 3x auto-retry incl. early-partials, offline grace) but a device that stays offline past the 10-min buffer window will still drop clips — by design, with clip_gave_up logged.

RESOLVED THIS WEEK (see dev skill for detail): double-play/flipping (single-owner lock + version supersede), env-poisoned drainers (env self-heal), confirm-vs-retry race, early-partial auto-retry, all-time log counters misreading as current failures (24h window + rotation).

HOW TO REPORT: include adom-tts logs tail + the clip's check output + your adom-tts --version. The dev skill's debugging playbook maps most symptoms to causes.

0 Replies

Log in to reply.