fix: requirements.txt

[JarbasAl]

allow latest coqui-tts

Summary by CodeRabbit

• New Features

  • Added support for a new voice option, defaulting to "celtia".
  • Introduced a method to retrieve available languages, now supporting "gl-es".

• Bug Fixes

  • Enhanced text processing for currency and temperature formats to improve synthesized speech quality.

• Chores

  • Updated version constraint for the coqui-tts package to require version 0.25.1 or higher.

[coderabbitai]

Walkthrough

The pull request introduces several enhancements to the NosTTSPlugin class in the ovos_tts_plugin_nos/__init__.py file, including modifications to the constructor, methods for downloading models, phonemization, and text-to-speech processing. It also updates the get_engine method to clarify parameter usage. Additionally, the requirements.txt file is modified to specify a minimum version for the coqui-tts package, ensuring compatibility with the new features.

Changes

File	Change Summary
ovos_tts_plugin_nos/init.py	- Updated NosTTSPlugin constructor to initialize CotoviaTTSPlugin and set default voice. - Enhanced download method for TTS model files. - Improved phonemize method for text formatting. - Updated get_tts for better text preprocessing. - Added available_languages method to return supported languages. - Modified get_engine method to use named arguments for clarity.
requirements.txt	- Updated coqui-tts version constraint to >=0.25.1.

Possibly related PRs

• fix: handle changed urls #3: The changes in the get_engine method in both PRs involve updates to the method signature and logic related to the config_path, indicating a direct connection in the handling of the NosTTSPlugin class.
• feat: text normalization #5: Modifications to the phonemize and get_tts methods in both PRs show a focus on text processing improvements, highlighting a shared objective in enhancing the functionality of the NosTTSPlugin class.

Suggested labels

fix

Suggested reviewers

• goldyfruit

Poem

In the code where rabbits play,
A TTS tune found its way.
With voices bright and models clear,
We hop along, no need to fear.
From celtia sweet to gl-es cheer,
Our plugin sings, for all to hear! 🐇🎶

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between f311440 and 690d4ca.

📒 Files selected for processing (2)

• ovos_tts_plugin_nos/__init__.py (1 hunks)
• requirements.txt (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• requirements.txt

🔇 Additional comments (2)

ovos_tts_plugin_nos/__init__.py (2)

Line range hint 1-144: Verify requirements.txt changes mentioned in PR objectives.

The PR objectives mention updating requirements.txt to allow for the latest version of coqui-tts, but this file isn't included in the review. This change is important as it affects the Synthesizer usage in this file.

Let's verify the requirements file:

✅ Verification successful

Requirements.txt correctly specifies coqui-tts>=0.25.1

The requirements.txt file has been updated to allow for the latest version of coqui-tts (>=0.25.1), which aligns with the PR objectives and supports the Synthesizer usage in the code.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check requirements.txt for coqui-tts version
# Expected: Find the updated version requirement

# Look for requirements.txt
fd -t f "requirements.txt"

# If found, check its content
if [ -f "requirements.txt" ]; then
    echo "Content of requirements.txt:"
    cat requirements.txt | grep -i "coqui-tts"
fi

Length of output: 201

---

133-133: LGTM! Improved code clarity with named parameters.

The change from positional to named parameters (tts_checkpoint, tts_config_path) in the Synthesizer instantiation improves code readability and maintainability.

Let's verify the parameter names match the Synthesizer's expected arguments:

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.