Re: lyluatex: captions and page breaks

2018-05-17 Thread Federico Bruni
Il giorno gio 17 mag 2018 alle 9:00, Urs Liska ha scritto: Am 17.05.2018 um 08:54 schrieb Federico Bruni: Hi all As lyluatex does not support captions¹, so far I've used \header{piece="Caption"} in the lilypond snippet to display a title before the music fragment. I'm ok with the way

Re: Displace position of time signature

2018-05-17 Thread Aaron Hill
On 2018-05-17 19:05, Andrew Bernard wrote: Thank you very much. The next logical (or stupid?) question is, can one snug the notes under the time signature, as though it occupied no space? \version "2.19.81" { \override Staff.TimeSignature.Y-offset = #4 \override Staff.TimeSignatur

Re: Displace position of time signature

2018-05-17 Thread Karlin High
On Thu, May 17, 2018 at 9:05 PM, Andrew Bernard wrote: > The next logical (or stupid?) question is, can one snug > the notes under the time signature, as though it occupied no space? Intriguing. I found a lilypond-user thread from 2009 about imitating time signatures in markup.

Re: Displace position of time signature

2018-05-17 Thread Andrew Bernard
Hi Aaron, Thank you very much. The next logical (or stupid?) question is, can one snug the notes under the time signature, as though it occupied no space? Andrew On 18 May 2018 at 10:57, Aaron Hill wrote: > > > \version "2.19.81" > { \override Score.TimeSignature.Y-offset = #4 \time

Re: warning: no PostScript font name for font `/usr/local/share/fonts/100dpi/ncenB24-ISO8859-1.pcf.gz'

2018-05-17 Thread Jonathan Chen
On 18 May 2018 at 12:04, Aaron Hill wrote: > On 2018-05-17 15:29, Carl Sorensen wrote: >> >> On 5/17/18, 3:51 PM, "Jonathan Chen" wrote: >> I've just returned to using lilypond 2.18.2 after a break, and I now >> find if I compile any of my existing .ly files, I get a scree of >> erro

Re: Displace position of time signature

2018-05-17 Thread Aaron Hill
On 2018-05-17 17:53, Andrew Bernard wrote: Is it possible to have time signatures show above the barline, not inline in the staff? I'm aware there is a solution using a separate staff for time signatures, but I would rather not use that, as I do want them to sit very snug on top of the barli

Displace position of time signature

2018-05-17 Thread Andrew Bernard
Is it possible to have time signatures show above the barline, not inline in the staff? I'm aware there is a solution using a separate staff for time signatures, but I would rather not use that, as I do want them to sit very snug on top of the barline. Andrew _

Re: warning: no PostScript font name for font `/usr/local/share/fonts/100dpi/ncenB24-ISO8859-1.pcf.gz'

2018-05-17 Thread Aaron Hill
On 2018-05-17 15:29, Carl Sorensen wrote: On 5/17/18, 3:51 PM, "Jonathan Chen" wrote: I've just returned to using lilypond 2.18.2 after a break, and I now find if I compile any of my existing .ly files, I get a scree of errors, eg: What is your operating system? How are you runn

Re: Broken Hairpin

2018-05-17 Thread Thomas Morley
2018-05-17 15:47 GMT+02:00 foxfanfare : > Kieren MacMillan wrote >> Hi foxfanfare, >> >>> Is it possible to adjust the padding of a broken hairpin after a line >>> break? >> >> http://lilypond.org/doc/v2.18/Documentation/notation/modifying-broken-spanners >> >> Hope that helps! >> Kieren. >> __

Re: warning: no PostScript font name for font `/usr/local/share/fonts/100dpi/ncenB24-ISO8859-1.pcf.gz'

2018-05-17 Thread Carl Sorensen
On 5/17/18, 3:51 PM, "Jonathan Chen" wrote: Hi, I've just returned to using lilypond 2.18.2 after a break, and I now find if I compile any of my existing .ly files, I get a scree of errors, eg: What is your operating system? How are you running lilypond? I find your sam

Re: warning: no PostScript font name for font `/usr/local/share/fonts/100dpi/ncenB24-ISO8859-1.pcf.gz'

2018-05-17 Thread Jonathan Chen
On 18 May 2018 at 10:10, Simon Albrecht wrote: > On 17.05.2018 23:51, Jonathan Chen wrote: >> >> I've just returned to using lilypond 2.18.2 after a break, and I now >> find if I compile any of my existing .ly files, I get a scree of >> errors, > > > As always, it’s hard to help if you don’t give

Re: warning: no PostScript font name for font `/usr/local/share/fonts/100dpi/ncenB24-ISO8859-1.pcf.gz'

2018-05-17 Thread Simon Albrecht
On 17.05.2018 23:51, Jonathan Chen wrote: I've just returned to using lilypond 2.18.2 after a break, and I now find if I compile any of my existing .ly files, I get a scree of errors, As always, it’s hard to help if you don’t give a minimal example – often errors become apparent while distilli

warning: no PostScript font name for font `/usr/local/share/fonts/100dpi/ncenB24-ISO8859-1.pcf.gz'

2018-05-17 Thread Jonathan Chen
Hi, I've just returned to using lilypond 2.18.2 after a break, and I now find if I compile any of my existing .ly files, I get a scree of errors, eg: warning: no PostScript font name for font `/usr/local/share/fonts/100dpi/ncenB24-ISO8859-1.pcf.gz' warning: FreeType face has no PostScript font nam

Re: Vertical space above ossia

2018-05-17 Thread Ben
On 5/17/2018 3:08 PM, Carl Sorensen wrote: *From: *Ben *Date: *Thursday, May 17, 2018 at 8:38 AM *To: * *Subject: *Re: Vertical space above ossia On 5/17/2018 10:13 AM, Walter Garcia-Fontes wrote: But notice that there is additional space between the 3^rd line of the score and the fourth lin

Re: Solution to have repeats with upbeat and different alternatives??

2018-05-17 Thread Aaron Hill
On 2018-05-17 10:22, st...@linuxsuite.org wrote: I posted a piece of simplified code to illustrate. This is what the default does isnt 'it?? https://ln.sync.com/dl/2d42a9350/ukfaa7s8-rpenm7ne-xqxv7mpk-x99vbzbw [ . . . ] the code below prints an extraneous bar in the sec

Re: Vertical space above ossia

2018-05-17 Thread Carl Sorensen
From: Ben Date: Thursday, May 17, 2018 at 8:38 AM To: Subject: Re: Vertical space above ossia On 5/17/2018 10:13 AM, Walter Garcia-Fontes wrote: But notice that there is additional space between the 3rd line of the score and the fourth line of the score (to make room for the ossia). I thin

Re: Solution to have repeats with upbeat and different alternatives??

2018-05-17 Thread steve
> Hi Steve, > > Just going to chime in here, that I believe it will come out like the > latter version you prefer by default. > I am finished the basic engraving for 3 guitars, but can't get the repeats the way they should be. I posted a piece of simplified code to illustrate. Thi

Re: Solution to have repeats with upbeat and different alternatives??

2018-05-17 Thread Amy McGlothlin
Hi Steve, Just going to chime in here, that I believe it will come out like the latter version you prefer by default. Original is subjective here, some editor did that for some reason in the first example. That's not really standard practice. Have you started scoring it for guitars yet? Are you

Re: Solution to have repeats with upbeat and different alternatives??

2018-05-17 Thread steve
Well, I mean it appears that the same thing is scored differently. The first entrance has the upbeat before the repeat. If you look at this link of the first entrance with the downbeat a half note C flat in the third system https://ln.sync.com/dl/e80999780/f4ravrje-6gg923k6-id9vw4ub-4bc39f

Re: Solution to have repeats with upbeat and different alternatives??

2018-05-17 Thread Andrew Bernard
Hi Steve, I'm unclear what the problem is. Seems also easy. Can you show your code? I am also puzzled about you saying there are several ways to set the first part. Again, I cant see how one would do it differently to how I showed. This proves I don't know what you are referring to as your diffic

Re: Solution to have repeats with upbeat and different alternatives??

2018-05-17 Thread steve
> Hi Steve, > > Does this sketch help you out? Thanks, I am aware of that solution... and there are a couple of others... I am trying to render this second appearance of this after the trio. Here is a a page. The part I am interested in has the downbeat a C flat half note and

Re: Vertical space above ossia

2018-05-17 Thread Walter Garcia-Fontes
* Ben, soundsfromso...@gmail.com [17/05/18 17:04]: > In your original post, you mentioned that you wanted the ossia closer to the > below-staff, which the code earlier should help with. > > If you are talking about explicitly positioning a single staff in addition > to that, maybe you could try so

Re: Vertical space above ossia

2018-05-17 Thread Ben
In your original post, you mentioned that you wanted the ossia closer to the below-staff, which the code earlier should help with. If you are talking about explicitly positioning a single staff in addition to that, maybe you could try something from: http://lilypond.org/doc/v2.19/Documentatio

Re: Vertical space above ossia

2018-05-17 Thread Walter Garcia-Fontes
Sorry Ben, I answer with a photo. Actually the demand is both, to make the ossia closer to the below staff, and to reduce the distance with the above staff. But there is an unbreakable space above the ossia it seems, so the most it can be done is to increase the space between all staffs in the scor

Re: Vertical space above ossia

2018-05-17 Thread Walter Garcia-Fontes
* Ben, soundsfromso...@gmail.com [17/05/18 16:39]: > On 5/17/2018 10:13 AM, Walter Garcia-Fontes wrote: > > * Ben, soundsfromso...@gmail.com [17/05/18 15:52]: > > > On 5/17/2018 9:34 AM, Walter Garcia-Fontes wrote: > > > > * Ben, soundsfromso...@gmail.com [17/05/18 12:05]: > > > > > On 5/17/2018 2:

Re: Vertical space above ossia

2018-05-17 Thread Ben
On 5/17/2018 10:13 AM, Walter Garcia-Fontes wrote: * Ben, soundsfromso...@gmail.com [17/05/18 15:52]: On 5/17/2018 9:34 AM, Walter Garcia-Fontes wrote: * Ben, soundsfromso...@gmail.com [17/05/18 12:05]: On 5/17/2018 2:01 AM, Walter Garcia-Fontes wrote: I'm having trouble eliminating vertical

Re: Vertical space above ossia

2018-05-17 Thread Walter Garcia-Fontes
* Ben, soundsfromso...@gmail.com [17/05/18 15:52]: > On 5/17/2018 9:34 AM, Walter Garcia-Fontes wrote: > > * Ben, soundsfromso...@gmail.com [17/05/18 12:05]: > > > On 5/17/2018 2:01 AM, Walter Garcia-Fontes wrote: > > > > I'm having trouble eliminating vertical space above an Ossia > > > > snippet.

Re: Vertical space above ossia

2018-05-17 Thread Ben
On 5/17/2018 9:34 AM, Walter Garcia-Fontes wrote: * Ben, soundsfromso...@gmail.com [17/05/18 12:05]: On 5/17/2018 2:01 AM, Walter Garcia-Fontes wrote: I'm having trouble eliminating vertical space above an Ossia snippet. This is the example of the manual, augmented to extend over multiple lines

Re: Broken Hairpin

2018-05-17 Thread foxfanfare
Kieren MacMillan wrote > Hi foxfanfare, > >> Is it possible to adjust the padding of a broken hairpin after a line >> break? > > http://lilypond.org/doc/v2.18/Documentation/notation/modifying-broken-spanners > > Hope that helps! > Kieren. > > > Kieren MacMillan,

Re: Vertical space above ossia

2018-05-17 Thread Walter Garcia-Fontes
* Ben, soundsfromso...@gmail.com [17/05/18 12:05]: > On 5/17/2018 2:01 AM, Walter Garcia-Fontes wrote: > > I'm having trouble eliminating vertical space above an Ossia > > snippet. This is the example of the manual, augmented to extend over > > multiple lines: > > \version "2.19.32" \new Staff

Re: Solution to have repeats with upbeat and different alternatives??

2018-05-17 Thread Andrew Bernard
Hi Steve, Does this sketch help you out? Andrew \version "2.19.81" { \time 3/4 \key es \major \partial 4 bes8. ees'16 | ees'2 g'8. es'16 | \repeat volta 2 { es'4 d'4. es'8 | R1*3/4^\markup "etc" } \alternative { { g'4 f'8 bes'8\rest bes8. es'16 |

Re: Broken Hairpin

2018-05-17 Thread Kieren MacMillan
Hi foxfanfare, > Is it possible to adjust the padding of a broken hairpin after a line break? http://lilypond.org/doc/v2.18/Documentation/notation/modifying-broken-spanners Hope that helps! Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣

Broken Hairpin

2018-05-17 Thread foxfanfare
Hi, Is it possible to adjust the padding of a broken hairpin after a line break? For instance: \new PianoStaff << \relative c' { c4 d e f \break g f e d } \new Dynamics { \override PianoStaff.Hairpin.to-barline = ##f \override PianoStaff.Hairpin.after-line-breaking = ##

Re: tremolo

2018-05-17 Thread ptoye
You might also be interested in the thread at http://lilypond.1069038.n5.nabble.com/Fermatas-with-tremolos-td210054.html I see that your example had fermata signs over both notes. I personally prefer having a single fermata sign over the centre of the tremolo. All the best, Peter -- Sent from

Re: Maintaining font-size regardless of staff-size

2018-05-17 Thread David Kastrup
David Sumbler writes: > On Wed, 2018-05-16 at 16:55 +0200, David Kastrup wrote: >> David Sumbler writes: >> >> > >> > At the moment I define variables for formatting title, composer >> > etc. at >> > the start of a score separately for each staff-size that I use. >> > >> > A simple question:

Re: Vertical space above ossia

2018-05-17 Thread Ben
On 5/17/2018 2:01 AM, Walter Garcia-Fontes wrote: I'm having trouble eliminating vertical space above an Ossia snippet. This is the example of the manual, augmented to extend over multiple lines: The vertical distance above the ossia I could not reduce no matter how much I tweaked the numbers i

Re: Maintaining font-size regardless of staff-size

2018-05-17 Thread David Sumbler
On Wed, 2018-05-16 at 16:55 +0200, David Kastrup wrote: > David Sumbler writes: > > > > > At the moment I define variables for formatting title, composer > > etc. at > > the start of a score separately for each staff-size that I use. > > > > A simple question: is there a way of getting the same

Changing default \partcombine rest behaviour

2018-05-17 Thread Brent Annable
Hi all, I've just started using \partcombine, and have noticed that, by default, it doesn't print a rest in one part that coincides with a note of the same duration in the other part. I want it to print both the note and the rest. I know that I can use \partcombineApart to get around individual in

Re: lyluatex: captions and page breaks

2018-05-17 Thread Urs Liska
Am 17.05.2018 um 08:54 schrieb Federico Bruni: Hi all As lyluatex does not support captions¹, so far I've used \header{piece="Caption"} in the lilypond snippet to display a title before the music fragment. I'm ok with the way it looks. The problem is that sometimes this title is put just be