[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #3445 \retrograde should move the notes to their new location when clef is changed

[Auto mailings of changes to Lily Issues]

No, this does not render as a palindrome since clef changes, like any property changes, now affect the previously preceding rather than following passage. That cannot be changed with reasonable effort as far as I can think of. But the bug report was about the vertical position of the clef changes getting messed up (due to the reversal of the property changes effected by the \clef command). The vertical positions are now again consistent with the clef. Putting clef changes in a retrograde passage, alas, will not be overly useful. But at least now the result is "just" an unsuitable clef, not musical nonsense.

Attachments:

• clf.preview.png (7.2 kB; image/png)

---

[issues:#3445] \retrograde should move the notes to their new location when clef is changed

Status: Duplicate
Created: Sun Jul 07, 2013 01:33 PM UTC by Anonymous
Last Updated: Tue Aug 16, 2016 05:19 PM UTC
Owner: David Kastrup

Originally created by: *anonymous

Originally created by: address@hidden

Report:
http://lists.gnu.org/archive/html/bug-lilypond/2013-06/msg00082.html

% If a clef is changed in retrograde it only prints the new clef
% It does not move the notes to their new locations on the staff
% All notes here are the same pitch but during clef changes it is printed
% incorrectly

\relative c' {
  c1 % printed correctly
  \retrograde {
    c %printed correctly
    \clef treble
    c %printed as though in bass clef
    \clef treble
    c % Should be one ledger line above not below the staff in bass clef
    \clef bass
    c % Correctly printed in the assumed Treble clef
  }
}

Comment from Harm:

\retrograde was implemented in 2.13.x
See
http://lilypond.org/doc/v2.13/Documentation/changes-big-page.html

There you can read:
"A minimal composer toolkit of modal transformations is provided. A
motif may be transposed, inverted and/or converted to its retrograde
within any scale."
This should be read as: "A composer toolkit, with minimal functionality." ;)

In 2.17.-NR
http://lilypond.org/doc/v2.17/Documentation/notation/changing-multiple-pitches#retrograde
you can read
"Known issues and warnings
Manual ties inside \retrograde will be broken and generate warnings. ... "

Though not only Ties are broken. As the Nr-example shows Slurs are not
printed. Hairpins will return warnings, every simple \override will
lead to surprising results, setting clef-changes (much more complex,
than a simple \override), too.

So far I've tested.

So yes, \retrograde should be improved.
I'd call it an enhancement-request.

---

Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

------------------------------------------------------------------------------

_______________________________________________
Testlilyissues-auto mailing list
address@hidden
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto