Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[MU3 Issue] MuseScore 3.6.3 or 3.7.0, PRs to be merged and issues to be fixed. #7449

Closed
Jojo-Schmitz opened this issue Feb 8, 2021 · 10 comments
Closed

[MU3 Issue] MuseScore 3.6.3 or 3.7.0, PRs to be merged and issues to be fixed. #7449

Jojo-Schmitz opened this issue Feb 8, 2021 · 10 comments

Comments

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Feb 8, 2021 •
edited
Loading

PRs available (complete list of PRs against the 3.x branch):

PRs for master that would apply to 3.x and seem worth getting backported:

PRs available (complete list of PRs against the 3.6.2_backend branch not yet merged into 3.x, which should cherry-pick cleanly):

3.5+ Regressions with no PR yet:

(Some copied across from #6505, #6887, #7244, #7347)

3.x regression (post 3.6.2 release)

Other urgent issues or earlier regressions with no PR yet:

  • Fix #306066: Updated build for ARM (and since 2.1!)
  • Fix #313298: MuseScore in Microsoft Store is outdated (and since 3.3.4!)
  • Fix #313840: Issue with saving score online when using "Upload score audio" (and a custom soundfont) (still actual?)
  • Fix #318866: MP3 export fails for instruments not set for Single Note Dynamics, but set for using an "expr." sound (intruduced some time after 3.2.3)

Other long-time and frequent issues (where the real cause still is very unclear):
@Harmoniker1
Copy link
Contributor

Isn't "improve horizontal spacing & vertical alignment" #6312?

@Jojo-Schmitz
Copy link
Contributor Author

yes, corrected

@Harmoniker1
Copy link
Contributor

Why has it been deleted?

@Jojo-Schmitz
Copy link
Contributor Author

Jojo-Schmitz commented Feb 22, 2021 •
edited
Loading

Fat fingered when I added #6021. It is back now

@cbjeukendrup
Copy link
Contributor

cbjeukendrup commented Mar 1, 2021 •
edited
Loading

@Jojo-Schmitz
Copy link
Contributor Author

Added in the initial post already ;-)

@MarcSabatella
Copy link
Contributor

I have no idea what #7941 is supposed to fix, but as far as I can tell, all it does is break something that works perfectly now (scaling of line width as you change scaling for the score).

@Jojo-Schmitz
Copy link
Contributor Author

Jojo-Schmitz commented Apr 12, 2021 •
edited
Loading

We'll see whether it turns into something useful. So far it is just listed as a potential candidate.
Edit: it got closed now

@Jojo-Schmitz Jojo-Schmitz changed the title MuseScore 3.6.3. PRs to be merged and issues to be fixed. [MU3 Issue] MuseScore 3.6.3, PRs to be merged and issues to be fixed. Apr 18, 2021
@Jojo-Schmitz Jojo-Schmitz mentioned this issue Sep 1, 2021
Closed
@Jojo-Schmitz Jojo-Schmitz changed the title [MU3 Issue] MuseScore 3.6.3, PRs to be merged and issues to be fixed. [MU3 Issue] MuseScore 3.6.3 or 3.7.0, PRs to be merged and issues to be fixed. Sep 23, 2021
@Tantacrul
Copy link
Contributor

@Jojo-Schmitz - should this be closed now, since it is so old?

@Jojo-Schmitz
Copy link
Contributor Author

Jojo-Schmitz commented Apr 30, 2022 •
edited
Loading

I don't think so, there are enough things left that have not yet been ported, or at least not been checked for the neccessity.

Hmm, actually I meant #6079
The things from this issue here are mostly done on #9000 and there still isn't any further 3.x planned

@Jojo-Schmitz Jojo-Schmitz mentioned this issue Mar 1, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@Jojo-Schmitz @MarcSabatella @Tantacrul @Harmoniker1 @cbjeukendrup