In this article, we will explain our policy for assigning product versions.
Unified Version
NovoNotes adopts a unified versioning system where multiple products share the same version number. For example, if Duo and SideRack are released simultaneously, they will be assigned the same version number. When using multiple products together, we recommend using products with similar version numbers as much as possible to avoid compatibility issues. If you encounter compatibility problems, first ensure that the major version is the same or the latest.
Version Format
Additionally, at NovoNotes, we represent versions in the format of Major.Minor.Patch. For example, in the case of v2.1.3, it means Major version 2, Minor version 1, and Patch version 3.
Meaning of Each Element
Major Version: Incremented when there are incompatible, breaking changes. Updates may sometimes require a paid upgrade.
Minor Version: Incremented when new features are added while maintaining backward compatibility.
Patch Version: Incremented for bug fixes that maintain backward compatibility.
Changes Included in Updates
Updates may include the following types of changes:
| Project File Compatibility | Compatibility Between Products | Output Sound | User Interface | |
|---|---|---|---|---|
| Major Version | Project files created with older versions may not open, but a project file conversion feature will be provided as a countermeasure. | May include breaking changes that are not compatible with other products. We recommend checking if the other products you plan to use in combination are compatible with the new version and updating them simultaneously. | May include changes that are noticeable to the ear. | Major changes or removals may be made to the existing UI. |
| Minor Version | Project files created with older versions can be opened as is. | Does not include changes that break compatibility with other products. | While the output may not be exactly the same, the changes will sound the same to the ear. | May include new features. |
| Patch Version | Project files created with older versions can be opened as is. | Does not include changes that break compatibility with other products. | No changes | May include fixes that do not affect usability. |
Project File Compatibility
- Major Version Updates
- Includes new features
- v2 can open v1 project files
- Conversion may be required. In such cases, users will be asked for permission to proceed with the conversion.
- The conversion process will be applied after making a copy of the project file. The original project file can still be opened with v1.
- However, project files from unsupported versions may not be accessible.
- v1 cannot open v2 project files
- Minor Version Updates
- Includes new features
- v1.1 can open v1.0 project files and reproduce almost the same sound.
- However, exact sample-level sound reproduction is not guaranteed as there may be audio engine improvements.
- v1.0 can open v1.1 project files and reproduce almost the same sound.
- However, parts using new features may be replaced with silence or cause errors and warnings.
- Patch Version Updates
- No new features, only bug fixes.
- v1.0.1 can open v1.0.0 project files and reproduce exactly the same sound.
- However, noise and other sound issues may be resolved due to bug fixes.
- v1.0.0 can open v1.0.1 project files and reproduce exactly the same sound.
- However, issues may arise due to unresolved bugs in v1.0.0.