-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Soprano Voice on Mixer #23382
Comments
Alt click the choir in musehub and uninstall it then reinstall. |
unfortunately alt+click (uninstall) doesn't work. So I manually deleted and reinstalled and it didn't work. MuseScore still doesn't see the soprano voice. |
What specifically do you mean when you say Alt+click "doesn't work"? Do you mean it doesn't uninstall, or that the uninstall was not effective in resolving the issue? On some Linux systems, Alt+click doesn't work directly as that gesture is reserved by the OS apparently. But you can still trick the system into allowing the operation by using Alt+Tab to switch to another window, then Alt+Tab back. Now you'll have delete buttons you can click normally. |
Hello Marc; I was able to uninstall the choir sounds with the information in the second paragraph. Thank you very much. I thought this was a bug for a long time. And the soprano voice is back :) I'm closing this bug. Thanks. |
Issue type
UI bug (incorrect info or interface appearance)
Bug description
Hello, I am using MuseScore Studio 4.3.2(x64) and MuseSound Manager Beta 1.1.0.587(x64) on Linux Mint operating system. I guess after the last MuseScore Studio update MS Studio can't find the soprano voice. I deleted the soprano in the folder containing the sounds, and then MS Manager noticed the absence and reinstalled the soprano. However, MuseScore Studio still cannot find the soprano voice. And I'm getting this bug in MS Studio 4.4.0 as well.
Steps to reproduce
Screenshots/Screen recordings
MuseScore Version
4.3.2, 4.4.0(ninghtly)
Regression
I don't know
Operating system
Linux Mint 21.3 Cinnamon
Additional context
No response
The text was updated successfully, but these errors were encountered: