What problem(s) would this feature resolve?
Manually managing project versions by renaming files is time-consuming and error-prone. It increases the risk of overwriting important work or creating inconsistent version names. A built-in “Save New Version” (like in Cubase) feature would streamline the workflow and improve project organization, especially during iterative production stages.
How does this feature fit in Bitwig as a product?
Bitwig is known for its flexible and modern workflow. Adding a versioning feature would align with Bitwig’s focus on non-destructive editing and creative exploration, making it easier for users to experiment freely while preserving previous versions of their work.
Is there already an alternative way to achieve this on Bitwig?
The only current method is manually using “Save As…” and entering a new filename with a version suffix. This works but lacks automation and is prone to human error (e.g., forgetting which version you’re on).
Could it be implemented using Bitwig components or APIs, without Bitwig team’s support?
Not sure about that. Bitwig’s scripting API focuses on controller integration and doesn’t expose file or project-level operations. Therefore, this feature likely requires support from the Bitwig development team.
Could it be provided by a VST or something else reasonably integrated with Bitwig?
No, VSTs do not have access to Bitwig’s project file system or saving logic. This kind of feature must be part of Bitwig’s core functionality.
Are there other products that offer this feature?
Yes.
Cubase has a built-in “Save New Version” option that automatically creates a new project file with an incremented version number. This makes version control seamless and efficient.