Missing system track bar numbers (entire flow) (solved)

I had an issue with a particular flow wherein all the system track display bar numbers that are controllable via the view menu disappeared - vanished. This included the entire flow. (The printed bar numbers in write and engrave modes were ok though..)

I am not not sure how it got that way because this is in a project from about a year ago that had been set aside.

I went through all the forum suggestions here about making sure that it had a master time signature (it did - with no overridden staves either) and so on - no dice. Also tried some of Google AI’s suggestions - no luck there either.

The final solution was to create a new flow from scratch, assign existing instruments to it to mirror the problem flow and then select all from the problem flow and paste in the new one. That’s the trick.

Just wanted to toss this out there incase someone else winds up here.:blush:

Did I understand correctly, your System Track disappeared? Or did the appearance of the System Track change?
Did you really check view option for it?
This is related to Dorico version 6.1, if you are using an earlier version it would be good to know.

I don’t think it was that as those option are globals, and this issue was constricted to just one flow. I’m going to try a few other things and I’ll report back.

Yes - the missing bar number were constrained to a single flow in a document containing multiple flows.

The copy/paste wasn’t as successful as I’d like as it borked a few divisi passages. That’s not too hard to correct, but just now I did find an old version of the project and exported the flow in question and re-imported it into the newer project.

Gene, it is still not 100% clear, what exactly went missing in the first place. You quote:

Did the system track disappear as a whole?
Did those immanent numbers disappear?:

Or did the grey bar numbers in Galley View disappear?:

Yes - the grey bar numbers in the system track as well as on the pages, the galley view , and the fill view.

The ‘white’ system track was definitely visible - just no grey bar numbers displayed within it. As I mentioned before, what struck me as really odd was that this was the third flow of a four flow project. Flows one, two, and four were just fine with the grey bar numbers working as expected.

It had the hallmarks of some internal program variable getting set to a mismatched state. How that happened is anyone’s guess. Not a really a show stopper, just a glitch.

@SuperG, do you happen to still have the original project?

Thank you for your answer.
That’s a very rare sighting, so far I have never heard of this.
To further investigate:

Where in the view menu can you control the visibility of the bar numbers in the system track?
I have not seen that either yet.
Assuming you are on version 6 there are view options for the system track itself.

Hi @SuperG, this happened sometimes in the past in connection with local Time Signatures (especially with open time and in the top staff but it may vary). Or the TS is somehow corrupted: mostly reapplying it solves the problem (as the bar lines and bar number are generated by the TS)

If you could upload the project we can have a look.

See also this post (in case you have a similar situation):

1 Like

Yep. It’s quite large though. I will post a weblink to it in the morning.

Yes, it’s a score with a lot of metric modulation going on. The data was originally imported via XML and hand corrected - so it’s really pushing Dorico quite hard.

The Planets - Backup 1-17-2026 - missing bar num in flow 3..dorico

A link to a project file that illustrates this problem.

Thank you Gene,
This is easily solved.
When I open your project, go to flow 3 and select the first 6/8 time signature, I notice that it is a local time signature:

Same with all other instruments (you can see this if you can select each time signature by themselves):

Solution select each local time signature (best in Galley View) and delete them - until you end up with now time signature for that movement at all. Then (re-)input the 6/8 time signature the usual way, problem solved:

These glitches happen quite a lot after music.xml import of files, and it depends how your source program handled time signatures. For me it is routine: after xml import check for local time signatures and delete them, check for implicit clefs and delete them - and much more.

3 Likes

Thanks! I’ve learned something today! :slight_smile: