I have a Dorico file that always opens in Dirty mode. If I close the file without making any changes, I am prompted to save changes. I know this is minor, but annoying. Has anyone else encountered this issue?
Thank you.
I have a Dorico file that always opens in Dirty mode. If I close the file without making any changes, I am prompted to save changes. I know this is minor, but annoying. Has anyone else encountered this issue?
Thank you.
Ok I’ll bite, what does this mean?
If the problem occurs on one specific file, as always on the forum, please post that file or a cut down version of it, and someone will probably be able to help.
And does it happen again if you then in fact save, close and re-open the file?
One thing I can think of is that the file comes from an older Dorico version, opening it in a later version then constitutes a change to the file.
It means that Dorico thinks the file has been modified.
dirtySample.dorico (3.1 MB)
Here is the stripped down file. It always opens in Dirty mode.
I’m using the latest version of Dorico Pro6.
I can reproduce this with that file.
It opens without warning about a previous version. Even “saving as…” does not change this behaviour.
(Windows)
Is it possible that the file in question is read-only?
After trying various resets and deletions, I have discovered that after deleting all notation in the first 6 bars of the upper staff and then saving the file, it will open not “dirty”.
Also, in those first 6 bars in the upper staff, if all notes which are not marked staccato are selected and staccato applied to them, then the file saved and closed, it will re-open not “dirty”.
I see the same. Opens dirty. Removing first 6 bar note in right hand solves issue. On Mac. Think this is something for the developers.
I have taken one more look on this. To me it seems like there are some very odd malformed midi cc6, cc98 and cc99 messages. I cannot make them go away. These might be the problem, but it really does not make sense
Temporary solution:
Dorico has various “fix-up” steps that may run when opening a project, if they are needed to clean up things that are in an odd state. It sounds like that’s what’s happening here.
Thanks to SJ and G for discovering the offending six bars. Solution: Went into original file and deleted the six bars and re-recorded them. Now the file opens clean.