I am new to Dorico, so maybe my questions are trivial. Anyway, I would appreciate any hints and answers.
I am member of a choir and orchestra, and our musical director produces the arrangements for all of us - in future using Dorico. He is responsible for the complete arrangements in Dorico, but it would be helpful for other people to change parts of the arrangements in a secure way, e.g., for a choir representative to correct wrong notes after a choir rehearsal.
Therefore, I have three questions:
Is it possible to restrict the access for individual users to certain parts of the arrangement?
Is it possible for different users to simultaneously work on the same arrangement - maybe only on different parts?
Is there a feature for making changes visible, e.g. showing new/changed notes in red until they are “accepted”? (comparable to the “change mode” in MS Word)
I am looking forward to answers or hints, how to handle these scenarios?
sadly none of your questions are possible. These would be nice collaboration features of course.
The way I solved it in the past was to use either a common cloud service with my partners and informed them, whenever I was working on a file, or creating a local copy and having someone assigned to be in charge of “version control”, who would receive all the changed files, with maybe a manually written change log.
If two computers have the same project file open, you will get alerts saying “this project has been modified on disk, do you want to load the new version, overwrite it with what you’re doing instead; or Cancel.”
You might look into using Dorico’s comments feature.
Another alternative option would be to create a private repository in GitHub and upload the scores there (which is convenient for sharing the latest version anyway.)
Set the permissions in GitHub so that certain others are permitted to upload a new version, but do not give them rights to “merge” their changes into the main (we tend to use “main” rather than “master” these days. ) The musical director would get notified of the change and have the ability to review and accept the changes (or not).
GitHub is not great at letting you review a binary file in too much detail. But if your habit was to always upload both Dorico and musicXML versions of the score, then the musically director WOULD be able to review the changes in red (basically). A con is that they’d have to understand musicXML a little more. A pro is that you could decide to divide and conquer on the work more.
Hello everybody,
many thanks for all your answers!
As I already assumed, there seems to be no perfect solution. But you gave me some interesting hints to at least deal with this challenge.
I think we will try and work with GitHub and always store both the Dorico and musicXML file as gdball suggested.
