Lyric extenders and \skip

Hi. Please consider the following example. \version "2.19.15" << \relative { c' d e f } \addlyrics { a __ _ \skip 1 a } \relative { c' d e f } \addlyrics { a __ _ a a } \relative { c' d r f } \addlyrics { a __ _ \skip 1 } \relative { c' d r f } \addlyrics { a __ _ a } >> I would

Re: Smoothing out RepeatTie irregularities between chords?

Hi Trevor, No clue what's going on here... Here's a workaround (to be addapted to your needs): \version "2.19.17" \language "english" repeatTieExtend = #(define-music-function (parser location arg-repeat-tie-extend) (number?) #{ -\tweak X-extent #(cons (* (+ arg-repeat-tie-extend 4) -1)

Re: Bad extent estimation causing too much vertical spacing

Hello Peter, as a last resort there’s , but that means hard-coding, of course, which loses flexibility. HTH, Simon Am 17.04.2015 um 00:15 schrieb Peter Bašista: Hi LilyPond users, I would like to ask a question about the

Re: \compoundMeter

Hi Tobias, Well, difficult to say without a tiny example. Maybe go for the v.2.19.18 Cheers, Pierre 2015-04-14 20:14 GMT+02:00 Tobias Hagedorn : > I need some help with „compoundMeter“ > When i compile my Staff in the lilypondversion 2.19.15, then the > compoundMeter is shown like this: 2 + 3 + 3

Re: Lyric extenders and \skip

Dear Davide, Am 17.04.2015 um 09:40 schrieb Davide Liessi: > How can I achieve the desired result, i.e. a melisma with lyric extender > line followed by a note with no syllable and no extender line? How about this: \relative { c' d r f } \addlyrics { a __ _ "" } Cheers, Joram _

Re: \compoundMeter

Hi Tobias, do you really require the \compoundMeter or is it simply the way you chose to define the beat structure of the measure? How about this: \version "2.19.15" \score { \relative { \time 11/16 \set Timing.beatStructure = #'(2 3 3 3) c'16 d e c d e c d e f e } \layout {

Re: Lyric extenders and \skip

Dear Joram, Il 17/04/15 09.52, Noeck ha scritto: \relative { c' d r f } \addlyrics { a __ _ "" } thanks, this does what I want. I didn't try with "" before posting my question, but I did try with " ". Why are the following staves different? \version "2.19.15" << \relative { c' d r f } \a

Re: Make plus sign of compoundMeter bolder

Hi Calixte, How about (after: http://lsr.di.unimi.it/LSR/Item?id=782) : \version "2.18.2" %% \version "2.19.18" #(define ((time-parenthesized-time up down upp downp) grob) (grob-interpret-markup grob (markup #:override '(baseline-skip . 0) #:number (#:line ( (#:column (

Re: Survey: Large scores

Hi, Am Donnerstag, den 16. April 2015 um 19:43:38 Uhr (+0200) schrieb Urs Liska: > ... I'd like to know what might be the biggest score anyone has > successfully created with LilyPond. the biggest score so far for me is a piece for big orchestra, 6 soloists, live-electronics and fixed media from

undefined

Hi everyone! Traditionally, vocal scores are written without beams, except for melisma. But modern scores tend to keep beams everywhere and put slurs to indicate melisma. Is it possible to have both output with one source, without complicating the typesetting? I have this in mind : vocal = \rela

Re: Bad extent estimation causing too much vertical spacing

Hi Simon, I will definitely try that, thanks for the tip. But I agree it is more like a hard-coding workaround than an actual solution. Peter On Apr 17, 2015 9:42 AM, "Simon Albrecht" wrote: > Hello Peter, > > as a last resort there’s >

Re: undefined

Am Freitag, den 17. April 2015 um 11:05:00 Uhr (+0200) schrieb Calixte Faure: > Hi everyone! > > Traditionally, vocal scores are written without beams, except for melisma. > But modern scores tend to keep beams everywhere and put slurs to indicate > melisma. > > Is it possible to have both output

Re: (hypothetical) Availability of LilyPond engravers

Hi Urs, I’m self-employed and always in need of paid projects, and I love to work with LilyPond since more than 10 years. But usually I do only lead sheets or songbooks - you know what I can or cannot do, and that I can learn quickly under (your) good advise. ;) Greetlings, Hraban ___

Re: undefined

Am 17.04.2015 um 11:15 schrieb Orm Finnendahl: Am Freitag, den 17. April 2015 um 11:05:00 Uhr (+0200) schrieb Calixte Faure: Hi everyone! Traditionally, vocal scores are written without beams, except for melisma. But modern scores tend to keep beams everywhere and put slurs to indicate melism

Re: Make plus sign of compoundMeter bolder

Hi Pierre, Perfect, thanks a lot! Cheers, Calixte. 2015-04-17 10:36 GMT+02:00 Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com>: > Hi Calixte, > > How about (after: http://lsr.di.unimi.it/LSR/Item?id=782) : > > \version "2.18.2" > %% \version "2.19.18" > > #(define ((time-parenthesized

Re: Bad extent estimation causing too much vertical spacing

Peter, you wrote Thursday, April 16, 2015 11:15 PM > > I would like to ask a question about the vertical spacing in a rather > long score ... > > I believe the attached sample can be typeset on 4 pages. But LilyPond > by default uses 6 pages > > But ... I believe ... > LilyPond should be clev

Re: undefined

Hi Calixte, it should be possible to create an engraver that solves this. The following things to keep in mind for that: You can set the properties, which trigger melismas \set melismaBusyProperties = #'(melismaBusy slurMelismaBusy tieMelismaBusy beamMelismaBusy) If slurMelismaBusy and beamMelis

Re: Bad extent estimation causing too much vertical spacing

Hi Trevor, Thank you for the suggestions! I am definitely going to try that. Peter On Apr 17, 2015 12:13 PM, "Trevor Daniels" wrote: > > Peter, you wrote Thursday, April 16, 2015 11:15 PM > > > > I would like to ask a question about the vertical spacing in a rather > > long score ... > > > > I

Do we really offer the future?

Just one more of the fundamental questions I took home from the Musikmesse ... The question can be asked somewhat less pretentious then in this message's subject line, but I think it actually boils down to no less than that. You know that I have again been at the Frankfurt Musikmesse this we

Re: Smoothing out RepeatTie irregularities between chords?

Hi, > 2015-04-16 3:36 GMT+02:00 Trevor Bača : > >> Hi, >> >> Using the \shape command to length repeat ties works great between notes. >> But weird behavior seems to arise with lengthened repeat ties between >> chords: >> >> >> ### BEGIN ### >> >> \version "2.19.17" >> \language "english" >> >> >

Re: undefined

Hi Calixte, someone has made a cool snippet for that: http://lsr.di.unimi.it/LSR/Item?id=968 He's simply re-defining the [ ] commands. A little modification to fill your needs: % - "[" = - #(make-music 'SlurEvent 'span-direction -

Re: Do we really offer the future?

Hi Urs, First off, thank you so much for your continuing efforts on behalf of Lilypond. They are really important, and no doubt time- and energy-consuming for you, with little promise of immediate benefit to you personally. The ‘Pond appreciates you! > "why should a publishing house use LilyPo

Re: (hypothetical) Availability of LilyPond engravers

Hi Urs (et al.), > In any projects not all contributors have to be proficient with all aspects, > particularly not with beautifying the final output. Agreed. > Nevertheless people should be able to provide their input without requiring > too much hand-holding and without producing an inappropr

Re: Re: Introducing some 'path' drawing tools

Thanks for the compliment Ming! Cheers, Pierre 2015-04-16 17:33 GMT+02:00 MING TSANG : > > Wow, very nice and I like it. Thank you Pierre! > Immanuel, > Ming > > > > > On Thursday, April 16, 2015 2:56 AM, "lilypond-user-requ...@gnu.org" < > lilypond-user-requ...@gnu.org> wrote: > > 5. Re:Int

256th notes (was: How to define a non existing grob)

Dear List, Please find hereunder the snippet I'd like to upload on the LSR - with bad workarounds!! Two major issues: 1. 'warning: rest `rests.8' not found': LP print the grob but cannot affect any dimension to it 2. I cannot find any working 'Flag.stencil', probably also - or part of - because f

Re: undefined

> On Apr 17, 2015, at 5:05 AM, Calixte Faure wrote: > > and a magic command (say \beamToSlur) would switch [ ] to ( ). Hi Calixte, Here’s a music function for this. Seems to do the trick, but untested on actual music. HTH, -Paul % \version "2.18.2" beamsToSlurs = #(define-music-

Re: Do we really offer the future?

Hi. On Fri, 17 Apr 2015 15:03:19 +0200, Urs Liska wrote: Just one more of the fundamental questions I took home from the Musikmesse ... The question can be asked somewhat less pretentious then in this message's subject line, but I think it actually boils down to no less than that. To whom Lil

Re: undefined

Hi all, Thanks for all this solutions! Of course using a script with sed would do the work, but like Urs, I prefer keeping input file unmodified. Therefore the snippet solution of Klaus is not the best, because we can’t use variables properly: the "[" and "]" redefinition has to be before any \inc

Jianpu Notation

Hello! I am a Java developer and music amateur from China who is familiar with both 5-staff notation and Jianpu (aka numberic) notation used for all pitched Chinese instruments. I have seen post discussed about displaying Jianpu notation in Lilypond years ago, and would like to help developing

Re: undefined

On Fri, Apr 17, 2015 at 10:06 AM, Calixte Faure wrote: > Hi all, > > Thanks for all this solutions! > Of course using a script with sed would do the work, but like Urs, I > prefer keeping input file unmodified. > Therefore the snippet solution of Klaus is not the best, because we can’t > use vari

Re: \compoundMeter

Hi Tobias, it is recommended to always reply to the list, because others might be interested in the follow-up messages or (in this case) to let others know that the question is answered. Cheers, Joram Am 17.04.2015 um 13:03 schrieb Tobias Hagedorn: > Thank you very much! That’s what i wanted to

Re: undefined

> On Apr 17, 2015, at 12:57 PM, David Nalesnik wrote: > > Nice function! I think you also need to set types to reflect the change to a > slur. Good catch! Looks like there’s also a ‘spanner-id property on slurs, so I added that too for good measure. Also a little code simplification. Thank

Re: (hypothetical) Availability of LilyPond engravers

Am 17.04.2015 um 16:10 schrieb Kieren MacMillan: Hi Urs (et al.), In any projects not all contributors have to be proficient with all aspects, particularly not with beautifying the final output. Agreed. Yes, and that is an important point when you are promoting the feature of "clustering"

Re: Survey: Large scores

On Fri, Apr 17, 2015 at 10:51:41AM +0200, Orm Finnendahl wrote: [...] > The only really painful part was the partcombiner which seems very > buggy, but was indispensable as I needed to save as much vertical > space as possible. Yeah, I've run into quite a number of \partcombine myself. Most of it

Re: Survey: Large scores

On Fri, Apr 17, 2015 at 11:44:57AM -0700, H. S. Teoh wrote: > On Fri, Apr 17, 2015 at 10:51:41AM +0200, Orm Finnendahl wrote: > [...] > > The only really painful part was the partcombiner which seems very > > buggy, but was indispensable as I needed to save as much vertical > > space as possible. >

Re: Survey: Large scores

On Thu, Apr 16, 2015 at 1:43 PM, Urs Liska wrote: > I'd like to know what might be the biggest score anyone has successfully > created with LilyPond. > > Not exactly a single score, but I've been working on a transcription/transposition of the Bartok violin duets for my personal use. Each duet (o

Re: (hypothetical) Availability of LilyPond engravers

> note->articulation->dynamic->slur->beam->tie note->articulation->beam->slur->dynamic->tie please ;) just kidding – but coding style has to come with coding-style discussions ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/

Re: Survey: Large scores

Am 17.04.2015 um 20:44 schrieb H. S. Teoh: On Fri, Apr 17, 2015 at 10:51:41AM +0200, Orm Finnendahl wrote: [...] The only really painful part was the partcombiner which seems very buggy, but was indispensable as I needed to save as much vertical space as possible. Yeah, I've run into quite a n

Re: (hypothetical) Availability of LilyPond engravers

Am 17.04.2015 um 21:05 schrieb Noeck: note->articulation->dynamic->slur->beam->tie note->articulation->beam->slur->dynamic->tie please ;) just kidding – but coding style has to come with coding-style discussions Yes, of course. And we decided not to be too strict about it for the project.

Re: Jianpu Notation

Hi David, I've absolutely no clue what kind of music you're talking about. I've seen than Ming (pretty active on the list) has already started some discussion about it. In any case I'd follow you just by curiosity! Cheers, Pierre 2015-04-17 8:53 GMT+02:00 Super-User : > Hello! > > I am a Java d

Re: Survey: Large scores

On Fri, Apr 17, 2015 at 09:12:50PM +0200, Urs Liska wrote: > Am 17.04.2015 um 20:44 schrieb H. S. Teoh: [...] > >More annoying is the fact that \partcombine often gets confused when > >the two voices have very divergent rhythms -- crescendo hairpins > >don't merge, dynamics get printed twice, > >

Re: Windows performance

Phil Holmes wrote Thursday, April 16, 2015 3:43 PM > > From: "Trevor Daniels" > Sent: Thursday, April 16, 2015 3:28 PM >> >> Phil Holmes wrote Thursday, April 16, 2015 2:00 PM >> >>> The performance of LilyPond 2.19.18 on Windows is _much_ better than >>> previous versions. Some examples: >>> >>

Re: Jianpu Notation

Super-User qq.com> writes: > I am a Java developer and music amateur from China who is familiar > with both 5-staff notation and Jianpu (aka numberic) notation used for > all pitched Chinese instruments. I have seen post discussed about > displaying Jianpu notation in Lilypond years ago, and woul

Re: Windows performance

Hi Phil, The point I am making is that you need to reboot the machine between version runs, to equalize matters such as disk block caching. If you run 2.19.16 and then 2.19.18 the latter may be using cached data from the former, such as shared DLL’s already loaded and so on. Now that you have

Re: (hypothetical) Availability of LilyPond engravers

Urs, With a distributed group project it seems to me that people must know git in order to cooperate successfully, but I tend to find git is hard for people to learn if they are not software developers and accustomed to such things. The lack of knowledge of git caused large difficulties on a di

ChordNames vs. \numericTimeSignature: used to be OK, not now

*sigh* Most of the time, LilyPond is amazing. Other times... I have an old document, a lead sheet, following basically the form an excerpt [A]. This prints out as I would expect: a single staff with melody, lyrics below and chord names above the staff. I have a new document, following almost ex

Re:notes do not show up in v2.19.18

Sorry, I include the wrong v2.19.18 pdf.  Here is the right one.Immanuel,Ming test_2.19.18_god's-magnificent-love.pdf Description: Adobe PDF document ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-use

Re: Jianpu Notation

Hello David, > On Apr 17, 2015, at 2:53 AM, Super-User wrote: > Recently, I have tried to implement a small subset of Jianpu on Lilypond, in > ugly programming style, as attached in this email. I would like to hear more > from the Lilypond community about how to implement the Jianpu support bet

Re: (hypothetical) Availability of LilyPond engravers

Hi Andrew, thank you for your thoughts. Am 18. April 2015 03:56:59 MESZ, schrieb Andrew Bernard : >Urs, > >With a distributed group project it seems to me that people must know >git in order to cooperate successfully, but I tend to find git is hard >for people to learn if they are not software