Re: [snippet] Repeats with parallelMusic
Pierre Perol-Schneider writes: > 2014-07-02 12:13 GMT+02:00 David Kastrup : > > >> However, this fix does not have regtests. I would appreciate it if you >> could cook up a few short but difficult use cases for placing in the >> regtests. >> > > In order to find a sort of inspiration I've just re-wrote some snippets > from the regression in parallelMusic mode. [a dozen rewrites] Uh, wow. Now it would be overkill to add all of them, and it also would be strange to _replace_ all of them: \parallelMusic is a somewhat specific feature and somewhat hackish at that, so I would not want to have a lot of tests intended to check something else depend on it (we have things like \relative that get a _lot_ of incidental testing through unrelated regtests, but I don't like \parallelMusic enough for that). I'll look through those and see which ones seem to be important. Of course, one important criterion would be that they pass after this patch though not before. If they pass before, they don't test for the versatility this patch should have provided. If they don't pass afterwards, of course I want to take a look as to why... Did you check the resulting snippets, or was this a "dry run"? If you did check, I don't need to do so myself. > Hope I'll find something better tomorrow. Well, a good regtest should be thorough with regard to the tested feature and keep to reasonably basic constructs otherwise. It should also be simple to make a good guess from description and result whether it does what is intended. The guitar examples I have seen in this thread (and the old 2009 one) are actually not bad as an indicator since they make a lot less musical sense when \parallelMusic breaks down. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: solfege display for tie & slur (re-submit to list)
Thomas Morley writes: > well, in the mentioned thread I added/changed some code, though, I'm > not the author of the solfege-engraver. > > Nevertheless, I'll try to dig into it the upcoming days. Right now > I've less, down to absolutely no time for it. Well, for figuring out how to connect ties, the Grob_pq_engraver output might be useful as long as no tieWaitForNote is being used. Actually, that's one of the least helpful engraver names I've encountered in LilyPond. "pq" stands for "priority queue" and is an implementation detail. Something like Active_grob_tracker would likely be more telling (it maintains a list of grobs that are still musically significant at the current moment). -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ticks
On Thu, 2014-07-03 at 08:57 +0200, Robert Schmaus wrote:
> If you search for "Rhythmic Slashes" within the v2.18 snippets documentation,
> you'll find another way of creating those slashes - that approach has the
> advantage that the slashes will be silent in MIDI.
http://www.lilypond.org/doc/v2.18/Documentation/snippets/rhythms#rhythms-rhythmic-slashes
coincidentally, I was asked recently for slashes in chord symbols and
used this
\set noChordSymbol = "\\"
using rests where slashes were required. The attached shows the desired
effect in this case.
Richard
> Best, Robert
>
>
> > On 2 Jul 2014, at 23:06, Francisco Vila wrote:
> >
> > 2014-07-02 22:10 GMT+02:00 Janek Warchoł :
> >>
> >> What about
> >>
> >> {
> >> c' f' b' g'
> >> \new Voice \with {
> >>\consists "Pitch_squash_engraver"
> >>\improvisationOn
> >>\omit Stem
> >> } {
> >>c c c c
> >> }
> >> f'2 g'
> >> }
> >>
> >> ?
> >
> > Ah yes, improvisation notes without the stems. Thank you!
> >
> > --
> > Francisco Vila. Badajoz (Spain)
> > www.paconet.org , www.csmbadajoz.com
> >
> > ___
> > 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
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Issue on packed-spacing?
Hi,
Is this the desired behavior of SpacingSpanner.packed-spacing ? (I'm
using 2.18.2)
\paper { ragged-rigth = ##t ragged-last = ##t }
\relative c' {
\override Score.SpacingSpanner #'packed-spacing = ##t
c8 c c-\markup{"some very very very very very very long text"} c c c c c |
\repeat unfold 24 {c}
}
--
Abel Cheung
New GPG Key fingerprint: F43B 7F88 3D7B 4B58 928E 0151 EC2B E414 3B03 A8AC
Old GPG Key fingerprint: 671C C7AE EFB5 110C D6D1 41EE 4152 E1F1 C671 86FF
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
[openlilylib] Discuss restructuring
Hi to all interested or involved in the openlilylib (a.k.a openlilylib snippets) repository. Our repository has now lived for some time, and I think it is a good thing to have and maintain. The recent renaming was partially intended to stress its nature as an _includable_ library (as opposed to the official LSR). But to make that work for a longer time and to make it scale with an increasing amount of content I think we now need a fundamental restructuring of its directory structure. I have set up a page displaying the current and discussing my initial ideas in the project wiki: https://github.com/openlilylib/openlilylib/wiki So anybody who is interested in this library is invited to discuss the issue. I think that after an initial phase of trial & error we should now do it right and create a structure we can live with for the future. Best Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Issue on packed-spacing?
Am 03.07.2014 10:03, schrieb Abel Cheung:
Hi,
Is this the desired behavior of SpacingSpanner.packed-spacing ? (I'm
using 2.18.2)
\paper { ragged-rigth = ##t ragged-last = ##t }
\relative c' {
\override Score.SpacingSpanner #'packed-spacing = ##t
c8 c c-\markup{"some very very very very very very long text"} c c c c c |
\repeat unfold 24 {c}
}
I'm not completely sure what you mean, but does overriding on Staff
context do what you want?
Urs
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Issue on packed-spacing?
The artifact here is (forget the ragged-rigth typo), when using
packed-spacing, the whole note with markup is stretched horizontally
in an insane way to cope with the markup size, and I wonder if this is
the designed behavoir of lilypond.
On Thu, Jul 3, 2014 at 4:08 PM, Urs Liska wrote:
> Am 03.07.2014 10:03, schrieb Abel Cheung:
>
>> Hi,
>>
>> Is this the desired behavior of SpacingSpanner.packed-spacing ? (I'm
>> using 2.18.2)
>>
>> \paper { ragged-rigth = ##t ragged-last = ##t }
>> \relative c' {
>>\override Score.SpacingSpanner #'packed-spacing = ##t
>>c8 c c-\markup{"some very very very very very very long text"} c c c c
>> c |
>>\repeat unfold 24 {c}
>> }
>>
>
> I'm not completely sure what you mean, but does overriding on Staff context
> do what you want?
>
> Urs
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
--
Abel Cheung
New GPG Key fingerprint: F43B 7F88 3D7B 4B58 928E 0151 EC2B E414 3B03 A8AC
Old GPG Key fingerprint: 671C C7AE EFB5 110C D6D1 41EE 4152 E1F1 C671 86FF
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Issue on packed-spacing?
OK, maybe it's clearer to attach image.
On Thu, Jul 3, 2014 at 5:35 PM, Abel Cheung wrote:
> The artifact here is (forget the ragged-rigth typo), when using
> packed-spacing, the whole note with markup is stretched horizontally
> in an insane way to cope with the markup size, and I wonder if this is
> the designed behavoir of lilypond.
>
> On Thu, Jul 3, 2014 at 4:08 PM, Urs Liska wrote:
>> Am 03.07.2014 10:03, schrieb Abel Cheung:
>>
>>> Hi,
>>>
>>> Is this the desired behavior of SpacingSpanner.packed-spacing ? (I'm
>>> using 2.18.2)
>>>
>>> \paper { ragged-rigth = ##t ragged-last = ##t }
>>> \relative c' {
>>>\override Score.SpacingSpanner #'packed-spacing = ##t
>>>c8 c c-\markup{"some very very very very very very long text"} c c c c
>>> c |
>>>\repeat unfold 24 {c}
>>> }
>>>
>>
>> I'm not completely sure what you mean, but does overriding on Staff context
>> do what you want?
>>
>> Urs
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
>
> --
> Abel Cheung
> New GPG Key fingerprint: F43B 7F88 3D7B 4B58 928E 0151 EC2B E414 3B03 A8AC
> Old GPG Key fingerprint: 671C C7AE EFB5 110C D6D1 41EE 4152 E1F1 C671 86FF
--
Abel Cheung
New GPG Key fingerprint: F43B 7F88 3D7B 4B58 928E 0151 EC2B E414 3B03 A8AC
Old GPG Key fingerprint: 671C C7AE EFB5 110C D6D1 41EE 4152 E1F1 C671 86FF
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Issue on packed-spacing?
- Original Message -
From: "Abel Cheung"
To:
Sent: Thursday, July 03, 2014 10:40 AM
Subject: Re: Issue on packed-spacing?
OK, maybe it's clearer to attach image.
On Thu, Jul 3, 2014 at 5:35 PM, Abel Cheung wrote:
The artifact here is (forget the ragged-rigth typo), when using
packed-spacing, the whole note with markup is stretched horizontally
in an insane way to cope with the markup size, and I wonder if this is
the designed behavoir of lilypond.
On Thu, Jul 3, 2014 at 4:08 PM, Urs Liska wrote:
Am 03.07.2014 10:03, schrieb Abel Cheung:
Hi,
Is this the desired behavior of SpacingSpanner.packed-spacing ? (I'm
using 2.18.2)
\paper { ragged-rigth = ##t ragged-last = ##t }
\relative c' {
\override Score.SpacingSpanner #'packed-spacing = ##t
c8 c c-\markup{"some very very very very very very long text"} c c c
c
c |
\repeat unfold 24 {c}
}
Looks like a bug to me.
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Denemo 1.1.6 Release
Denemo version 1.1.6 has been released. There have been improvements to the LilyPond editing which have actually been present since version 1.1.2 but I've been getting behind with announcing releases here. Also, asked for on this list are French 18th c keyboard ornaments - full support for creating new ornaments is in the next release. Below is the release announcement plus feature lists of the previous two releases. Richard Denemo is a program for inputting music notation. http://www.denemo.org The music is displayed as music notation while typing or playing in and simultaneously it can be typeset via LilyPond. It can also be played via internal synthesizer. Demo videos are at https://vimeo.com/62188678 New features in this version: Lyrics Interface Cursor on music moves to match cursor in lyrics Jump to any point in the lyrics by mouse or keyboard The inactive pane (lyrics or music) clearly indicated by graying-out Margins Control Set top, bottom, left and right margins in mm. Tweaking Typesetting Individual notes, chords and rests can be tweaked Accidentals and markings move with the note Fingerings can be offset For use when LilyPond is sub-optimal Fret Diagrams Chords typeset as fret diagrams Defaults to Guitar Can be used with Chord Names too Comprehensive Musical Symbol Support Menu access to the complete set of LilyPond music symbols Over 600 types of music glyphs can be placed and dragged on the score More Ornamentation Support Coulés Arpègements Suspensions Editing Timer Displays time spent creating a score Accumulates over all editing sessions Known issues for this release: none http://ftpmirror.gnu.org/denemo/denemo-1.1.6.tar.gz If automatic redirection fails, the list of mirrors is at: http://www.gnu.org/order/ftp.html Or if need be you can use the main GNU ftp server: http://ftp.gnu.org/gnu/denemo/denemo-1.1.6.tar.gz Denemo version 1.1.4 has been released. New features in this version: Spillover Appending over-length notes spill into next bar. Works for rests too. Optional – set a preference for old behavior. Shortcuts Cheat Sheet Current set of shortcuts listed. Alphabetical order. Gives description of command. Support for Aubio 4 Microphone Input Note Detection. Note Onset Detection. Instrument Tuning. General Seek and Edit Facility Choose from all available object types in movement. Choose from objects at cursor. Seek and edit the chosen type in music playing order. Restart last search, wrap to beginning, to next movement. Display Editing Control+Shift drag to move objects in the input music display Does not affect the final typeset score. Useful when the input music display is too cluttered to see clearly. MusicXML import Imports Titles, copyright and other text Imports dynamic markings Denemo version 1.1.2 has been released. Links to source files can be relative to current score location Transcribing from MIDI Play in to a click track. Enter rhythm afterwards. Guided MIDI import Durations can be checked as they are entered. Support for LilyPond 2.18 Old scores are updated for incompatible syntax. Re-shaping/Re-positioning Ties Both WYSIWYG and tweaking width/height/convexity. LilyPond View Improvements Bracket Matching. Line numbering visible. Cursor position highlighted. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [snippet] Repeats with parallelMusic
Pierre Perol-Schneider writes: > 2014-07-02 12:13 GMT+02:00 David Kastrup : > > >> However, this fix does not have regtests. I would appreciate it if you >> could cook up a few short but difficult use cases for placing in the >> regtests. >> > > In order to find a sort of inspiration I've just re-wrote some snippets > from the regression in parallelMusic mode. > Hope I'll find something better tomorrow. Now looked at the test. Most of those are rather equivalent in their complexity (so "sort of inspiration" would appear to indeed mean mostly finger exercises) and would have worked without the patch in place. alignment-order-prallelMusic.ly using nested \parallelMusic constructs is rather weird: I don't think we should explicitly support it. The only complex test seems to be volta-multi-staff-prallelMusic.ly but since _all_ of its voices are apparently identical, it is not all that useful for detecting problems. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
hacked?
Sir or Madam, This e-mail arrived in my in box this morning. It appears that the list has been compromised. Mark Stephen Mrotek -Original Message- From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of janov...@yahoo.com Sent: Wednesday, July 02, 2014 11:49 PM To: lilypond-user@gnu.org Subject: Re: Hi! http://enneyapi.com/_redirect?odene675228 ___ 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: hacked?
On 03/07/14 14:22, Mark Stephen Mrotek wrote: Sir or Madam, This e-mail arrived in my in box this morning. It appears that the list has been compromised. No I think it that this users email address janov...@yahoo.com has been compromised, and as he is subscribed to the Lilypond list (and probably has this lists email address) in his address book, that that is why we and anyone else in the list see this. Mark it as spam (it was already in the spam folder in my own email). I have cc'd the user. Thanks James Mark Stephen Mrotek -Original Message- From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of janov...@yahoo.com Sent: Wednesday, July 02, 2014 11:49 PM To: lilypond-user@gnu.org Subject: Re: Hi! http://enneyapi.com/_redirect?odene675228 ___ 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 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: hacked?
James writes: > On 03/07/14 14:22, Mark Stephen Mrotek wrote: >> Sir or Madam, >> >> This e-mail arrived in my in box this morning. It appears that the list has >> been compromised. > No I think it that this users email address > > janov...@yahoo.com > > has been compromised, and as he is subscribed to the Lilypond list > (and probably has this lists email address) in his address book, that > that is why we and anyone else in the list see this. > > Mark it as spam (it was already in the spam folder in my own email). > > I have cc'd the user. Not sure who is our list moderator, but it should be possible to put mails from this user under moderation by default until he/we are sure that his problem has been fixed. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Capped tuplet number
Is it possible to add these caps to tuplet numbers? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [openlilylib] Discuss restructuring
Hi, I like your ideas on the wiki. - I'd like to second especially the renaming/reodering of the definitions file. It looks better without definition(s).ily at the end. However, it means that the content of the library doubles (one folder and one ily). I am not sure, if it is a good idea, but the readme and the examples do not need to be includable and internal files should then go to helper-files (as far as I understand), so: how about only .ily files in the include-path and the rest elsewhere? - I had problems distinguishing these categories: - general-tools - input-shorthands - notation-snippets - specific-solutions While I could understand some of those from their content (or the description), I found it hard to draw the line between them in each case. What you propose now (layout, tweaks, text, lyrics, notation) is more intuitive for me. I see some border-cases/issues: - Is notation only for music? A function for lyrics or text would go in their categories? - I don't see yet what would go into »specific instruments/repertoire« - Where would the music-fonts go? (I would suggest the custom- because anything here is custom) - What is period? - Btw, I always found the »markup« annoying, because it is such a technical term. »text« would be more straightforward, even if it is extended with markup commands. - Why is a 2nd »meta« folder inside library? - +1 for the lowercase-dash-naming - Will openlilylib and snippets be the same? Does openlilylib contain all the LilyPond resources or only the the includable part and the meta folders etc. I am a bit confused about the naming. lilylib is outdated, right? - I would like to remind the idea of a preview-image-overview over the library. Those are just my comments. Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Fwd: Re: Capped tuplet number
I really should remember to always answer to the list ... Original Message Subject: Re: Capped tuplet number Date: Thu, 03 Jul 2014 18:03:53 +0200 From: Malte Meyn To: Javier Ruiz-Alma Of course it is. I don’t have an exact solution but I think one could change the TupletNumber text to some \markup \center-column … You could use the frown symbol from Unicode (U+2322). Or, instead of the \center-column, you could try to use a combining inverted breve (U+0311) or a similar symbol. But why would you want that? For me these caps look like tuplet brackets or slurs. But the Henle Urtext edition of Chopin’s first Ballade doesn’t show slurs in bar 183, so I tend towards “probably these are tuplet brackets”. On 03.07.2014 17:52, Javier Ruiz-Alma wrote: Is it possible to add these caps to tuplet numbers? ___ 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: [openlilylib] Discuss restructuring
Uns Liska wrote > I think that after an initial phase of trial & error we should > now do it right and create a structure we can live with for the future. Hi Urs, This is looking like an improvement to me. Here's a thought. If the emphasis is on include-ability, what about just having all the include files at the same level in the "Library" directory, without needing to categorize them by putting them in different directories by topic? Then you could just do \include "filename.ily" without having to remember what category directory a file is in. (Maybe stylesheets still gets a directory since they are a clear case of a different kind of file with a specific usage?) It seems the category directories are mainly for navigation purposes, i.e. for finding things, but could this be done (in a more flexible way) through tags and/or search? So a file can be tagged with more than one tag and you can see a list of the files for any given tag. I guess GitHub lends itself to organization by nested categories-by-directory rather than by a flat list with tags and search... So... one simple way to provide for navigation is to have a GitHub wiki page (or the main readme page?) that lists links to the files by category and/or tag, and use that for navigation. That has the advantage of giving you an overview of what's in each category/tag, on a single page, rather than having to open and close directories. (This could be maintained manually, but I suppose it could also be automated at some point.) In any case, I think having fewer and broader categories is generally better. Cheers, -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/openlilylib-Discuss-restructuring-tp163922p163950.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Issue on packed-spacing?
Well, of course this reminded me of \textLengthOff and \textLengthOn,
which normally serve to control this behaviour.
However, with packed-spacing, \textLengthOff has no effect at all, while
\textLengthOn slightly increases the spacing between notes, or basically
it seems to me that it increases padding after the text and before the
following note-column.
I used the following code:
\version "2.19.8"
\paper { ragged-rigth = ##t ragged-last = ##t }
\relative c' {
\override Score.SpacingSpanner.packed-spacing = ##t
%\textLengthOn
c8 c c-\markup { "some very very very very very very long text" } c c c
c c |
\repeat unfold 24 {c}
}
%%%
Best regards, Simon
Am 03.07.2014 12:20, schrieb Phil Holmes:
- Original Message - From: "Abel Cheung"
To:
Sent: Thursday, July 03, 2014 10:40 AM
Subject: Re: Issue on packed-spacing?
OK, maybe it's clearer to attach image.
On Thu, Jul 3, 2014 at 5:35 PM, Abel Cheung
wrote:
The artifact here is (forget the ragged-rigth typo), when using
packed-spacing, the whole note with markup is stretched horizontally
in an insane way to cope with the markup size, and I wonder if this is
the designed behavoir of lilypond.
On Thu, Jul 3, 2014 at 4:08 PM, Urs Liska wrote:
Am 03.07.2014 10:03, schrieb Abel Cheung:
Hi,
Is this the desired behavior of SpacingSpanner.packed-spacing ? (I'm
using 2.18.2)
\paper { ragged-rigth = ##t ragged-last = ##t }
\relative c' {
\override Score.SpacingSpanner #'packed-spacing = ##t
c8 c c-\markup{"some very very very very very very long text"}
c c c c
c |
\repeat unfold 24 {c}
}
Looks like a bug to me.
--
Phil Holmes
___
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: [openlilylib] Discuss restructuring
On Thu, Jul 3, 2014 at 1:06 AM, Urs Liska wrote: > Our repository has now lived for some time, and I think it is a good thing > to have and maintain. The recent renaming was partially intended to stress > its nature as an _includable_ library (as opposed to the official LSR). But > to make that work for a longer time and to make it scale with an increasing > amount of content I think we now need a fundamental restructuring of its > directory structure. One thing that would be useful is a way to define dependencies which would be automatically downloaded from some repository. Modern build systems do this (e.g. maven for java). This type of functionality is becoming standard with newer programming languages. I imagine something as simple as: = \library "lilyjazz" = At compile-time it would download the snippet or load it from its local cache. Even something which takes an extra step to request a download would still be useful. In this case the above would give a compile error until you do something like: $ install lilyjazz Of course it can get complicated (versioning, caching, etc.). Just a thought. -Jay ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Increase vertical spacing between systems
Hello Lilypond users,
I'm having a vertical spacing problem.
For a simple score (see [1]) I want to increase the vertical space
between stanza 2 and the next system (I've marked an occurence) just a
little bit.
I've looked into the documentation [2], but it doesn't seem to work.
What I don't want is to stretch the systems, like with
> \paper{
> ragged-last-bottom=##f
> }
Thanks in advance.
Hartmut
[1] https://www.dropbox.com/sh/f2rw614acsglg7i/AABvKYjtNB-1DbZo2LPA2l_Ta
[2]
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Vertical-spacing-between-systems#Vertical-spacing-between-systems
--
Hartmut Leister
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Increase vertical spacing between systems
Hi Hartmut,
2014-07-04 8:12 GMT+02:00 Hartmut Leister :
> I'm having a vertical spacing problem.
> For a simple score (see [1]) I want to increase the vertical space
> between stanza 2 and the next system (I've marked an occurence) just a
> little bit.
>
system-system-spacing #'basic-distance = #19
is probably what you're looking for.
\version "2.16.2"
#(set-global-staff-size 16)
\paper {
system-system-spacing #'basic-distance = #19
}
\score {
<<
\relative c' {
\repeat unfold 4 { c4 }
\repeat unfold 4 { d }
\repeat unfold 4 { e }
\repeat unfold 4 { f }
g4^"some extra space here"
\repeat unfold 3 { g }
\repeat unfold 4 { a }
\repeat unfold 4 { b }
\repeat unfold 4 { c }
\repeat unfold 4 { b }
\repeat unfold 4 { a }
\repeat unfold 4 { g }
\repeat unfold 4 { f }
\repeat unfold 4 { e }
\repeat unfold 4 { d }
\repeat unfold 4 { c }
}
\addlyrics {
\set stanza = "1."
\repeat unfold 64 bla
}
\addlyrics {
\set stanza = "2."
\repeat unfold 64 blubb
}
>>
\layout {
\context {
\Score
\remove "Bar_number_engraver"
}
indent = #0
}
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Increase vertical spacing between systems
On Fri, 4 Jul 2014, Hartmut Leister wrote: Hello Lilypond users, I'm having a vertical spacing problem. [2] http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Vertical-spacing-between-systems#Vertical-spacing-between-systems v2.12 is quite old. Vertical spacing syntax has been drastically reworked since then. http://www.lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables -- MT ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Increase vertical spacing between systems
On 04/07/14 07:50, Martin Tarenskeen wrote: > > > On Fri, 4 Jul 2014, Hartmut Leister wrote: > >> Hello Lilypond users, >> >> I'm having a vertical spacing problem. >> [2] >> http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Vertical-spacing-between-systems#Vertical-spacing-between-systems >> > > > v2.12 is quite old. Vertical spacing syntax has been drastically > reworked since then. > > http://www.lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables > > Oh gosh yes! I didn't notice you were referring to 2.12. There were huge changes in 2.14. Please upgrade to the latest stable and you will have much better control (and documentation) over spacing. http://lilypond.org/download.html Note you should also probably run the 'convert.ly' script (after you have installed the latest code) on any lilypond scores that you are using that are still being compiled by 2.12 to make sure that any significant syntax changes we have made in the code are detected and converted in your *.ly files. http://www.lilypond.org/doc/v2.18/Documentation/usage/updating-files-with-convert_002dly.html James ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
