musescore / musescore/MuseScore

Breath marks are not deleted when new material is pasted into measure

Open
#26,744 0 comments 0 reactions 1 assignee View on GitHub

@cbjeukendrup is already working on this.

Since Feb 28, 2025.

P3 UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/interaction

Description with steps to reproduce
  1. Create a passage of music that contains a breath mark
  2. Copy/Paste a passage of music that does not contain a breath mark into the measure that does contain a breath mark
  3. Pasted notes and rhythms are correct but breath mark is still present
Supporting files, videos and screenshots

OS: macOS 15.3, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.4-243461245, revision: github-musescore-musescore-2232670

Image

Image shows original measures with measure 1 containing a breath mark

Image

Image shows what occurs when measure 2 is copy/pasted over measure 1. Notice that the breath mark persists.

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

4.4.4-243461245

Regression

I was unable to check

Operating system

OS: macOS 15.3

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.