…from server_editor.py

The logic has not been changed, only renaming, splitting and moving modules on a per-function basis.
Existing code will be left in place for the time being to avoid breaking the training code, which is not subject to refactoring this time.

…OX to style_bert_vits2/text_processing/japanese/user_dict/

… definitions and comments

…s are imported

…subprocess.py

…tyle_bert_vits2/models/

The code has not yet been cleaned up, just moved.

… loaded BERT models/tokenizer and replace all from_pretrained() to load_model/load_tokenizer

…each language to style_bert_vits2/text_processing/(language)/bert_feature.py

… style_bert_vits2/text_processing/__init__.py

This was often used in 3 function sets and felt like a wasteful division with few lines.

…VITS2

Since app.py and server_editor.py already exist as alternative Web UI, there is no need to revive webui.py in the future.

…_alignment.py

…ns.py

I have determined that this is excessive for this project at this time.

"text_processing" is clearer, but the import statement is longer.
"nlp" is shorter and makes it clear that it is natural language processing.

pyopenjtalk_worker.initialize() has the side effect of starting another process and should not be executed automatically on import.

Configured so that the same public function is exported from the module with the same name for each language.

…ert-VITS2 model

HyperParameters is largely a drop-in replacement for utils.HParams, which ensures type safety for hyper-parameters.

…ker.worker_client

ref: litagin02#91

…t/port

I didn't add docstring because it is very technical code and I don't understand what is being implemented.

I didn't add docstring because it is very technical code and I don't understand what is being implemented.

Considering library design, this function with many side effects should not be executed in a library.

openjtalkプロセス間通信のタイムアウト延長

…ckpoints and safetensors

…ontinue processing without a worker

When using style-bert-vits2 as a library, the requirement to be able to launch it in multiple processes may not be necessary. Also, if the library is embedded and exe-ed using PyInstaller or similar, it is difficult to make pyopenjtalk_worker run in a separate process.
Therefore, we changed it so that the worker is used only when it is explicitly initialized.

… clarification and add comments to each method

By executing "hatch run test:test", you can check whether the test passes in all Python 3.9 to 3.12 environments.

Style-Bert-VITS2 has been reported to not work with some PyTorch 2.2 series, but Python 3.12 is only supported in Torch >= 2.2, so Python 3.12 support is not provided for the time being

Enabling type checking with Pylance.

BERT models and tokenizers are already stored and managed in the bert_models module and should not be stored here.
In addition, since there may be situations where the user would like to use cpu instead of mps for inference when using it as a library, the automatic switching process to mps was removed.

The Pydantic models in the library are written for Pydantic v2 and will not work with Pydantic v1.

Prebuilt wheels for almost every OS/architecture (except musl) are now available on PyPI, eliminating the need for a build environment.
ref: https://pypi.org/project/pyworld-prebuilt/

Pydantic models are more robust and properties can be accessed by dots.