How to reset master pages to factory default?

What is the quickest way to reset master pages to factory defaults?

thank you!

Open Library Manager, select ā€œCompare to: Factory Settingsā€ then under Collections apply Page Template Sets.

3 Likes

Thanks!

1 Like

Hey Todd,
When you look in the Library and compare the custom Expression Maps in an open project with the ā€˜User Library’, do you know what Dorico is comparing them to? I keep my Expression Maps in the DefaultLibraryAdditions folder, but this does not seem to be where Dorico references my User Library Expression Maps. Where are the User Expression Maps kept, and how do they get there? Thought you might know…

I’m not entirely sure. Any maps that are referenced in PlaybackTemplateSpecs I think are loaded automatically. I think these reference the maps contained in the EndpointConfigs folder, but I’m not 100% sure about that. It seems like the maps contained in each of the playbacktemplatedeps.doricolib files in each of the subfolders are loaded with any New file. It’s not entirely clear to me the relationship or hierarchy between the DefaultLibraryAdditions folder and the EndpointConfigs folder though.

When I go to Library Manager and compare to User Library with a file created from File/New, all the maps in my custom Playback Templates are loaded on the left side, but only Default shows on the right. Clearly the Library Manager isn’t looking at the same place that File/New looks when it creates the project. Maybe the Library Manager is just looking at the userlibrary.xml file which doesn’t contain anything under expressionMapDefinitions?

Thanks, it is a little confusing. If I create a new project, the Expression Maps from my DefaultLibraryAdditions folder appear in my Expression Maps list, but they don’t appear in the Library list of Expression Maps. It may be that if you have a score with a bunch of expression maps, they get saved with the project file and then those EM’s become USER EM’s when you compare it with another project. I do not save endpoint configurations because I don’t use templates so my EM’s are not getting stored that way. My goal is to have the Library see the Expression Maps in my DefaultLibraryAdditions folder, because that’s where I keep the newest versions of each EM. Then I can update an old project to my my latest versions. At the moment I have to keep my newest versions in a template file and then compare to that. But it’s easy to forget to update the template file when you create a newer EM version and so you have to load manually via the EM dialogue. If I could keep all my latest EM’s in a place that the Library would see, it would be fine. Maybe I’m just keeping them in the wrong place, but at least in the DLA’s folder they always show up in a new project.

I really like the workflow you are proposing. It would be great to be able to update the EM, then update it in any file with a click. Unfortunately, I can’t figure out how to make that work.

If I manually graft the EM into expressionMapDefinitions in the userlibrary.xml file, then it works. Here’s what I now get in the Library Manager where dummytestmap is the one I grafted into the file:

Manually grafting or updating the userlibrary.xml file obviously isn’t as easy as just copying it into DefaultLibraryAdditions, but that might be the only way to get it to work in Library Manager.

I guess the feature request would be to allow EMs that are loaded via DefaultLibraryAdditions, EndpointConfigs, PlaybackTemplateSpecs, other methods to be visible in the Library Manager. This would support updates to any VSL, Spitfire, or other third-party EM updates too.

1 Like

Perfect! Thank you for condensing this into a feature request.