VPR Parser
Pydantic-based VOCALOID5 Editor Project (.vpr) file parser & unparser
For parsing and manipulating Yamaha VPR (Vocaloid 5 Project) files, this tool allows you to read, modify, and save VPR files programmatically using Pydantic models for type safety and validation.
Features
- Parsing: Extract structured data from
.vprfiles into Pydantic models. - Modifying: Update or manipulate the parsed data and save it back to a
.vprfile. - Well-typed: Uses Pydantic for robust data validation and serialization.
- Detailed performance logging: Includes a
Timerutility for profiling operations.
Installation
Install the package using pip:
pip install vpr-parser
Or install from source:
git clone https://github.com/0x24a/vpr-parser.git
cd vpr-parser
pip install .
Usage
Parsing a VPR File
from vpr_parser import VPRParser
parser = VPRParser()
vpr_file = parser.parse("path/to/your/project.vpr")
# Access parsed data
print(vpr_file.title) # Print the project title
print(vpr_file.tracks) # List all tracks
Modifying and Saving a VPR File
from vpr_parser import VPRParser, models
parser = VPRParser()
vpr_file = parser.parse("path/to/your/project.vpr")
# Modify the title
vpr_file.title = "New Project Title"
# Save the modified file
parser.dump(vpr_file, "path/to/modified_project.vpr")
Available Models
The following Pydantic models are provided for working with VPR data:
VPRFile: Root model representing the entire VPR file.Track: Represents a track in the project.Part: Represents a part (segment) within a track.Note: Represents a note.- And many, literally, MANY more (see
models.pyfor details).
Development
Dependencies
- Python 3.8+ (ONLY tested on Python 3.11+, but should work on other versions?)
- Pydantic
Running Tests
WIP, bcs it just works...?
Contributing
PRs are welcome! For major changes, please open an issue first to discuss the proposed changes.
License
This project is licensed under the MIT License. See the LICENSE file for details.
Metadata
Release files for vpr-parser 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| vpr_parser-0.1.0.tar.gz | 5.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vpr_parser-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.9 kB
Release files / vpr_parser-0.1.0.tar.gz
| Download URL | vpr_parser-0.1.0.tar.gz |
|---|---|
| Size | 5.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a38f893751fc4f4d6a66a70a1555293ec4cdb6dd064836cbbc6750b5212de3fc
|
|
BLAKE2b-256 checksum How to use checksums |
7d1b8ade646ce9deaa5b9c1d0b28b96fa29e071b4309815ad5626307fd3e8cba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.6
|
Release files / vpr_parser-0.1.0-py3-none-any.whl
| Download URL | vpr_parser-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f4875bfb3a0d95121443d7a5a745883a5c2cf40d8aeffe30fd68b49b3b35f7c
|
|
BLAKE2b-256 checksum How to use checksums |
c4310b13d5e4025311197f6896b4d60aadd24e8ec084b99fc9aef7bedddff0a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.6
|
Security for vpr-parser 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.