musescore / musescore/MuseScore

Ties missing when overwriting existing note in note-entry mode

Open
#34,398 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce
  1. Create a long note (eg whole note) and select it
  2. Enter note-entry mode ("N")
  3. Choose a short note (eg 32nd note) length
  4. Add note

Expected: New note added. Old note reduced by that length, using ties.

Actual: New note added. Notes are created to replace the old note, but no ties.

Supporting files, videos and screenshots
Image Image
In which versions of MuseScore Studio is this issue present?

4.7, also main

Regression

The same behavior in MuseScore 3.6.2

Operating system

macOS

Additional context

No response

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.

Research direction

Reproduce the issue in MuseScore Studio 4.7 or main using the listed whole-note and 32nd-note steps. Start by tracing note-entry mode's handling of replacing a selected note and compare the result with the expected duration split. Done means the replacement creates the required tied notes while preserving the old note's remaining duration.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.