Playback and navigation issues in layout after updating to 5.1.60

I tried searching for similar issues, but haven’t found anything that sounds like what I’m experiencing.

I just updated to 5.1.60 and have had several headaches. First the audio engine wouldn’t ever initialize and I repeatedly had to terminate the program. I solved that by re-installing the update. I’m not saying this to complain, but for reference in case anyone is dealing with this. A simple re-install may solve that for you.

After the re-install the application launches, but has a new quirk that makes my current task impossible. In the project I’m currently working on, the playback for a specific layout is working correctly. The audio engine is running and the audio plays, but there is no playhead and the view does not follow the playhead. This worked fine before the update and still works in my other layouts. This is really troublesome since I need to make a screen capture of this layout specifically.

Another strange thing affecting only that one layout is that the next/previous flow key command doesn’t work. The [Edit] label in the menu flashes as it recognizes I pressed the key command, but it doesn’t go anywhere. These two issues kind of feel related - like Dorico isn’t sure where anything is.

I’ve tried closing and reopening Dorico, the file, and the layout several times and it doesn’t help. I’ve also tried duplicating the troublesome layout and it just duplicated the problems.

To be clear - the audio works fine and it does play back, there’s just no playhead and the page view doesn’t follow the playback (even though that option is set and it does follow on other layouts and files). My keyboard shortcuts also do work on other layouts. I’m baffled. Does anyone know why this might be happening and how I can fix it?

Thanks for the help.

Edit:
For reference, I’m using an M3 Max MacBook Pro on macOS 14.6.1.

Also, since the update every time I quit Dorico a popup window says that Dorico quit unexpectedly and asks if I’d like to send a report. I didn’t think too much of it since that has happened with Dorico somewhat frequently on this computer, but now it seems to happen every time I quit. Not sure if that’s a separate issue or not though.

Hello malloyca,
this popup comes from Apple. It makes sense to send these reports so they will be able to localise possible incompatibilities with their macOS version. Are you already on the newest macOS 15 Sequoia?

If you could upload the project here then we can take a look.

No, I’m still on macOS 14. I understand that message is from macOS, but it does imply that something about the shutdown procedure isn’t happening correctly. It’s something that happened for me off and on before the update. Since updating it happens every time. It doesn’t seem to have any effect beyond the popups so I send the reports and then don’t worry about it.

I did, however, determine that my playback/navigation issue is not due to the update. I just thought it was due to timing. It’s a page template issue. I reproduced it with 5.1.51 I recovered from Time Machine and an older version of the file. The layout where the playhead disappears and navigation breaks is using a custom page template not based on default or first page. I was then applying this to the entire layout.

This was my first time using a custom page template and when I tested by creating a second custom one without a base it had the same issues. If I create a custom one default or first, it works fine. I’m still getting the hang of templates and template sets.

I solved the issue for my use case by creating a new page template set, modifying default and first templates, and then using the new set. This is probably the way things are intended to be done when you want to apply it to a whole layout anyway. Sorry for the false alarm about the update. I just happened to make the new page template immediately before updating and didn’t notice the issue until after.

Thanks for the replies and offer to look at my project. It doesn’t seem necessary anymore since I was just using page templates and sets incorrectly. Cheers!