Okay, weird one here. I started a brand new project in Dorico 6, and I imported a .doricolib file I used without issue in Dorico 5. I then synced up the settings (blanket for now as this is a test, but I’ll be more judicious once I have a minute to look over the changes in defaults) and it doesn’t seem like the settings match at all compared to what they looked like in 5. Instead of a normal looking part on Concert-sized paper with rastral size 4, I get some sort of eldritch horror: tabloid-sized paper with tiny staves, formatted like it’s a one-part score instead of a part.
Now, I know better, but if I didn’t, I’d say that Dorico can no longer tell the difference between a score and a part. Have a sample (and don’t mind the mess, trust me it’s not going to stay like this):
If anyone has any clue how to deal with this without painstakingly going through a Dorico 5 project and screenshotting all the settings before manually putting them in Dorico 6, I’m all ears.
Appears so. I’ll have to figure out how that works. I was able to get it going for this test sheet just fine at least. I knew they had changed this but the ramifications of the change weren’t obvious to me. Thanks!
We’re happy to investigate this, but it’s not something we’ve encountered in our testing, nor had any other reports of, so it would be helpful if you could provide us with a step-by-step procedure to reproduce the problem, and to include both the destination project and the source project or library file as well.
OK, I’ll give it a shot. The project is just a visual uncluttering of the violin 1 part from Moldau because some of the folks in my orchestra were having trouble with how cramped the edition was that we got.
By default, the parts were set up on letter paper. I use concert size paper in my projects, though, so I went Library → Library Manager… and I realized, “Oh, that’s strange, the button underneath the ‘Compare to:’ text isn’t there anymore,” so I clicked the Dorico project tab which immediately opened a file navigation dialog, navigated to the folders where my .doricolib file is located, and double clicked the library file. The button that used to be there all the time before now shows up, showing that I’ve selected the intended .doricolib file.
In Dorico 5, all I would need to do at this point to make everything match the library file is to click the red inequality symbols next to Options and Collections, then Apply and Close. That, however, absolutely does not work here, instead giving me a result much like what’s in the image in my original post.
People here have talked about applying to scores or specific layouts, but that option does not seem to exist here unless I’m missing something obvious, which, frankly, I probably am:
That said, I’m uploading both the project file itself and my library file, which–another minor issue–cannot be uploaded directly to the forum because it will not accept .doricolib attachments.
Justin, I’ve had a quick look. I think the problem might be that you’ve got used to some bugs in the Library Manager in v5 - it used to be that Dorico would sometimes ignore the value of the “Layout” selectors, and by chance this might have given you the answer you want in this case. However, what you really need to do here is to select “Layout Options” in the top left of the Library Manager dialog, and then ensure that you’ve set the Layout type appropriately in the “This project” and “Compare to” sections. For example, here I’ve chosen to import from the “Part” layout type in your saved file into the “Guitar” layout of my project.
If you don’t do this, Dorico will import from the “Full Score” layout in the compared-to file - in this case that’s Tabloid rather than Concert. (When you have “Layout Options” selected there will also be a button at the bottom left of the dialog that says e.g. “Copy to All Part Layouts” - that might also be useful.)
I’ve finally got to a point in another project where I can try this out and it is definitely not behaving how I’d expect. I open the project, go to Library Manager, and pull in the .doricolib file under the “Compare to” section. I make everything match on the left, so all is either a blue check mark or a green arrow, then hit Apply so it sticks. I then specifically go to Layout Options on the left and I’m presented with this:
So far so good, it seems. Great. Now I switch to "Part"under the “Compare to” layout and “Piccolo” under the “This project” layout, make the layout options match, hit Apply. All looks good. I then click the “Copy to All Part Layouts” and then “OK” on the “Do you want to proceed” dialog. Suddenly, the layout is broken again:
And that’s the layout I just finished setting. What is it copying from? That page size shown there of 8.25" x 11.7" isn’t in any of my settings anywhere as far as I can tell; it’s just fabricating it out of whole cloth. I’m seriously stuck on this and all I want to do is finish a couple of projects so I can get them released. I could make all the setting changes manually as I said before, but why should I go through that trouble when I have this that’s supposed to do it all for me?
I can reproduce this same behaviour when using your doricolib and repeating the same steps. I’ve never used the “Copy to All Part Layouts” option before this, so perhaps I am doing something wrong.
FYI - I noticed that that page size does match your “Custom” layout in the Doricolib file. In fact almost all the options do, when using “Copy to All Part Layouts”. So it is almost like it is copying the “Custom” layout from the doricolib to the parts instead of the Part layout.
Hi Justin. Many apologies, it does look like there’s a bug here when using the “Copy to All …” functionality with a doricolib file, rather than a project file. For the time being, I think the easiest way to work around this is to import the Part layout into a single layout - as you did with the Piccolo in your example - then save a temporary copy of your Dorico project with the correct Piccolo layout, and then import the layout settings from there instead of importing them from the doricolib file.
I’ll log the bug for one of our developers to look at.
