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

Customised positions of beams which begin on a rest are not saved #16919

Closed
Vykoiazon opened this issue Mar 19, 2023 · 3 comments
Closed

Customised positions of beams which begin on a rest are not saved #16919

Vykoiazon opened this issue Mar 19, 2023 · 3 comments
Assignees
@oktophonie @mike-spa
Labels
duplicate Already covered by another issue / addressed in another PR engraving P1 Priority: High

Comments

@Vykoiazon
Copy link

Vykoiazon commented Mar 19, 2023 •
edited by oktophonie

Issue type

Engraving bug

Bug description

When the beam position is adjusted and saved, it goes back to the default placement after reopening the file.

Steps to reproduce

  1. Create a beam which begins on a rest
  2. Move it up or down using the arrow keys (or by dragging, etc)
  3. Save
  4. Close MuseScore and reopen the file

Screenshots/Screen recordings

image

the right beam went back to default placement which could be too close to the rest

MuseScore Version

4.0.2

Regression

No.
@oktophonie oktophonie added the P1 Priority: High label Mar 20, 2023
@oktophonie oktophonie changed the title altered stem lengths do not save Customised position of beams which begin on a rest are not saved Mar 20, 2023
@oktophonie oktophonie changed the title Customised position of beams which begin on a rest are not saved Customised positions of beams which begin on a rest are not saved Mar 20, 2023
@mike-spa
Copy link
Contributor

As far as I can tell, this is already fixed in the latest master by #16602, so I'm going to close it (feel free to reopen in case I'm wrong).

@Jojo-Schmitz

This comment was marked as resolved.

Sign in to view
@MarcSabatella

This comment was marked as resolved.

Sign in to view
@musescore musescore deleted a comment from Jojo-Schmitz Apr 15, 2023
@oktophonie oktophonie closed this as not planned Won't fix, can't repro, duplicate, stale Jun 13, 2023
@oktophonie oktophonie added the duplicate Already covered by another issue / addressed in another PR label Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@oktophonie oktophonie

@mike-spa mike-spa

Labels
duplicate Already covered by another issue / addressed in another PR engraving P1 Priority: High
Projects
MuseScore 4.1
Status: Done
Milestone
No milestone
Development

No branches or pull requests
6 participants
@Jojo-Schmitz @MarcSabatella @muse-bot @oktophonie @mike-spa @Vykoiazon