I find browsing Bitwig projects to be cumbersome with the current folder structure of projects. You have to go into a folder, and then you have to figure out what the latest version was, and then click that version to open the project.
I’d like to have the option to store projects in a package similar to the option that Logic Pro has.
A package would just be a single self contained file that includes all of the different versions of the song you’ve worked on. It’d also include all the samples, presets, bounces, recordings, and any other necessary data for the project.
When you clicked to open the package in Bitwig, it’d load the latest version of the song and pull any data from the package.
If you wanted to open a different version of the song you could browse the package manually by right clicking on the song/package and selecting show package contents in Mac OS. Bitwig’s dashboard could offer the ability to right click on a package and it’d show the different versions of the song that you could click to load that specific instance. You could also rename versions in the Finder if you want for further clarity, or there could be an option to name the version upon saving as Studio One does.
It would be very similar to the current structure except that now everything would be self contained in a single file that’d save you time when browsing your music and provide cleanliness in your track folder structure.
It would make it quicker and cleaner to go through songs you’ve been working on. Most of the time I want the latest version of the song I was working on. Rarely do I need any other versions. However, there are cases where I’d like to see different versions or variations of the song and I want to go through and audition the different changes. In those cases I could just browse the package through the Finder, or there could be a right click option when browsing recent projects on the Bitwig dashboard that opened a sub list of versions which is how Studio One’s start page functions.
This also makes sharing a song with others to work on, easier. You just send them the single package file and they have a full history of the changes you’ve made along with all the samples and everything they’d need to work on the song.
It would also allow Bitwig to offer a new option to save new version instead of just save as where you create a new file or folder structure using the Finder. Instead you’d just click save new version, and it would either increment the current version with a number of the current version you’re on, or have a simple single input dialog box where you name the version. It would save the version into the package. The latest version would be loaded when opening the package directly, but you’d have the option to browse past versions by going through the package contents or right clicking in the Bitwig dashboard.
The only question I have is if Windows or Linux operating systems have a similar file concept as a Mac OS package or if that would even be necessary.
I don’t believe so.
Studio One (S1 has a similar same setup, but it still saves everything into a project folder. The start page puts all versions into a single file and you right click on the file to see different versions.)