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

MuseScore 3.5.1 Release. PRs to be merged and issues to be fixed. #6355

Closed
anatoly-os opened this issue Jul 21, 2020 · 27 comments
Closed

MuseScore 3.5.1 Release. PRs to be merged and issues to be fixed. #6355

anatoly-os opened this issue Jul 21, 2020 · 27 comments

Comments

@anatoly-os
Copy link
Contributor

No description provided.

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Jul 21, 2020 •
edited
Loading

See also https://github.com/musescore/MuseScore/milestone/14 ;-)

@MarcSabatella
Copy link
Contributor

Potentially #6259 (disable playback of chord symbols for older scores), if we get enough feedback to warrant it. I'd need to update a bunch of tests.

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Aug 10, 2020 •
edited
Loading

Other long-time and frequent issues:

3.5 Regressions with no PR yet:

@Harmoniker1
Copy link
Contributor

Harmoniker1 commented Aug 20, 2020 •
edited by anatoly-os
Loading

- [ ] #6472: Implement the third stroke style of minim-based two-note tremolos (moved to 3.6)

@lvinken
Copy link
Contributor

lvinken commented Aug 24, 2020 •
edited by vpereverzev
Loading

  • #6485: Trivial musicxml fixes

@MarcSabatella
Copy link
Contributor

MarcSabatella commented Aug 25, 2020 •
edited by anatoly-os
Loading

A couple of small bugs relevant to chord symbol playback:

@jthistle
Copy link
Contributor

jthistle commented Aug 30, 2020 •
edited by anatoly-os
Loading

^ This one was very much missed going from 3.4 -> 3.5. I hope this PR can be merged to stop the flood of complaints!

@SKefalidis
Copy link
Contributor

SKefalidis commented Sep 1, 2020 •
edited by vpereverzev
Loading

@jthistle
Copy link
Contributor

jthistle commented Sep 2, 2020 •
edited by vpereverzev
Loading

@igorkorsukov
Copy link
Contributor

I added who does what in the inhouse team
#6355 (comment)

@Jojo-Schmitz
Copy link
Contributor

Another really big issue that needs to get looked at is the very many cases of 'no sound'.

@vpereverzev
Copy link
Member

Another really big issue that needs to get looked at is the very many cases of 'no sound'.

Do we have any links related?

@igorkorsukov
Copy link
Contributor

igorkorsukov commented Sep 3, 2020 •
edited
Loading

fix #308978: Display language not set by Windows Language setting
I think it does not require correction, here is an explanation
https://musescore.org/en/node/308978#comment-1023940

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Sep 3, 2020 •
edited
Loading

Another really big issue that needs to get looked at is the very many cases of 'no sound'.

Do we have any links related?

There are literally thousands in the issue tracker and the forum. Across the board, all platforms, all MuseScore versions (since at least 3.0). On average 2 new ones per day.
See "no sound" in the issue tracker

@MarcSabatella
Copy link
Contributor

There are indeed very many cases of people not having sound, but I'm not so sure there are more such cases with 3.5 than earlier releases. But I am quite sure there are very many more startup crashes, with most apparently being connected to the Start Center.

@Jojo-Schmitz
Copy link
Contributor

True, no sound happens frequently, but not particularly more frequent with 3.5 vs befire. Crash on startcenter though came back massively with 3.5

@MarcSabatella
Copy link
Contributor

308890 (an issue with incorrect use of chord symbols) isn't a regression and not really much of a bug at all, just a case where we miss an opportunity to correct a user's error for them.

@Jojo-Schmitz
Copy link
Contributor

True, not a real regression, but something that only now shows with chord symbols playback

@MarcSabatella
Copy link
Contributor

It would have showed the moment you tried to transpose. But anyhow, not really a bug either, and any fix would be a little risky, not worth it for 3.5.1.

@lvinken
Copy link
Contributor

lvinken commented Sep 5, 2020

Working on #309949 and #309950, which I would like to have solved in 3.5.1.

@cbjeukendrup
Copy link
Contributor

Maybe this one too: PR #6561

@lvinken
Copy link
Contributor

lvinken commented Sep 20, 2020 •
edited
Loading

Pull request 6542 now contains:

  • #309949 [MusicXML import] guess page one credit words type
  • #309950 [MusicXML import] fix title frame position
  • #310412 [MusicXML import] alignment and offset of texts in vertical frames not preserved
  • #309702 [MusicXML import/export] support credit-type element
  • #310678 [MusicXML import] incorrect font size in title frame when credit-words size unspecified

It now solves all regressions in handling the title frame on MusicXML import that I am aware of.

@Harmoniker1
Copy link
Contributor

Harmoniker1 commented Sep 20, 2020 •
edited by vpereverzev
Loading

@lvinken
Copy link
Contributor

lvinken commented Sep 23, 2020 •
edited by vpereverzev
Loading

  • #6571 fix #310570 [Musicxml Export] - Triple and Quadruple Dots not exported correctly

@njvdberg
Copy link
Contributor

njvdberg commented Sep 28, 2020 •
edited by vpereverzev
Loading

- [n.a.] #6610 : [Fix #310602](https://musescore.org/en/node/310602) - Adding a tie from grace note to note goes wrong way at times

@ZingBlue
Copy link

Is "no sound" the same as when closing MuseScore, my audio driver breaks and plays static noises until restart?

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Oct 5, 2020 •
edited
Loading

* [ ] #6610 : Fix #310602 - Adding a tie from grace note to note goes wrong way at times
The above mentioned #6610 got closed, being a duplicate of #6510
Neither is a plain 3.5 regression though. But no translatable strings involved either

@Jojo-Schmitz Jojo-Schmitz mentioned this issue Oct 6, 2020
Closed
74 tasks
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