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.