Bonjour, I wanted to hide some empty staff in a score,
doing so, it instantly crashes.
I tried with a old project, same result. it did work in the past.
I believe a corruption of some sort happened this morning.
I am attaching a diagnostic report and a dorico project
Thank you for your help and wishing you all a beautiful 2025
B.
Dorico Diagnostics.zip (3.1 MB)
project crashes.dorico (1.6 MB)
Hi @midiese, I tried with Manual Staff Visibility (for Oboes) in your project, and no problems on my system. I attach the file: can you try to open it and see if the issue persists? I am sure someone of the Team will also comment on your Diagnostics.
project crashes-manual staff visibility applied.dorico (1.6 MB)
Salut @Christian_R ,
well, the file you sent me crashes when I want to reset staff visibility.
I’ll wait for a diagnostic report examination, there is obviously wrong on my side.
Thank you someone at Dorico team for your look into this!
Benoit
Maybe you can upload a second Dignostics after this further crash.
Thanks for uploading the diagnostics, Benoit. The crash is occurring in the dialog, but it’s not clear to me exactly what’s going on. It looks like some kind of keyboard event is triggering a crash somewhere in the Qt platform plug-in. Do you have any third party keyboard software installed, or do you have any unusual OS settings for keyboard handling?
Hi Daniel,
thank you for your reply.
Actually, I am preparing a seminar for my composition students on using dorico and since a few of them are using a french canadian (qwerty) keyboard, some other a english (US) keyboard, I am preparing a sheet with the main shortcuts and where they sit on the different keyboards. For that purpose, I rely on the keyboard visualisor (see picture).
my dorico preferences are set to default language and key commands to english (I have a apple full keyboard, (english) hooked to my m2 apple laptop (with french keyboard).
Would there be a preferences folder I could trash to solve this issue?
Merci
B.
Using the operating system’s built-in tools for changing input method shouldn’t be a problem. Do you have “full keyboard access” enabled or any of the other accessibility settings related to the keyboard?
Salut Daniel,
The crash only happens when I have the keyboard viewer on,
as these screen recording show.
Thank you
Benoit
Crash_with keyboard viewer.mov
No_crash_no_Keyboard viewer.mov
Salut Daniel,
no, full acces keyboard is off.
I made two short videos for you. (sent via email since I am not able to upload here. The crash only happens when I have the keyboard visualiser on. When I do not open it, there is no crash.
Benoit
I don’t think I’ve received your email, Benoit. Can you perhaps try sending me the videos again using a service like WeTransfer?
Ok Daniel,
what email adress can I use?
Benoit
Alo Daniel,
hoping this reply gets to you!
Benoit
Crash_Benoit.zip
You can email me at d dot spreadbury at steinberg dot de. However, I don’t have a Google account for my work email address, so perhaps you can send me the file via WeTransfer to my work address.
Thanks, Benoit. I was able to reproduce this problem, and we’ll fix this in due course. For the time being, you’ll need to close the Keyboard Viewer before you confirm the dialog with the keyboard. The problem won’t affect all dialogs in Dorico, but it will affect quite a number of them, so I would definitely recommend keeping the Keyboard Viewer closed when possible. I know this will be inconvenient for you, and I’m sorry about that.
Merci Daniel,
I will upload a keyboard viewer as pdf , so no worries and thank you for looking at this for all of us
Benoit
