Re: Positioning of a tiny voice

2020-02-07 Thread David Kastrup
Kieren MacMillan writes: > Hi Joram, > >> the following works for me: >> \new Staff << >> { \oneVoice \music } \\ { \voiceThree \shiftOff \upper } >> > > Glad you found a solution! > >> Why did you use \voices 1,2 in your example? > > Bad coding… Here’s a better snippet (including your

Re: Positioning of a tiny voice

2020-02-07 Thread David Kastrup
Noeck writes: > Hi, > > I would like to add small notes into an already populated staff. > It is the right hand of a piano staff and I don’t want real voices with > their shifts. The tiny font size distinguishes the "upper" voice > already. It should have the least impact possible on the "music"

Re: Positioning of a tiny voice

2020-02-07 Thread Kieren MacMillan
Hi Joram, > the following works for me: > \new Staff << > { \oneVoice \music } \\ { \voiceThree \shiftOff \upper } >> Glad you found a solution! > Why did you use \voices 1,2 in your example? Bad coding… Here’s a better snippet (including your \oneVoice fix): %%% \version "2.19.83" upper =

Re: Positioning of a tiny voice

2020-02-07 Thread Noeck
> Does this workaround/hack suit your needs? Hi Kieren, unfortunately not, because the "music" voice should behave like a \oneVoice. But the following works for me: \new Staff << { \oneVoice \music } \\ { \voiceThree \shiftOff \upper } >> Why did you use \voices 1,2 in your example? And I’d

Re: Positioning of a tiny voice

2020-02-07 Thread Kieren MacMillan
Hi Joram, > How to move the b'' exactly on top of the chord below? > What to do about this warning? Does this workaround/hack suit your needs? %%% \version "2.19.83" upper = \relative { \tiny \stemUp s4 b'' } music = \relative { \key e \minor \time 2/4 b'8 16 c' 8 16 b' } \new Staff {

Positioning of a tiny voice

2020-02-07 Thread Noeck
Hi, I would like to add small notes into an already populated staff. It is the right hand of a piano staff and I don’t want real voices with their shifts. The tiny font size distinguishes the "upper" voice already. It should have the least impact possible on the "music" voice. Here is one

Re: Page numbers with text

2020-02-07 Thread Noeck
… and if you want this footer on every page, you can have it shorter: oddFooterMarkup = \markup \fill-line { \line { \fromproperty #'page:page-number-string "–" \fromproperty #'header:title } } Best, Joram

Re: Page numbers with text

2020-02-07 Thread Noeck
Dear Marco, is this close to what you want? %% \version "2.19.84" \paper { print-first-page-number = ##t oddHeaderMarkup = \markup \null evenHeaderMarkup = \markup \null oddFooterMarkup = \markup \fill-line { \line { \on-the-fly

Re: Page numbers with text

2020-02-07 Thread Kevin Barry
On Fri, Feb 07, 2020 at 09:06:19PM +0100, Marco Bagolin wrote: > My knowledge of lilypond is not good enough... > I tried to understand the examples in the guide of lilypond but the chapter > is not clear enough for me. > I am in difficult... Hi Marco, If you add the code below to your score,

Re: Page numbers with text

2020-02-07 Thread Marco Bagolin
My knowledge of lilypond is not good enough... I tried to understand the examples in the guide of lilypond but the chapter is not clear enough for me. I am in difficult... Please someone can help me?  Thank you all Il giorno ven 7 feb 2020 alle 07:11 Aaron Hill ha scritto: > On 2020-02-06

Re: can a Scheme engraver "solve" Issue #34 (grace note bug)? [cross-posted]

2020-02-07 Thread Thomas Morley
Am Fr., 7. Feb. 2020 um 14:46 Uhr schrieb Kieren MacMillan : > > Hi all, > > Here’s the brainstorm I’ve currently got going: > > Issue #34, a.k.a. the grace note bug, is one of Lilypond’s longest-standing > and most newbie-unfriendly issues. It doesn’t appear in single-staff scores, > obviously

Re: can a Scheme engraver "solve" Issue #34 (grace note bug)? [cross-posted]

2020-02-07 Thread David Kastrup
Kieren MacMillan writes: > Hi all, > > Here’s the brainstorm I’ve currently got going: > > Issue #34, a.k.a. the grace note bug, is one of Lilypond’s > longest-standing and most newbie-unfriendly issues. It doesn’t appear > in single-staff scores, obviously — only in multi-staff scores where >

can a Scheme engraver "solve" Issue #34 (grace note bug)? [cross-posted]

2020-02-07 Thread Kieren MacMillan
Hi all, Here’s the brainstorm I’ve currently got going: Issue #34, a.k.a. the grace note bug, is one of Lilypond’s longest-standing and most newbie-unfriendly issues. It doesn’t appear in single-staff scores, obviously — only in multi-staff scores where one staff has a grace note [in the note

Re: Typing error in the 2.19.84 documentation

2020-02-07 Thread David Kastrup
Bernhard Kleine writes: > I noted on the page > http://lilypond.org/doc/v2.19/Documentation/notation/paper-size-and-automatic-scaling#index-Papierformat > >> \paper { >> #(set-paper-size "tabliod") >> } > Should that not be "tabloid"? > Fixed in master already. Looks like I need to do one

Re: Spacing grobs with an invisible object between them (hack)

2020-02-07 Thread Paolo Prete
On Fri, Feb 7, 2020 at 4:28 AM Aaron Hill wrote: > I have applied this logic to your code and made some changes [1]. > > [1]: http://lilybin.com/bt0t2d/11 > > That's great, Aaron! Now we have a very robust method for *easy* spacing *complex* vertical layouts. I would not even consider this a

Typing error in the 2.19.84 documentation

2020-02-07 Thread Bernhard Kleine
I noted on the page http://lilypond.org/doc/v2.19/Documentation/notation/paper-size-and-automatic-scaling#index-Papierformat > \paper { > #(set-paper-size "tabliod") > } Should that not be "tabloid"? Kind regards Bernhard -- spitzhalde9 D-79853 lenzkirch bernhard.kle...@gmx.net

Set up label in add-toc-item!

2020-02-07 Thread Robert Kubosz
Hello! I have a question that bothers me. Can I put a label in a markup function/add-toc-item! ? I'll explain: I have scores, that obviously use a \header {} block. I use a custom scoreTitleMarkup, that obviously manages each piece's title markup and also calls add-toc-item! that puts an item