musescore / musescore/MuseScore

Pasting or changing score messes with accidentals

Open
#32,098 1 comment 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

awaiting reply from user engraving needs info
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce
  1. Write music with several notes affected by one accidental in the same bar
  2. Copy and paste somewhere else
  3. OR (as I learned today) change from 4/4 to cut time
  4. Some notes end up with the correct pitch but have change from e.g. Db to C#
Image
Supporting files, videos and screenshots

Fritiof i Arkadien.zip - see bar 37 (there were more but I started correcting them before I realised I should report the bug and now I can't find my backups - sorry)

In which versions of MuseScore Studio is this issue present?

(64-bit): 4.6.5-253511702, revision: github-musescore-musescore-653f38d

Regression

No.

Operating system

Windows 10 Version 22H2 or later, Arch.: x86_64

Additional context

I thought I had already reported the pasting issue since this has occurred for me for years, possibly since MS2.x even. I can't find anything about it when searching here however, so I'm adding it to this report as well. What's new (to me) is that after I added cut time, the same bug happened - suddenly several of my parts had some accidentals flipped. It's not all notes and I can't find a pattern for when it happens.

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.