Re: time signature is printed after first bar line

Am 20.09.2016 um 17:28 schrieb Roderick Mackenzie: I am still trying to print bagpipe tunes with Lilypond, with a repeat bar at the start of each part. I am almost there; my only problem now is that the time signature is printed after the first bar line (the repeat bar line). How do I get the

Re: Initial clef change in piano score

Am 15.09.2016 um 21:46 schrieb Simon Albrecht: if in a piano score the right hand begins in bass clef, it is customary to write a treble clef first and change to bass clef after the time signature, presumably to draw more attention. Is there any more elegant way than this kind of fake in

Re: Please help with Lilypond calling Scheme

Am 20.09.2016 um 19:12 schrieb PMA: (define (colorNote n) (cond ((eq? (- n) 1) 'red ) ((eq? (- n) 2) 'blue))) This returns the symbol 'red or the symbol 'blue, not the constant named red (value (1.0 0.0 0.0)) or the constant named blue. \override NoteHead.font-size =

Re: moving notes in cue-voice must not influence dot after notehead in main voice

Am 16.09.2016 um 13:37 schrieb Knut Petersen: Hi everybody! I used << \new Voice {\voiceTwo e'4. 8 4} \new CueVoice { \voiceOne \override NoteColumn.force-hshift = 0.4a,4. \override NoteColumn.force-hshift = 1.2 8

Re: \abs-(font)size for \epsfile

Am 16.09.2016 um 11:53 schrieb Pierre Perol-Schneider: Hi Malte, Here is an old thread regarding a similar demand: http://lilypond.1069038.n5.nabble.com/Absolute-size-for-epsfile-i-e-independent-of-global-staff-size-td161872.html HTH, Pierre Thanks Pierre for the hint and Marc for the

Re: Keep alive together - call for use cases

Am 18.08.2016 um 15:10 schrieb David Kastrup: Malte Meyn <lilyp...@maltemeyn.de> writes: Am 18.08.2016 um 14:16 schrieb Mark Knoop: Could you both take a look at this and see (a) if it helps, and (b) what else needs to be achieved. I didn’t read the whole thread but how t

Re: Keep alive together - call for use cases

Am 18.08.2016 um 14:16 schrieb Mark Knoop: Could you both take a look at this and see (a) if it helps, and (b) what else needs to be achieved. I didn’t read the whole thread but how to deal with different clefs? For example, in a choir a tenor is notated with \clef "treble_8" but a

Re: Dynamic marks and vertical space

Am 27.08.2016 um 01:24 schrieb Timofey Misarenkov: (DynamicText.extra-offset can help to move, but vertical space waste remains the same. And using same approach to move \p and hairpin do not helps either.) extra-offset only moves the visual appearance of a grob but doesn’t affect spacing

Re: Switching to drummode and back

Am 26.08.2016 um 11:40 schrieb Malte Meyn: \version "2.18.2" \new Staff \with { \accepts DrumStaff } { \repeat unfold 8 {e''8} \drums { I forgot \once \omit DrumStaff.TimeSignature here. hh4. r4. hh4 % else an additional clef would be printed \

Re: Switching to drummode and back

Am 26.08.2016 um 11:32 schrieb Sven Hillebrand: \version "2.18.2" { \repeat unfold 8 {e''8} \drummode { \clef percussion hh4. r4. hh4. } \clef bass d1 } Is there a way to make it look like the original in the attachment? Displaying percussion music in \drummode needs a

Re: Alternative bar numbering [0.18571]

Pleae always reply to the list (at least as CC) so others can see when your problem is solved or new questions arise ;) Am 25.08.2016 um 22:39 schrieb Pastor Neubauer: Is there any way to not have the first line indent? Yes: replace line 10 (“indent = #10”) by “indent = #0”. You can also

Re: Alternative bar numbering [0.18571]

Oh, and because you mentioned time savers: You don’t have to write the duration of every note. If you don’t write the duration the last duration is repeated. So c4 d4 e4 r4 f8 e8 f4 is the same as c4 d e r f8 e f4 Am 25.08.2016 um 23:00 schrieb Malte Meyn: Pleae always reply to the list

Re: Alternative bar numbering [0.18571]

Am 25.08.2016 um 21:12 schrieb Pastor Neubauer: I am not using score blocks. I never really trained in on Lilypond, just sort of started finding what worked so I am going line by line using addlyrics. I know I have had some difficulties that could be worked out if I used more “formal”

Re: crossStaff beaming not connecting both staves

Am 27.09.2016 um 23:05 schrieb Ryan Michael: The problem is the stem does not connect the two staves. Here is the complete piece: Are you serious? 290 lines of code producing a three page score? Please always give a minimal working example and include a version statement. This time I made

Re: crossStaff beaming not connecting both staves

Am 28.09.2016 um 00:01 schrieb Malte Meyn: \version "2.19.47" \new PianoStaff \with { \consists #Span_stem_engraver } << \new Staff { a\harmonic } \new Staff { \crossStaff a } This looks like a Span_stem_engraver bug to me: The NoteHeads don’t share a stem because

Re: Grob name for part combine texts?

Am 28.09.2016 um 11:03 schrieb Simon Albrecht: I need to tweak (offset) the text(s) produced by the partcombiner, e.g. "Solo" What grob do I need to tweak? CombineTextScript (found in the list at the bottom of http://lilypond.org/doc/v2.18/Documentation/internals/text_002dinterface)

Re: Pitched Trill Collision

Am 30.09.2016 um 15:47 schrieb dtsmarin: How can I move the pitched trill note so that the ledger lines aren't connected? Try using a version ≤ 2.19.40. This shouldn't happen at all. You have to change the engraving rules for this specific notation. This is a bug which was introduced

Re: Pitched Trill Collision

Am 30.09.2016 um 19:56 schrieb dtsmarin: Unfortunately I can't downgrade to an older version because some files won't compile at all. Which features of 2.19.41–48 do need? Maybe there’s an alternative so you can use 2.19.40. ___ lilypond-user

Re: Pitched Trill Collision

Am 01.10.2016 um 18:39 schrieb Paul: Thanks for the bug report. I posted a comment on the issue here: https://sourceforge.net/p/testlilyissues/issues/4979/#b111 This comment says: When two ledger lines are at the same vertical position, in the same note column, (as I assume is probably

Re: need help

Am 06.11.2016 um 11:25 schrieb David Sumbler: How do I find out what changes have been made between (for instance) 2.19.48 and 2.19.49? You could read the commit messages in the git log: http://git.savannah.gnu.org/cgit/lilypond.git/log/ ___

Re: Jazz Chord Symbols

Am 06.11.2016 um 15:41 schrieb jasonsilver: This is great- but how do I use it for sharp notes in chords? For example, I get how to do something like c:1.2.3.5 but don't know how to a chord like Cmin7#5 I don’t find the message you answered to but maybe you are looking for something like

Re: basic question regarding \drummode

Am 04.11.2016 um 23:15 schrieb Tobin Chodos: What's the best way to handle a percussion part that has a lot of pitched and un-pitched material? You could have a “pitched” Staff accept not only “pitched” Voices but also DrumVoices: \version "2.18.2" \new Staff \with { \accepts DrumVoice

Re: need help

Am 04.11.2016 um 22:11 schrieb Peter Lavetti: Processing `/Users/peterlavetti/Desktop/Untitled.ly' Parsing... /Users/peterlavetti/Desktop/Untitled.ly:1: warning: no \version statement found, please add \version "2.18.2" for future compatibility Success: compilation successfully completed

Re: Adding a barline at the start of a new line

Am 09.11.2016 um 22:27 schrieb Malte Meyn: c'1 c c c \bar "|" \break Oh, of course you don’t need \bar "|" here as "|" is the default barline type. ___ lilypond-user mailing list lilypond-user@gnu.org https://

Re: Adding a barline at the start of a new line

Am 09.11.2016 um 21:50 schrieb hbezemer: I want LP to create a barline at the beginning of every new line, but so far I can't find the right way to do so. You can use the define-bar-line command. It takes four arguments: 1. name/default barline 2. barline at end of line 3. barline at begin

Re: Adding a barline at the start of a new line

Am 09.11.2016 um 22:27 schrieb Malte Meyn: #(define-bar-line "|" "|" "|" "|") #(define-bar-line "||" "||" "||" "||") You might also want #(define-bar-line ":|." ":|." "|" &quo

Re: ties in volta / alternatives

Am 23.10.2016 um 10:11 schrieb bart deruyter: I was wondering if this issue really isn't solved yet after 6 years. If so, I can't find anything in the documentation, or I must have missed it. This is issue 2884: https://sourceforge.net/p/testlilyissues/issues/2884/ It really isn’t solved

Re: Server error?

Am 19.10.2016 um 18:59 schrieb Jan-Peter Voigt: http://lsr.di.unimi.it/LSR/Search This annoying dead-link came somehow, somewhere into the net ... This link hasn’t always been dead: Some years ago the computer science department of the University of Milano changed it’s name/abbreviation

Re: Alternative subtleties

Am 28.11.2016 um 08:44 schrieb Menu Jacques: Hello folks, I’ve always used \alternative with a list of bracketed elements, and just found that example in the Notation Reference: […] % to be compared with this: { \accidentalStyle modern \time 2/4 \repeat volta 2 { c'2 }

Re: PianoStaff.shortinstrumentName

Am 28.11.2016 um 10:20 schrieb Robert Blackstone: \set PianoStaff.shortinstrumentName = "B. C." It has to be shortInstrumentName (with a capital I). ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Setting the number for \mark \default

Am 16.11.2016 um 08:08 schrieb Johan Vromans: Still as someone familiar with ASCII control codes, I would expect #20 to yield T, not U. But that's because the 'I' is missing in the sequence. This is because LilyPond uses #format-mark-letters as default (“letters”: A to Z but without I,

Re: alternative notehead style breaks cross-staff stem

Am 13.11.2016 um 15:45 schrieb Urs Liska: I'm trying to build something like similar to an automated harmonic display on two staves, and it seems that alternative note head styles break the cross staff stems: Is this known (at least not said in the NR)? Is there a way around this issue? I

Re: Setting the number for \mark \default

Am 14.11.2016 um 09:52 schrieb Mojca Miklavec: I'm using \markDefault from the following code for marking parts of music: stdMarkFormat = { \set Score.markFormatter = #format-mark-box-letters } markDefault = { \stdMarkFormat \mark \default } Why do you use these functions? A \set is

Re: beams in treble and bass staff

Am 14.01.2017 um 11:07 schrieb Gianmaria Lari: > Novice question. Attached it's a small music fragment from an harpe > score. How can I write it using lilypond? You have to name your staffs and then use the \change command. \version "2.19.53" \new PianoStaff << \new Staff = "upper"

Re: Faking a time signature

Am 13.01.2017 um 14:29 schrieb Menu Jacques: > Hello folks, > > In a Canzon by Gabrieli, we have 4/2 time written as slashed C: > \time sets timeSignatureFraction and measureLength. So you can either use time and set one of these context properties or you set both of them and don’t need

Re: Find out denominator of current time signature

Am 11.01.2017 um 14:00 schrieb Thomas Weber: > Dear all, > > I wonder how I can create a duration that is so to say exactly one time > signature denominator long (e.g. an eigth in 6/8, a quarter in 4/4 > etc.). I thought something like this would work: You can get the duration from the

Re: Removing Barlines

Am 14.01.2017 um 18:16 schrieb Amir Teymuri: > i am a new lilypond user. How can i hide / remove barlines completely? > When i set \override Score.BarLine in each upper and lower staffes of a > piano staff only the line on the systems will be overriden but not the > line between upper and lower

Re: How to merge two scores into one?

Am 05.01.2017 um 22:45 schrieb Jeff Epstein: > I'm not understanding how to merge two scores into one. The song just > continues, but it's a different section with a different voice configuration. > The first section has a single voice, the second has two. The only way I can > figure it out

Re: Changing midi-tempo within score

Am 07.01.2017 um 23:34 schrieb UCas: > I am able to set midi-tempo in my header-file with > > \midi { > \context { > \Score tempoWholesPerMinute = #(ly:make-moment miditempo 4) > } > } > > but how can I change this tempo within the score? \set

Re: Problem with partcombine and shape notes

Am 31.12.2016 um 11:55 schrieb Phil Holmes: I think it's documented in http://lilypond.org/doc/v2.19/Documentation/notation/multiple-voices#automatic-part-combining You’re right. (I didn’t notice that my browser chose the german translation which hasn’t included this change yet.) However it

Re: Problem with partcombine and shape notes

Am 31.12.2016 um 10:57 schrieb Malte Meyn: By the way: what’s this optional \partcombine argument introduced in 2.19? I haven’t found any documentation. Found it. It’s an two year old addition that has been documented only in appendix A.18 of the NR (which seems to be generated directly

Re: Problem with partcombine and shape notes

Am 30.12.2016 um 07:27 schrieb Bumby Hymnal: I've run into a problem with using \partcombine while using \aikenHeads. The problem is that under certain circumstances the aiken shape note heads are not used in the output of \partcombine. The strange thing is that it sometimes works.

\relative { \time 3/4 a' d b c2 \bar "|." }

___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: French tablature?

Am 29.12.2016 um 23:15 schrieb Alasdair McAndrew: Is it likely that Lilypond will provide such tablature at some stage? Currently, if I want to typeset tablature, I need to use different software. LilyPond already supports this type of tablature: You have to set the tablatureFormat to

Re: French tablature?

Am 30.12.2016 um 05:16 schrieb Alasdair McAndrew: Many thanks! I didn't know about RhythmicStaff. Is this all possible in version 2.18.2 (which I'm using)? Not everything is possible: the additionalBassStrings property has been added in 2.19; so 2.18.2 won’t support this.

Re: French tablature?

Am 30.12.2016 um 09:09 schrieb Alasdair McAndrew: I tried it without the RhythmicStaff, just to see what the tablature looks like. However, the tablature is written on the lines, rather than between them. I suppose this could be tweaked by moving all the letters up by half the distance

Re: French tablature?

Am 30.12.2016 um 09:27 schrieb Malte Meyn: Then you can add the following code to the \layout-\context-\TabStaff block (f. e. after setting tablatureFormat): \override TabNoteHead.before-line-breaking = #(lambda (grob) (ly:grob-set-property! grob 'Y-offset

Re: Strange error

Am 18.12.2016 um 18:03 schrieb Br. Samuel Springuel: When I compile the following snippet I get an error under 2.19.53 that wasn't there under 2.18.2: \version "2.19.53" timeless = \with { \remove "Time_signature_engraver" } \new Staff \with { \remove "Time_signature_engraver" } {

Re: Change augmentation dot size

Am 23.12.2016 um 17:19 schrieb liang seng: My questions is, is there a way to change the size of augmentation dots to make it bigger or smaller? Yes, there is: \version "2.18.2" { c'4. \override Dots.font-size = 3 c' } The default font-size is 0, negative values give smaller dots,

Re: tweak the position of arpeggio

Am 22.03.2017 um 08:50 schrieb Jinsong Zhao: > In the following code, you may see the arpeggio is far away the notes. > My question is how to make it close to the notes? Thanks in advance. How about \once \override PianoStaff.Arpeggio.padding = -1 ?

The End. [Was: Parallel Square Premusic]

Am 22.03.2017 um 11:07 schrieb Urs Liska: > Indeed, I think those last remarks of the OP seem to be bringing this > discussion to an end. Otherwise we might end up engaging in something > like the infamous "maclaren" episode ... I think we can agree on this. One good thing happened in this

Re: LSR down?

Am 26.03.2017 um 07:21 schrieb Andrew Bernard: > Is LSR down for others? Not for me: http://lsr.di.unimi.it/LSR/Search (Probably you know already that dsi.unimi.it changed to di.unimi.it some years ago; but there are old links pointing to the old domain in mail archives etc.)

Re: LSR down?

> On 03/26/17 08:48, Malte Meyn wrote: >> >> >> Am 26.03.2017 um 07:21 schrieb Andrew Bernard: >>> Is LSR down for others? >> >> Not for me: http://lsr.di.unimi.it/LSR/Search (Probably you know already >> that dsi.unimi.it changed to di.unimi.it so

Re: Make dots in repeat barline smaller

Am 26.03.2017 um 09:13 schrieb Andrew Bernard: > When using a smaller staff size than the default, how do you make the > double dots in a repeat barline smaller also? These dots come from the music font, so try \override Staff.Barline.font-size = 6 (negative values for smaller than

Re: Is it possible \quoteDuring from a different position?

Am 25.03.2017 um 02:23 schrieb caag...@gmail.com: > For example, quoting the start of the music when you are a few measures in? You could use several \addQuotes. But this needs one for every shift, so maybe it’s not the best solution. \version "2.19.56" foo = \relative { c' d e f g2 g

Re: LSR down?

Am 27.03.2017 um 02:30 schrieb Andrew Bernard: > LSR still down as at 0030 UTC here in Australia. > > Andrew No time zone problems here so http://lsr.di.unimi.it/LSR/Snippet?id=1007 shows up correctly but the search gives no results: http://lsr.di.unimi.it/LSR/Search?q=notehead

Re: Unclear doc?

Am 29.03.2017 um 08:41 schrieb Menu Jacques: > Hello folks, > > In appendix A.17 of the LPNR v2.19.57, what doest the « No setting… » > sentence mean? > > alternativeNumberingStyle (symbol) > The style of an alternative’s bar numbers. Can be numbers for going back > to the same number or

Re: Unexpected Stem behaviour

Hi Gerard, please try to make minimal examples that are easier to understand (http://lilypond.org/tiny-examples.html). These long lines and tons of {} and <<>> aren’t easy to read. Am 31.03.2017 um 11:55 schrieb Gerard: > 1. The stems in red do not match the coding, length should be 8 in stead >

Re: Unexpected Stem behaviour

Am 31.03.2017 um 12:27 schrieb Malte Meyn: > The tie is attached to the note head you attached it to—but this note > head is transparent. If you don’t use \hideNotes you can see that. The > two note heads are printed side by side to prevent collision; you can > turn that

Re: How to force script (articulation custom function) inside staff ?

Am 31.03.2017 um 11:48 schrieb Les Éditions Valmajour - pg: > Dear list members, > I have to use lots of dots and dashes in a score, so I found a snippet > to apply an articulation > (staccato) function to a long passage. I tried to adapt it for another

Re: inconsistent bar number placement

Am 17.03.2017 um 21:47 schrieb Juan Cristóbal Cerrillo: > the barnumber in measures 5, 6, 9 and 10 in the following example are placed > so differently as the other bar numbers. Cannot reproduce any inconsistencies. Are you sure you’re using LilyPond 2.18.2?

Re: Partial

Am 17.03.2017 um 21:08 schrieb Joseph Austin: > First of all, although I did not see it in the documentation, > the form \partial DUR*NUM, such as \partial 8*5, seems to work, where NUM is > an integer multiplying DUR. > This seems to be sufficient to accommodate any arbitrary anacrusis, >

Re: inconsistent bar number placement

Am 17.03.2017 um 22:54 schrieb Juan Cristóbal Cerrillo: > Yes, my version is 2.18.2 > This is what the top of page 3 looks like with ragged-right and > ragged-bottom ##t The code you posted doesn’t contain these settings. > Are you not seeing the same? No, even if I add \paper {

Re: What can Premusic do that others can't?

Am 20.03.2017 um 22:48 schrieb have@anti.capital: > These are the first measures of Beethoven's Fifth in premusic. This is missing tempo, fermatas and dynamics. ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Parallel Square Premusic

Am 20.03.2017 um 02:11 schrieb have@anti.capital: > I have invented an extremely robust and perfectly extensible plaintext file > format called Parallel Squares. This sounds very promising, let’s do a partial fact check. > premusic (I use this word to describe instructions for how to play music,

Re: What can Premusic do that others can't?

Am 21.03.2017 um 06:46 schrieb have@anti.capital: > A composer who uses an irrational tuplet is a composer who is going out of > his way to exclude his music from comfortable notation. Oh, I think that these irrational tuplets are comfortable to write easy to understand if you use traditional

Re: What can Premusic do that others can't?

Am 20.03.2017 um 22:48 schrieb have@anti.capital: > MusicXML […] but it is an unwise solution here. As you mentioned several times, you’re not a programmer so probably others know a little better about how to store music in a way that programs can easily read. > ABC […] lacks the perfect and

Re: Scaled grace

Am 21.03.2017 um 11:44 schrieb Malte Meyn: > Or if you don’t want variants for all \grace variants (i. e. \grace, > \slashedGrace, \appoggiatura, \acciaccatura, \afterGrace), just make a > function that takes a music expression and scales it to 1. Maybe this > could also be nice for

Re: Scaled grace

Am 21.03.2017 um 11:04 schrieb Urs Liska: > > > Am 21.03.2017 um 10:46 schrieb Malte Meyn: >> (By the way: I think that the way LilyPond handles it (using “grace” and >> “real time”) is pretty good but not perfect. \grace only needs grace >> time but \afterGrace n

Re: What can Premusic do that others can't?

Am 21.03.2017 um 10:18 schrieb Hans Åberg: > >> On 21 Mar 2017, at 00:40, Werner LEMBERG wrote: >> >>> As an example of what David is mentioning, have a look at the attached >>> png image (taken from Chopin's prelude op. 28/24) and try to notate >>> this. >> >> Oops, wrong image.

Re: MIssing semi-sharp, semi-flat , sesqui-sharp, and sesqui-flat names in some languages in LPNR 2.19.56

Am 20.03.2017 um 11:38 schrieb Menu Jacques: > I’ve noticed that only the following languages: > > nederlands deutsch english espanol or espa~nol français italiano > portugues > > are mentioned at page 9 regarding: > > semi-sharp semi-flat sesqui-sharp sesqui-flat > >

Re: Parallel Square Premusic

Please always reply to the messages you are actually quoting/referring to so mail clients and archives put the mails in the thread in correct order. Am 22.03.2017 um 02:10 schrieb have@anti.capital: > I'm not sure how the octave of a pitch is ambiguous?? Scientific pitch > notation is pretty

Re: new to this list - converting from Noteworthy Composer

Am 22.03.2017 um 09:52 schrieb Guido van Harten: > Hi, > > I think I am new to this list. A few years ago I tried Lilypond to > create my music files. It failed, but I do not remember why. > > As of today I will give it a new try. Now I am starting of my current > music notation software,

Re: Converting a large project from 2.18 to 2.19: what to expect?

Am 05.04.2017 um 09:15 schrieb Shevek: > In terms of Scheme changes, how does this affect compatibility with snippets > written on 2.16 or 2.18? Most notable change is the change in definition of music function changes: #(define-music-function (parser location arg1 arg2) (type1? type2?) …)

Re: Specify output directory *in* the file

Am 05.04.2017 um 11:19 schrieb Urs Liska: > Hi all, > > is it possible to specify an output directory from within the LilyPond > file without going through the hoops of ly:book-process? > > TIA > Urs How about \bookOutputName? This works with absolute paths like \bookOutputName

Re: "natural width" of a measure

Am 11.04.2017 um 20:36 schrieb Urs Liska: > So, is there any moment in the compilation process where the natural, > unstretched length of a measure can be calculated? It doesn't have to be > an easily-read property and can involve calculation, but actually the x > position of the barlines would

Re: German User Forum down

Am 01.04.2017 um 06:51 schrieb Manuela Gößnitzer: > Hi, > > does anybody know anything about the German forum? The page is down since > yesterday, the site says "End of life". I am really sad because this forum > is very valuable for me, > greetings > Manuela Hi Manuela, fugenkomponist from

Re: German User Forum down

Am 01.04.2017 um 10:42 schrieb Manuela: > Hi Malte, > > I really do hope this is a joke (not a good one), if not, we can get a > backup of our threads. I would participate in the costs of a new forum, > greetings, > Manuela Maybe it’s not a joke but also not the end of the forum. Might be a

Re: Slurs within chords, within tuplets -- seem to be ignored (without warnings!)

Am 12.04.2017 um 11:17 schrieb Phil Holmes: > Without actually trying this out, it seems to me that the reason is > likely to be that your slur markings are inside chord notation. Try > putting them outside the chords and see if that helps. You’re right (slurs work but not phrasing slurs; also

Re: Incipit default notehead.style

Am 05.04.2017 um 20:06 schrieb Johannes Roeßler: > Hi, > > I'd like to have an incipit with modern notation styles in 2.19 - but > what ever I do - I get neomensural noteheads./ > /I tried to place \override NoteHead.style = #'default or \override > Staff.NoteHead.style = #'default several

Re: lilypond errors on a guitar minor sixth chord

Am 15.04.2017 um 02:36 schrieb Stan Mulder: > Thanks for the clarification on the reply-all. I wasn't sure what to do. > Is there some place on the web were I can see other discussions? There are several archives, f. e. http://lists.gnu.org/archive/html/lilypond-user/ (this is the mailing

Re: Last number on a score; but this is the first in the next one...

Am 15.04.2017 um 15:40 schrieb Son_V: >> And a solution > > Sorry but I wasn't able to find it, surely, my fault. I tried some of your > code without success. I'm using version "2.18.2" on Linux. Maybe try all code, not some code ;) ___

Re: Last number on a score; but this is the first in the next one...

Am 15.04.2017 um 15:47 schrieb Son_V: >> \override Score.BarNumber.break-visibility = #end-of-line-invisible > > Thanks! That was successful. > > But I'm still in doubt of what should be the correct way. There is no single correct way. In classical music traditionally you have bar numbers

Re: flip clef at end of line only

Am 15.04.2017 um 17:32 schrieb Marc Hohl: > Hi list, > > I am working on a little piece that's played as written; > after that, the musician has to turn the page upside down and play the > resulting notes. > > I managed to get the clef displayed at the beginning and the end of each > line, and

Re: Last number on a score; but this is the first in the next one...

Am 15.04.2017 um 13:54 schrieb Son_V: > Hi all, Lilypond (using \override Score.BarNumber #'break-visibility = #'#(#t > #t #t) ) writes at the end of a score, the number of the next beam, that is > written at the beginning of the subsequent score; and it writes at the end > of the last score the

Re: Forcing a downward line at the end of a second time bar marking

Am 13.04.2017 um 12:13 schrieb Richard Shann: > can the second time bar be made to look like the first time bar, being > "finished off" with a downward verstical stroke at the double barline? This is done automagically for some bar types like "|." and ":|." but not for "||". But I cannot find

Re: Tuplet bracket

Am 14.04.2017 um 06:45 schrieb Andrew Bernard: > Hi Michiel, > > Use shorten-pait to taste. > > %\once \override TupletBracket.positions = #'(3.1 . 3.4) > \once \override TupletBracket.shorten-pair = #'(0 . 0.5) Shouldn’t this be #'(0.2 . 0) or similar but not #'(0 . 0.5)

Minimal examples (was: Last number on a score; but this is the first in the next one...)

Am 15.04.2017 um 14:30 schrieb Son_V: > I'm not able to make a truly "minimum example", that's what I could do: I’ll show you how this can be simplified. > \version "2.18.2" > \header { > } You don’t need an empty \header, \paper, \layout, … block. > PartPOneVoiceOne = \relative a' { >

Re: Key signatures repeated on every staff

Am 15.04.2017 um 16:41 schrieb Son_V: > I dare to try a minimal example! :-) > But I hope it's self-explaining. \version "2.18.2" { \key d \major R1*20 } That’s not too hard ;) But yes, it’s self-explaining this time. > On my scores, the key signature appears on every

Re: flip clef at end of line only

Am 15.04.2017 um 21:34 schrieb Marc Hohl: > Thanks a lot! Just for clarification: after-line-breaking seems to work > here, too – is there a special reason to use before-line-breaking? No. I thought I had tried it with after-line-breaking first without success but maybe I made another mistake.

Re: \repeatTie on a single note in a chord

Am 09.03.2017 um 17:07 schrieb Mojca Miklavec: > How can one add "\repeatTie" that only works on a single note in a chord? > > Example where I would only want to add the tie just to "f": > […] > 2 \repeatTie r4 | I think 2 should do what you want. But

Re: \repeatTie on a single note in a chord

Am 09.03.2017 um 17:35 schrieb Mojca Miklavec: > Should I file a bug report? I think so. Minimal example could look like this (I use \displayMusic to show that the RepeatTieEvent is there): \version "2.19.56" \displayMusic ___ lilypond-user

Re: \repeatTie on a single note in a chord

Am 09.03.2017 um 22:25 schrieb Thomas Morley: > > Another possibility to fake it: > > { > \override LaissezVibrerTie.head-direction = #RIGHT > < b d'^\laissezVibrer > > } This looks like the source of the bug should be easily found. LaissezVibrerTies and RepeatTies are basically the same

Re: Klammern und verkleinerte Noten

Am 09.03.2017 um 09:59 schrieb Bernhard Kleine: > The problem is with the spacing of the grace notes. Being not a > programmer I do not find enough information in the 2.9.56 manual to do > it by myself: The spacing of parentheses to the graces and the distance > of the grace notes to the notes

Re: Problem with bar numbers

Am 14.03.2017 um 09:11 schrieb Don Gingrich: > OK, I'll start by saying that I'm doing some things that > are wrong as far as musical purists are concerned, > but there *is* a reason. > > […] > > So it breaks the rules of music theory, but there is > a reason. If I understand correctly: No,

Re: Problem with bar numbers

Am 14.03.2017 um 11:35 schrieb David Kastrup: >> Maybe you should use a newer (“unstable”/development version); 2.19.xx >> allows \partial after the start of a piece and handles bar numbers >> correctly. The development versions aren’t unstable in the sense that >> they will crash or damage your

Re: Problem with bar numbers

Am 14.03.2017 um 11:30 schrieb Andrew Bernard: > I had a look into this for Don. The partial after a repeat throws a new > bar number, although it should not. Is there a way to control this, or > is it a defect? I don’t really understand what you mean. Which LilyPond version did you use? Which

Re: Starting with Lilypond - First Error

Am 13.03.2017 um 22:04 schrieb David Kastrup: > Scoutladen - Ralph Fröhlich writes: > >> Hi everybody, >> >> I try to use Lilypond in our Mediawiki for collection songs for group >> of children (like boyscouts...). >> >> Try to set up the first song with a given .ly I get

Re: function/macro for "on the fly" dynamics+text

Am 04.03.2017 um 22:59 schrieb Kieren MacMillan: > Many scores use dynamics like “pp sub.” or “f dolce” etc. In order to build > such a grob as a DynamicText, I use the following: > […] > 1. I have to define a macro for every single combination in every score. For > ppSub and the like, which

Re: placement of clef before break

Am 08.03.2017 um 08:43 schrieb Juan Cristóbal Cerrillo: > In the following example, I would like to be able to place the clef after the > repeat barline, and the time signature in parenthesis. Time signature in parentheses: http://lsr.di.unimi.it/LSR/Item?id=734 For the order of Grobs at the

<    1   2   3   4   5   6   7   8   >