musescore / musescore/MuseScore

Glissandi are allowed to cross over other notes within the same voice

Open
#24,299 1 comment 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Aug 30, 2024.

P3 regression MS4 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 passage with at least 3 notes

  2. Create a glissando from the first to the second note

  3. Press Shift+right arrow on the ending node.
    Expected behaviour: No reaction- this should be an invalid movement
    Actual behaviour: The glissando connects the first and third note, crossing over the second note. Upon playback, the glissando happens within the span of the first note as expected, but the second and third notes then play.

  4. Delete the second note to create a rest in its place
    Actual behaviour: The gliss plays back in the span of the first note, then a rest plays, then the final note
    OR

  5. Press Shift+right arrow on the starting node
    Expected behaviour: the first note does not glissando on playback
    Actual behaviour: The first note glissandos as if the third note would play when the second note would, but then the second note plays its glissandi into the third

Supporting files, videos and screenshots

Untitled score.mscz.zip

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

4.4.0

Regression

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

Operating system

macOS 14.4.1

Additional context

Possibly related to #24300

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.