-
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
MuseScore 3.5 Release Candidate. PRs to be merged #6195
Comments
|
Fixes bugs and regressions introduced in #5623, #5922, and #6186. |
|
Still not totally clear on the criteria for what is being considered, but to me these are good candidates. They are not regressions (well, not new regressions in 3.5 anyhow) but they do address some real pain points that are easily solved. And they don't involve new strings or otherwise require new documentation, they just allow things to work that people have every right to expect to work anyhow.
|
The following issue needs to be resolved: https://musescore.org/en/node/307005. The following PR addresses it directly: And then also
Another possible approach is #6259 which disables chord symbol playback for pre-3.5 scores, but I think the consensus is #6268 is preferable. |
|
|
|
|
|
By popular demand. Undoes the change to the default zoom type that was made in #5623. |
I edited a comment above to list #6268 (changes default playback sound for chord symbols to piano) as the consensus on how to handle compatibility/surprise concerns for older scores with chord symbol playback. |
Yet unresolved issues (without PRs, as those don't make sense there):
|
|
This would really help to have this added to the 3.5 release, as it would make it easier for the folks over at HaikuPorts (Haiku’s main package management repo). |
|
|
This PR also fixes an issue of the stem length becoming a bit longer than necessary for chords with tremolo strokes and a downward stem. |
I'd like to see this PR in 3.5RC, even if not being a 3.5 regression, but it finally seems to make continuous mode with lyrics usable again: |
No PR yet, but this is a serious regression that needs to be fixed:
|
I believe this is important for 3.5, otherwise people will employ workarounds that will break when this does get fixed:
|
|
Congratulations with 3.5 Release Candidate! https://musescore.org/en/3.5rc |
The text was updated successfully, but these errors were encountered: