Glissando Lines from Grace Note Chord Not Pointing at Separate Notes in Target Chord

Open
#21,531 1 comment 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

Assessment

This issue has not been assessed yet.

Description

engraving feature request P2 UX/interaction
Issue type

Engraving bug (incorrect score rendering)

Bug description

The aim was to create a cluster of grace notes sliding into a chord, however none of the attempts led to the desired outcome, and rather created strange UI behaviours.

Steps to reproduce
  • Create a chord (in a TAB staff with a linked bass key staff in my example)
  • Attempt 1 (not included in screen recording):
  1. Select the chord and create a grace note (acciaccatura)
  2. Watch a single grace note get created in front of the chord, rather than a whole chord consisting of grace notes.
  3. Undo/Remove grace note and prepare for attempt 2.
  • Attempt 2:
  1. Select each of the chord's constituent notes individually and create a grace note for each of them one by one
  2. Watch the 2nd grace note get placed before the 1st, the 3rd before the 2nd, and so forth, rather than the grace notes get stacked to form a chord
  3. (Despite the undesired resulting shape) Add glissando lines between the grace notes with the aim of connecting each grace note with its target note in the chord in the next step.
  4. When trying to move the glissando lines' end points: Watch the end of the glissando lines skip the chord and irreversibly jump to the first note in the next measure instead[^1].
  5. Undo/Remove series of grace notes and prepare for attempt 3.
  • Attempt 3 (3'00" in video):
  1. Select the top note in the chord and create a grace note (acciaccatura again in my example)
  2. Select that grace note in the linked staff and stack additional chord constituent notes above it by using [SHIFT] + [note name] (I don't think that this is possible in a TAB, hence the workaround using the linked staff) and change their pitch as needed
  3. Create glissando lines to connect the individual notes with their corresponding note in the target chord
  4. Watch the lines get connected to the top chord note instead. Their end points cannot be moved up and down the chord stack using the usual [SHIFT] + [↑/↓][^2], only to the right via [SHIFT] + [→], however skipping one beat and jumping to the following measure.

[^1]: This seems to be true when slurs are used instead of glissandi as well, but when a slur is used, it connects the grace note to a different note in the linked staff as compared to the original TAB (Perhaps I should open this as a separate issue)
[^2]: This sometimes gets the line's end point (or that of a slur) to jump to the next staff instead the next stacked note.

Screenshots/Screen recordings

https://youtu.be/qwa4Bjo-h4c

MuseScore Version

MuseScore version (64-bit): 4.2.1-240230937, revision: github-musescore-musescore-d757433

Regression

I don't know

Operating system

OS: macOS 13.6, Arch.: x86_64

Additional context

No response

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

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.

More from musescore/MuseScore

All issues in musescore/MuseScore

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.