After some sleep and further analysis I found the following:
- Upon your question regarding signposts @pianoleo, I checked and they were all active (except the two accidentals) and so signposts whatsoever were visible . That triggered some further thoughts, but apparently there was no information available in the xml file that triggered any signposts.
So the conclusion here is that there were no time signature data available in file.
- After some reading up on musicxml it came to mind that it might be worth adding time signature attributes to the xml file, which I did. I added the time attribute to the attributes section first bar in the raw xml file. I found it needs to be located right after key and not e.g. after clef attribute, otherwise the Dorico parser generates an error.
Now, that solved the “can not add bars” issue. After adding the above and importing to Dorico I can now add bars at any position in the flow. That part of the problem solved.
- However, I also had another problem with some bars that clearly was not translated correctly when outputting the original xml file. I identified that when having a 4/4 bar beat and the measure x in xml definition does not have the correct number of note and rest values to equal the 4/4, we turn into another set of problem.
a. In the image below we see three bars (33-35). Bar 34 is missing a half rest
(and the signpost only showed in bar 34 in source versions where I had added time signature in xml file manually)
b. I have still not found a way in Dorico to amend bar 34 with the much needed half rest.
c. After adding a note/rest value in xml file, that problem was also solved. I tried to renew the time signature for that bar also but that did not help.
Conclusion: It seems that some of the general Dorico rules does not apply when importing xml. As I envisioned the way it would work was that you enter data to the system (manually or via xml) and then the system rules apply on the data entered. In that case, in the example above, bar 34 would have been filled with notes from bar 35, but that did not happen.
There may of cause be other use cases where you want to maintain the xml import, but there seem to be areas here that perhaps would need some further consideration.
I can not get my head around that the “fill the bars” rule does not apply when (a somewhat erroneous) xml file is imported to Dorico and that the validity of entering a time signature in Dorico does not apply through-out the flow (at least to the next change of time signature as @pianoleo pointed out). In conclusion there seems to be ruling conflicts in this area that needs to be sorted out.