Skip to content

Clarify using the latest voices with Wyoming Piper - #4601

Open
AlexGustafsson wants to merge 1 commit into
home-assistant:masterfrom
AlexGustafsson:fix-piper-docs
Open

Clarify using the latest voices with Wyoming Piper#4601
AlexGustafsson wants to merge 1 commit into
home-assistant:masterfrom
AlexGustafsson:fix-piper-docs

Conversation

@AlexGustafsson

@AlexGustafsson AlexGustafsson commented May 1, 2026

Copy link
Copy Markdown

The Wyoming Piper code fetches from the main Huggingface "branch", not
v1.0.0. Though in order to use newly available voices, one might need to
update the voices list - clarify this in the docs.

SEE: OHF-Voice/wyoming-piper#49

Summary by CodeRabbit

  • Documentation
    • Updated voice model setup guidance to reference the latest available voices from the rolling main branch.
    • Added note about using the update_voices option to fetch the most recent voice models.

The Wyoming Piper code fetches from the main Huggingface "branch", not
v1.0.0. Though in order to use newly available voices, one might need to
update the voices list - clarify this in the docs.

SEE: OHF-Voice/wyoming-piper#49
@coderabbitai

coderabbitai Bot commented May 1, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

Documentation update changes the Hugging Face Piper voice model download source from a pinned version (v1.0.0) to the rolling main branch, and adds guidance for users to utilize the update_voices option to fetch latest voices.

Changes

Cohort / File(s) Summary
Documentation
piper/DOCS.md
Updated Hugging Face model source URL from fixed version (v1.0.0) to main branch; added note about using update_voices option for latest voice models.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Clarify using the latest voices with Wyoming Piper' directly and clearly summarizes the main change: updating documentation to clarify that Wyoming Piper fetches from the main Hugging Face branch to use latest voices.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@piper/DOCS.md`:
- Line 31: Rewrite the sentence in DOCS.md to use a direct, authoritative tone
by removing "may" and fronting the instruction; change "To use the latest
voices, you may need to use the `update_voices` option." to a direct imperative
such as "Use the `update_voices` option to get the latest voices." Ensure the
reference to the `update_voices` option remains exact.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1ab273e7-441c-40cd-be9c-8e6086cfdf8d

📥 Commits

Reviewing files that changed from the base of the PR and between ad8a4b3 and af123f4.

📒 Files selected for processing (1)
  • piper/DOCS.md

Comment thread piper/DOCS.md
Name of the Piper voice to use, such as `en_US-lessac-medium` (the default).
Voice models are automatically downloaded from https://huggingface.co/rhasspy/piper-voices/tree/v1.0.0
Voice models are automatically downloaded from <https://huggingface.co/rhasspy/piper-voices/tree/main>.
To use the latest voices, you may need to use the `update_voices` option.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use direct, authoritative tone instead of "may".

The sentence uses "may" which should be avoided. Rewrite to be more direct and authoritative.

📝 Proposed fix
-To use the latest voices, you may need to use the `update_voices` option.
+To use the latest voices, enable the **update_voices** option.

As per coding guidelines: "For instructional content in documentation, use a direct and authoritative tone. Avoid expressions of politeness such as 'may' or 'please', and ensure the goal of the instruction is fronted."

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
To use the latest voices, you may need to use the `update_voices` option.
To use the latest voices, enable the **update_voices** option.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@piper/DOCS.md` at line 31, Rewrite the sentence in DOCS.md to use a direct,
authoritative tone by removing "may" and fronting the instruction; change "To
use the latest voices, you may need to use the `update_voices` option." to a
direct imperative such as "Use the `update_voices` option to get the latest
voices." Ensure the reference to the `update_voices` option remains exact.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant