Best Practice for working archiving versions in using flows?

Dorico
1

Hi,

Just finished my first project in Dorico having worked with Finale forever. I’ve very much enjoyed learning the software and finding solutions to pretty much any issue I had by using the help pages and the forums.

I wanted to raise a discussion about how best to work with versions of songs or cues using the flow system. In finale if I made big enough edits to a song or cue I would save a new version of the file and add v2 to the end of the file name.

For this first project on Dorico, I applied the same process by duplicating the flow and then moving the old version to the end of the flows list. The problem I think is that you could end up with so many flows to a project as you get to versions 7,8,9 of a flow within a project that may have 40 cues - all with multiple versions. I did notice the project start to slow its operation speed as the flows built up.

Has anyone found a cool way to archive previous versions whilst still working with the flow system?

It would be amazing if Dorico had an archive function where you could select a version from a dropdown from the flow screen so it only ever displays the version you want whilst keeping an archive of versions that you can call up if you need.

Thanks! Matt

2

I archive each file rather than adding flows for that purpose. Each day I append a date-stamp to the file name (filename250101.dorico) and may add letters onto the end of the date-stamp (filename250101a.dorico) if I decide to try something particularly daring on a file already date-stamped.

3

There are is a “Save Version” command – which annoyingly isn’t in the File menu, but is in the list of commands that you can apply a key shortcut to in Preferences.

IIRC, this will append an incremental number to the filename.

3 Likes