Re: Required font for simplified Chinese characters?
On Sat, 09 Dec 2017 14:23:46 +0800 Andrew Bernard wrote > With the release of stable version 2.20 coming out in the forseeable future, > and with 2.19.80 being really stable and excellent, could you considering > moving up? No crash occurs at 2.19.80, and there are dozens of really good > new features in this series, well worth having. Sorry to come back very late to this thread. I just tried 2.19.80, and this version *can* render simplified Chinese characters. Yes! BUT... in 2.19, the handling of landscape orientation has changed. In my v2.18.2 document, I used: #(set-default-paper-size "a4" 'landscape) ... and I got a document that was wider than it is tall, and I could read the notation on screen directly. That's what I wanted. In 2.19.80, without changing the code, I got a document whose paper is in portrait orientation, and whose notation was rotated 90 degrees counterclockwise. Staff lines read *upward* (???!) on the screen. Which... for reading is... shall we say, difficult. #(set-default-paper-size "a4landscape") gives me the layout I wanted. I'm not sure if this is intentional. The manual says "If the symbol 'landscape is added to the paper size function, pages will be rotated by 90 degrees, and wider line widths will be set accordingly." I am seeing that the page *contents* were rotated by 90 degrees and line widths were set accordingly, but the page dimensions did not rotate. So it isn't accurate to say that the **pages** will be rotated. Try it yourself: \version "2.19.80" #(set-default-paper-size "a4" 'landscape) \relative c' { c4 d e f g a b c } Is it a bug, or out-of-date documentation? I'm fairly sure nobody wants the behavior that is currently documented as the first option. hjh ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \magnifyStaff for dynamics?
On 12/20/2017 8:03 PM, Mason Hock wrote: \version "2.19.63" \score { << \new Staff \with { \magnifyStaff #(magstep -3) } \relative c' { c c c c } \new Dynamics \with { \override VerticalAxisGroup.staff-affinity = #UP } { s\p\< s s s\f} >> } Is there a way to magnify the dynamics staff by the same factor as the music staff? Thanks, Mason You could use something like this to change the font of the dynamics too? << \new Staff { \relative c'' { \dynamicDown c8\ff c c c c c c c } } \new Staff \with { *fontSize = #-3 \override StaffSymbol.staff-space = #(magstep -3)* } { \clef bass c8 c c c c\f c c c } http://lsr.di.unimi.it/LSR/Item?id=399 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
\magnifyStaff for dynamics?
\version "2.19.63" \score { << \new Staff \with { \magnifyStaff #(magstep -3) } \relative c' { c c c c } \new Dynamics \with { \override VerticalAxisGroup.staff-affinity = #UP } { s\p\< s s s\f} >> } shrinks the music staff as expected but does not shrink the dynamics staff. \version "2.19.63" \score { << \new Staff \with { \magnifyStaff #(magstep -3) } \relative c' { c c c c } \new Dynamics \with { \override VerticalAxisGroup.staff-affinity = #UP \magnifyStaff #(magstep -3)} { s\p\< s s s\f} >> } gives In procedure ly:context-property in expression (ly:context-property Staff (quote magnifyStaffValue)): /home/mason/.guix-profile/share/lilypond/2.19.63/scm/music-functions.scm:2513:19 <1>: Wrong type argument in position 1 (expecting Context): #f Exited with return code 1. Is there a way to magnify the dynamics staff by the same factor as the music staff? Thanks, Mason ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: single Note swell
Some explanations: On 20.12.2017 22:42, Simon Albrecht wrote: On 20.12.2017 01:21, Vivyan wrote: code to instruct a swell for the duration of c2 There’s several possibilities: First, LilyPond has the built-in command \espressivo (which is technically not a dynamic script, but an articulation): %% { c2\espressivo } %% Second, your ‘example’ hints at this strategy: %% \context Voice << { c2 } { s4\< s\> <>\! } >> %% \context Voice is used to reference an existing voice context. In this case, it prevents the <<>> construct from automatically creating two voices, since what you want in this case is two simultaneous music expressions within one voice. The empty chord <> takes up no time and thus can be used to terminate the hairpin here. Third, you could use this: %% after = #(define-music-function (t e m) (ly:duration? ly:music? ly:music?) #{ \context Bottom << #m { \skip $t <> -\tweak extra-spacing-width #empty-interval $e } >> #}) { \after 8. \> \after 4. \! c2\< } %%% If you want to use this, it is recommendable to put this music function definition in a library file and \include that file in your actual .ly document. This is basically a nicer user interface for the second solution above, with easier legible source code: “After a dotted eighth note duration, insert a \>, and after a dotted quarter note duration, insert a \<, on the note c2\<.” HTH, Simon It’s up to you which you prefer. Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: single Note swell
On 20.12.2017 01:21, Vivyan wrote: code to instruct a swell for the duration of c2 There’s several possibilities: First, LilyPond has the built-in command \espressivo (which is technically not a dynamic script, but an articulation): %% { c2\espressivo } %% Second, your ‘example’ hints at this strategy: %% \context Voice << { c2 } { s4\< s\> <>\! } >> %% Third, you could use this: %% after = #(define-music-function (t e m) (ly:duration? ly:music? ly:music?) #{ \context Bottom << #m { \skip $t <> -\tweak extra-spacing-width #empty-interval $e } >> #}) { \after 8. \> \after 4. \! c2\< } %%% It’s up to you which you prefer. Best, Simon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Rhythmic Excerpts with Breath Marks Above the Staff
Perfect! Thank you so much, David. Best, Reilly ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Rhythmic Excerpts with Breath Marks Above the Staff
Hi Reilly, On Wed, Dec 20, 2017 at 11:56 AM, Reilly Farrellwrote: > I'm seeking a way to create rhythmic examples, as in the sample code below, > while positioning breath marks above the rhythmic staff rather than along > the line. I thought ^\breathe might do the trick at first, but no dice. Any > advice on how to properly accomplish this is deeply appreciated. Thank you! > > > \version "2.18.2" \include "../../../lily-settings.ily" stuff = { \time 4/4 > } \new RhythmicStaff { c4 c4 c4 c4\breathe | c2 c2\breathe | c1 | } \include > \compileRhythmSyllablesPath \end{lilypond} > Adjust to your liking: \new RhythmicStaff { \override BreathingSign.Y-offset = 3 c4 c4 c4 c4\breathe | c2 c2\breathe | c1 | } HTH, David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Rhythmic Excerpts with Breath Marks Above the Staff
I'm seeking a way to create rhythmic examples, as in the sample code below, while positioning breath marks above the rhythmic staff rather than along the line. I thought ^\breathe might do the trick at first, but no dice. Any advice on how to properly accomplish this is deeply appreciated. Thank you! \version "2.18.2" \include "../../../lily-settings.ily" stuff = { \time 4/4 } \new RhythmicStaff { c4 c4 c4 c4\breathe | c2 c2\breathe | c1 | } \include \compileRhythmSyllablesPath \end{lilypond} ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: single Note swell
Vivyanwrites: > just trying this bit of code to instruct a swell for the duration of c2, > this hasn't quite work? >c2'' { s2 s\< s\> s\! } The first thing to try if you get an example from somewhere is to use it _unmodified_ and see whether you get it to run. If not, you won't be able to adapt it to your purposes. The code you apparently tried working with certainly had << >> around it. Those are not decorations but are an essential part of the input. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user