Skip to content

[MU4] Update Bravura to 1.39 #6704

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

Merged
merged 3 commits into from
Nov 10, 2020

Conversation

Jojo-Schmitz
Copy link
Contributor

@Jojo-Schmitz Jojo-Schmitz commented Oct 20, 2020

As taken fresh from https://github.com/steinbergmedia/bravura
Follow up to #4879, which updated it to 1.32

Counterpart to #5934 (which is in 3,x meanwhile)

@Jojo-Schmitz
Copy link
Contributor Author

Jojo-Schmitz commented Oct 20, 2020

failing vtests expected

@Jojo-Schmitz Jojo-Schmitz changed the title Update Bravura to 1.39 (master) [MU4] Update Bravura to 1.39 Oct 20, 2020
@vpereverzev
Copy link
Member

@Jojo-Schmitz I'm not against of this particular update, but we probably need to update the vtests ref-images in this PR?

@Jojo-Schmitz
Copy link
Contributor Author

Jojo-Schmitz commented Oct 22, 2020

Maybe. But there's a lot of those that need updating and not just for Bravura as far as I can tell? And many/most of the scores used for that are still from 2.x.
IMHO updated vtests is a whole project of its own.

I've tried updating the vtests, but can't get MuseScore 4 to run in converter mode (on Windows) :-(

@vpereverzev
Copy link
Member

@Jojo-Schmitz Oh, I think it's much easier. In CI_vtests job details you can find an artifact "compare" - https://github.com/musescore/MuseScore/suites/1367961822/artifacts/22385020. It contains the "new" images and the existing "refs".

@Jojo-Schmitz
Copy link
Contributor Author

Jojo-Schmitz commented Oct 23, 2020

So just grabbing them from there might be the solution?
Taking the new images and renaming them to ref images?

@vpereverzev
Copy link
Member

Yep, just grab them and upload the new ones here

@Jojo-Schmitz
Copy link
Contributor Author

Jojo-Schmitz commented Oct 23, 2020

That would cover only those this PR changes, but not the ones changed by other already merges ones, like from #6705.
Unless I'll collect those artifacts too (which in this case I could, but might miss others), should I?

@vpereverzev
Copy link
Member

vpereverzev commented Oct 23, 2020

No, I think all you need here is to rebase your branch on the latest master (if you didn't it before). So the result would cover all the difference considering the previous PRs.

@Jojo-Schmitz
Copy link
Contributor Author

Jojo-Schmitz commented Oct 23, 2020

Ah! Of course...

Well, no, it does not. So I'll add the ledgerlines ones too.

and match the orginal filenames from Steinberg to ease further updates
by not using `SymId::wiggleArpeggiatoDownArrow` in a `symbolLine()`
for an `ArpeggioType::DOWN`, but using the same line as
for `ArpeggioType::UP`, just turned upside down.
@igorkorsukov igorkorsukov merged commit e7d3df7 into musescore:master Nov 10, 2020
@Jojo-Schmitz Jojo-Schmitz deleted the bravura-master branch November 10, 2020 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants