Hi, I rarely use set up mode and when I do I have (so far) always got it completely wrong, got in a mess and I’ve had to ask for subsequent help. 
So now upfront I ask a trivial question - and I’m hoping the answer will be yes
If I want to remove a player from all layouts for one particular flow is there where I do it?
Incidentally I have read the entire PDF manual section. I’ve
read it several times now. I’ve also read
Help needed to understand the Flow-Layout-Player connection [SOLVED]
What is missing from your public documentation is a data model diagram (Graphic Picture) which would show what concepts relate to other concepts and how they own each other.
Other areas where I remain utterly confused after much usage is
-
PageTemplates and PageTemplateSets. I still don’t know who owns what or hence the scope for any particular object I might change. In fact I’m always afraid 
to change anything in case the whole thing goes pear shaped.
-
Some of the engraving behaviour. Again I live in fear and often have to cancel out without saving.
I would suggest thinking of Flows and Players as “Music data”, and Layouts as “visual representations of that data”.
If a Player isn’t in the Flow, then select the Flow and uncheck the Player.
You can remove a Player (or a Flow) from a Layout, but the data still exists - it’s just not being used in that Layout.
If you remove a Player from a Flow, then it’s gone. There is no Player data for that flow.
-
A Page Template Set consists of the “First” and “Default” templates (and any others that you may have created, like a Title Page). You can import and export sets.
By default, there’s a set for Part Layouts, and a set for Score Layouts. Each set has its own First and Default template.
-
You’ll have to explain exactly which behaviour, but essentially, you start with Engraving Options, which apply to the whole document, and then you make specific changes to individual items in the Properties panel, either Globally (affecting all layouts), or Locally (affecting only one).
Dorico is all about setting things globally, and then changing the exceptions as required, thus doing the minimum of work.
4 Likes
thank you. Your words are very clear.
Now I can make the change I need without messing up my project.
However, data model pictures would really help in the PDF. 
“One picture is worth a thousand words” 
I was trying to think whether I could create one, but the relationships are rather tangled.
A Player can be “in” a Flow, or not; and “in” a Layout, or not. A Flow can also be in a Layout, or not. But as said, Layouts are visual representations of the data, rather than data themselves.
In that way, you can have a Vocal Score Layout that excludes the instruments, but contains a Piano Player (e.g. a reduction) – but you wouldn’t want the piano reduction in the Full Score , so you would exclude that Player from the Full Score layout.
Also, in Messiah, the Trumpet Player would be in the flow The Trumpet Shall Sound; but wouldn’t be in the flow How Beautiful Are the Feet. The Trumpet part layout would show “Tacet” for every flow that the Trumpet isn’t in.
And this is why you can have different properties in different layouts – transpositions, enharmonic spellings, showing/hiding accidentals, text, etc – because the properties can be local to the layout; but the underlying data is the same.
Indeed. 
But compared what will be stored in Dorico elsewhere it is simplicity itself. The kind of picture I had in mind could start something like this:
The Dorico team will already own this kind of information - I am just asking that they expose a bit as “user understandable” pictures.
In an ideal world you can add little screenshots of the GUI so that you can see what you’re manipulating.
I am very impressed by Dorico generally - and my experience is that very good products like Dorico have very good data models underneath. Whoever first thought of storing the ‘notestream’ irrespective of bars/measures is a genius. For a composer it is the ultimate gift.
I’m not sure that captures it, either…
1 Like
