End of cross-page glissando appears on both pages

• Feb 27, 2015 - 22:27
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore

1. Open attached score (produced in 1.3).
2. 'Layout'>'Page Settings…'.
3. Increase stave space to 1.750mm.
4. 'OK'.

Result: The glissando appears at the start of the system.
Glissando appears at each end of system after resize.png

Note: This is also reproducible in a new score by mimicking the attached one (instruments, instrument names, scaling, line break at bar 1, glissando on the final note of bar 3).

Using MuseScore 2.0 Nightly Build 561cae3 - Mac 10.7.5.

Attachment Size
Glissando appears at each end of system after resize.mscz 2.76 KB
Glissando appears at each end of system after resize.png 44.46 KB

Comments

• Feb 27, 2015 - 22:43
Title Glissando appears at the start of system after resize ⇒ End of cross-page glissando appears on both pages

Looks to be *any* gliss that crosses pages. It is drawn correctly from the end of one page to the start of next, but a second copy of the end segment appears in the same position on the first page.

So you can also reproduce as follows:

1) new score / My First Score
2) add notes to measures 1 & 2
3) add gliss from last note of measure 1 to first note of measure 2
4) add page break to measure 1

Doesn't actually matter what order you do steps 3 & 4 in.

Reply

• Mar 1, 2015 - 22:15

This is probably not the right place for this comment, but I can't find wherever the original reference was.

Miwarre, you were asking about textlines attached to notes. I still have no idea where they came from or what they were actually intended for, but I found out how you can create one: there is a "Note anchored textline" action you can trigger if you define a keyboard shortcut for it in Edit / Preferences / Shortcuts.

Here's the amazing part - they basically work like glissandi! From what I can see, you have to select a range first before giving the command. The textline will be placed above the staff because they are (inappropriately, I guess) inheriting the code that sets the initial position of text lines to be -5sp above the anchor point. But set the vertical offset to 5sp, and you've basically got yourself a glissando, and it does most of the things you'd expect in terms of handling changes to the position of the start or end notes. Except oddly enough, it apparently doesn't inherit the part of the textline code that handles continuation across systems.

Reply