You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -75,47 +83,50 @@ The following steps are tested on an Ubuntu system.
75
83
76
84
7. Add your tests to our test suite under ```tests``` folder. It is important to show that your code works, edge cases are considered, and inform others about the intended use.
77
85
78
-
8. Run the tests to see how your updates work with the rest of the project. You can repeat this step multiple times as you implement your changes to make sure you are on the right direction.
86
+
8. Run the tests to see how your updates work with the rest of the project. You
87
+
can repeat this step multiple times as you implement your changes to make
88
+
sure you are on the right direction. **NB: running all tests takes a long time,
89
+
it is better to leave this to the CI.**
79
90
80
91
```bash
81
-
$ make test# stop at the first error
82
-
$ make test_all # run all the tests, report all the errors
92
+
uv run make test# stop at the first error
93
+
uv run make test_all # run all the tests, report all the errors
83
94
```
84
95
85
96
9. Format your code. We use ```black```for code formatting.
86
97
87
98
```bash
88
-
$ make style
99
+
make style
89
100
```
90
101
91
102
10. Run the linter and correct the issues raised. We use ```ruff```for linting. It helps to enforce a coding standard, offers simple refactoring suggestions.
92
103
93
104
```bash
94
-
$ make lint
105
+
make lint
95
106
```
96
107
97
108
11. When things are good, add new files and commit your changes.
98
109
99
110
```bash
100
-
$ git add my_file1.py my_file2.py ...
101
-
$ git commit
111
+
git add my_file1.py my_file2.py ...
112
+
git commit
102
113
```
103
114
104
115
It's a good practice to regularly sync your local copy of the project with the upstream code to keep up with the recent updates.
Copy file name to clipboardexpand all lines: README.md
+9-19
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,13 @@
1
1
2
2
## 🐸Coqui TTS News
3
3
- 📣 Fork of the [original, unmaintained repository](https://github.com/coqui-ai/TTS). New PyPI package: [coqui-tts](https://pypi.org/project/coqui-tts)
4
+
- 📣 Prebuilt wheels are now also published for Mac and Windows (in addition to Linux as before) for easier installation across platforms.
4
5
- 📣 ⓍTTSv2 is here with 16 languages and better performance across the board.
5
6
- 📣 ⓍTTS fine-tuning code is out. Check the [example recipes](https://github.com/idiap/coqui-ai-TTS/tree/dev/recipes/ljspeech).
6
7
- 📣 ⓍTTS can now stream with <200ms latency.
7
8
- 📣 ⓍTTS, our production TTS model that can speak 13 languages, is released [Blog Post](https://coqui.ai/blog/tts/open_xtts), [Demo](https://huggingface.co/spaces/coqui/xtts), [Docs](https://coqui-tts.readthedocs.io/en/latest/models/xtts.html)
8
9
- 📣 [🐶Bark](https://github.com/suno-ai/bark) is now available for inference with unconstrained voice cloning. [Docs](https://coqui-tts.readthedocs.io/en/latest/models/bark.html)
9
10
- 📣 You can use [~1100 Fairseq models](https://github.com/facebookresearch/fairseq/tree/main/examples/mms) with 🐸TTS.
10
-
- 📣 🐸TTS now supports 🐢Tortoise with faster inference. [Docs](https://coqui-tts.readthedocs.io/en/latest/models/tortoise.html)
Please use our dedicated channels for questions and discussion. Help is much more valuable if it's shared publicly so that more people can benefit from it.
0 commit comments