Stems disappearing when beaming a group and moving

musescore / MuseScore

MuseScore is an open source and free music notation software. For support, contribution, bug reports, visit MuseScore.org. Fork and make pull requests!

https://musescore.org

Other

12.27k stars 2.66k forks source link

Stems disappearing when beaming a group and moving #24635

Open swanhes opened 1 month ago

swanhes commented 1 month ago

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

See the attached video

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/23716c08-d6c5-4695-ade9-a138c434b087

What is the latest version of MuseScore Studio where this issue is present?

MuseScore Studio version (64-bit): 4.4.0-242390800, revision: github-musescore-musescore-0fcd11b

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

macOS 14.6.1

Checklist

[X] This report follows the guidelines for reporting bugs and issues
[X] I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
[X] I have attached all requested files and information to this report
[X] I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

swanhes commented 1 month ago

It happens only when the stem is directed downwards

oktophonie commented 1 month ago

I can't reproduce this in a new file with a simple example. Are you able to, or does it seem specific to this file? Was the file created in 4.4, or in which earlier version?

Does the layout problem fix itself when you make other edits elsewhere, or after a save/reload?

swanhes commented 1 month ago

Sorry, I edited with the correct MuseScore version.

swanhes commented 1 month ago

The problem does not fix with saving or editing elsewhere; in fact, sometimes it happens after edits in the parts of the score.

Adding a video of the same problem on a shoe created with the same MuseScore version i'm editing it on: https://github.com/user-attachments/assets/01b40c76-5384-4283-9d6c-3658a318ec38

swanhes commented 1 month ago

I doesn't happen on new scores or saved selections as new scores. Could it be something related to the number of notes in the score?

swanhes commented 1 month ago

Sometimes it solves by itself, when moving, for example, a rest and switching it back, as it triggers (I suppose) a refresh.

On a side note, I think a refresh gaphics button should be added.

oktophonie commented 1 month ago

I asked because I was reminded of this issue from long ago: https://github.com/musescore/MuseScore/issues/15401 (which may be totally unrelated anyway)

If you're able to supply any file where this can be reliably reproduced, it would help.

An explicit graphics refresh should never be necessary.