Skip to content

[Linux v1][Q04] Validate TTS, STT and full voice conversations #2148

Description

@w4ffl35

Parent/specification: #2083

Repository: Capsize-Games/airunner. Work type: Operator acceptance; a small-model session prepares scenarios, not fabricated results.

Outcome

Exercise every supported TTS/STT backend, voice selection/cloning with authorized neutral samples, microphone permissions, device switching, interruption and STT-to-chat-to-TTS ordering. This is an operator/manual acceptance issue. An ordinary small-model agent prepares the script/results template only; real GUI/model work requires the operator to run it.

Prerequisites

Read/change boundary

  • release-planning/linux-v1/feature-matrix.md
  • release-planning/linux-v1/acceptance/ (new)

Paths marked new are deliverables. The companion/ module is introduced by B01; release evidence files may be introduced by prerequisite issues. Directory entries identify a subsystem, not permission to refactor it. Normally limit implementation to five production files plus directly relevant tests; if more is needed, return a proposed split with exact files and do not omit requirements.

Acceptance

  • Record candidate digest, hardware/driver/model revisions and exact scenario IDs/results.
  • Untested/skipped/failed is not pass; file one-behavior defects with sanitized evidence.
  • Cover all R01 entries in this family and link any missing capability work before closing.

Validation

Deliver the named document/results artifact with a checklist, source references, reviewer/operator fields and explicit pending results. No new app tests needed just to mirror prose. The issue remains open until its specified acceptance evidence/review exists. Never claim manual, legal or safety efficacy checks passed from static analysis.

Guardrails / handoff

Linux + NVIDIA 16 GB minimum; retain Qt and offline core; no Electron/Windows work. Preserve existing features and user data. Do not co-install the two airunner_services implementations. No private policy vocabulary, credentials, customer content or sensitive test imagery in source, issues or logs. No GUI/model launch, paid API call, live DB change or deployment in an ordinary coding session. Read applicable repository instructions; preserve unrelated edits. One issue per session; no subagents, automatic follow-on issues or model escalation. Return behavior change, files, exact checks/results and unresolved facts. Do not close until required review/acceptance is complete.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    linux-v1Linux NVIDIA offline Desktop release handoff

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions