Re: Bass and Treble Clef notes on the same clef

[Janek Warchoł]

2014-10-17 0:58 GMT+02:00 David Kastrup :
> Knute Snortum  writes:
>
>> I have a situation I don't know how to deal with in LilyPond. I have
>> bass clef and treble clef notes on the same staff. I guess one way to
>> do it is to create a markup and a small bass clef sign and put it next
>> to the treble clef (and incorrect) gf which looks like a tied bf from
>> the bass clef in the first measure. I could make a temporary
>> ossia-type staff to hold the bf pedal tone.
>>
>> Any other thoughts?
>
> \new Staff \with { \accepts "Staff" }
> {
>   \partial 2
>   \clef bass
>   <<
> \new Voice
> { \voiceOne r8 \clef treble  
>   ~ q4 }
> \new Staff \with { createSpacing = ##f }
> { \voiceTwo bes,,2~
>   \once\override Staff.CueClef.Y-offset = #-4 \cueClef bass
>   bes,,2 }
>   >>
> }

!  This really works! 8O

LilyPond is awesome.  I knew it.
Janek

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

Re: how to avoid barre and fingerboard shift in fret-diagram? [SOLVED]

[MarcM]

Through this snippet
https://github.com/stevage/Lilypond/blob/master/Documentation/snippets/fret-diagrams-explained-and-developed.ly

and this doc :
http://lilypond.org/doc/v2.18/Documentation/notation/instrument-specific-markup

I found out the function in the LSR http://lsr.di.unimi.it/LSR/Item?id=790
appends  '(place-fret) to the (string fret) pairs and thus does not support
the syntax to indicate open strings. "(open 4)"

I changed the original function in the LSR to fix that and it works. 

% Expand the (string fret) pairs to valid lilypond syntax
% ORIGINAL
#(define (fret-from-list l1 l2 n1)
   (if  (null? l1) 
l2 
(fret-from-list (cdr l1) (append l2 (list (append '(place-fret) (car
l1) (inverted (length l2) n1 n1)))

% MODIFIED
% to allow to use other syntax of the fret-diagram syntax.
%  the function accepts (string fret) pairs and i added a test to check if
the first element of a 
% (string fret) pair is a number append '(place-fret) otherwise just return
the list

#(define (fret-from-list source target n1)
   (if  (null? source)
target
(fret-from-list
   (cdr source)
   (append target (list
  (if (integer? (car (car source)))
  (append '(place-fret) (car source)
(inverted (length target) n1))
  (car source)
   )
   ); list
)
   n1)))



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/how-to-avoid-barre-and-fingerboard-shift-in-fret-diagram-tp167595p167630.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: Bass and Treble Clef notes on the same clef

[David Kastrup]

Knute Snortum  writes:

> I have a situation I don't know how to deal with in LilyPond. I have
> bass clef and treble clef notes on the same staff. I guess one way to
> do it is to create a markup and a small bass clef sign and put it next
> to the treble clef (and incorrect) gf which looks like a tied bf from
> the bass clef in the first measure. I could make a temporary
> ossia-type staff to hold the bf pedal tone.
>
> Any other thoughts? 

\new Staff \with { \accepts "Staff" }
{
  \partial 2
  \clef bass
  <<
\new Voice
{ \voiceOne r8 \clef treble  
  ~ q4 }
\new Staff \with { createSpacing = ##f }
{ \voiceTwo bes,,2~
  \once\override Staff.CueClef.Y-offset = #-4 \cueClef bass
  bes,,2 }
  >>
}

-- 
David Kastrup


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

Re: Bass and Treble Clef notes on the same clef

[Tim Reeves]

My first thought is...that's a really bad idea. 
But maybe there is some reason to do it that I had not considered...



Tim



From:   lilypond-user-requ...@gnu.org
To: lilypond-user@gnu.org
Date:   10/16/2014 01:32 PM
Subject:lilypond-user Digest, Vol 143, Issue 103
Sent by:lilypond-user-bounces+tim.reeves=tokamerica@gnu.org



Send lilypond-user mailing list submissions to
 lilypond-user@gnu.org

To subscribe or unsubscribe via the World Wide Web, visit
 https://lists.gnu.org/mailman/listinfo/lilypond-user
or, via email, send a message with subject or body 'help' to
 lilypond-user-requ...@gnu.org

You can reach the person managing the list at
 lilypond-user-ow...@gnu.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of lilypond-user digest..."


Today's Topics:

   1. Bass and Treble Clef notes on the same clef (Knute Snortum)


--

Message: 1
Date: Thu, 16 Oct 2014 13:32:19 -0700
From: Knute Snortum 
To: lilypond-user@gnu.org
Subject: Bass and Treble Clef notes on the same clef
Message-ID:
 
Content-Type: text/plain; charset="utf-8"

I have a situation I don't know how to deal with in LilyPond.  I have bass
clef and treble clef notes on the same staff.  I guess one way to do it is
to create a markup and a small bass clef sign and put it next to the 
treble
clef (and incorrect) gf which looks like a tied bf from the bass clef in
the first measure.  I could make a temporary ossia-type staff to hold the
bf pedal tone.

Any other thoughts?


[image: Inline image 1]

Knute Snortum
(via Gmail)


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

Re: suppressing header info in bookparts

[Flaming Hakama by Elaine]

On Tue, Oct 14, 2014 at 8:56 PM, Helge Kruse  wrote:

> Hello Flaming Hakama,
>
> I did this with a small piece of Scheme.
>
> %% Bookpart first page and last page predicates
> #(define (not-part-first-page layout props arg)
>(if (= (chain-assoc-get 'page:page-number props -1)
>   (ly:output-def-lookup layout 'first-page-number))
>empty-stencil
>(interpret-markup layout props arg)))
>
> \paper {
> print-page-number = ##t
> print-first-page-number = ##f
> oddHeaderMarkup = \markup {
> \on-the-fly #print-page-number-check-first
> \fill-line {
> \on-the-fly #not-part-first-page \fromproperty #'header:poet
> \line {
> \titleLeft
> \titleKern
> \emDash
> \pageNumberKern
> \lower #0.55 \fontsize #6 \fromproperty
> #'page:page-number-string
> \pageNumberKern
> \emDash
> \titleKern
> \titleRight
> }
> \on-the-fly #not-part-first-page \fromproperty
> #'header:composer
> }
> }
> evenHeaderMarkup = \oddHeaderMarkup
> oddFooterMarkup = \markup { \fill-line { \fromproperty
> #'header:copyright } }
> evenFooterMarkup = \oddFooterMarkup
> }
>
> Regards Helge
>
>
Helge,

Thanks for this scheme approach.
After hunting around to figure out how it works a bit (like to understand
chain-assoc-get),
this seems similar to what's in share/lilypond/current/scm/titling.scm
Always good to learn new things.

On the other hand, I realized that what I want in the running headers is
pretty static,
so I can use regular variables for those.

And then I found in the normal documentation the way to suppress printing
of the normal header fields:
http://www.lilypond.org/doc/v2.19/Documentation/notation/creating-titles-headers-and-footers

\bookpart {
\header {
title = ##f
piece = \markup { \fontsize #4 "Doha - Chaubola - Daud" }
composer = ##f
arranger = ##f
}
}

This brings me to two font questions:

1) Modify the base font size
I chose a (roman) font I like, but overall it is too small, everywhere it
is used.
Is there a way to pump up the size everywhere, globally, and keep any
existing relative proportions intact?

2) Modify the size of header fields.
For example, I would like the 'piece' field to be a larger font.
In the above example, I accomplish this on a one-time basis.
Is there a way to modify the definition so that all 'piece' headers use
such a custom font/size?

Thanks,

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

Re: Bass and Treble Clef notes on the same clef

[Malte Meyn]

Have a look at http://lsr.di.unimi.it/LSR/Item?id=326

Am 16.10.2014 um 22:32 schrieb Knute Snortum:

I have a situation I don't know how to deal with in LilyPond.  I have bass
clef and treble clef notes on the same staff.  I guess one way to do it is
to create a markup and a small bass clef sign and put it next to the treble
clef (and incorrect) gf which looks like a tied bf from the bass clef in
the first measure.  I could make a temporary ossia-type staff to hold the
bf pedal tone.

Any other thoughts?


[image: Inline image 1]

Knute Snortum
(via Gmail)



___
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

Bass and Treble Clef notes on the same clef

[Knute Snortum]

I have a situation I don't know how to deal with in LilyPond.  I have bass
clef and treble clef notes on the same staff.  I guess one way to do it is
to create a markup and a small bass clef sign and put it next to the treble
clef (and incorrect) gf which looks like a tied bf from the bass clef in
the first measure.  I could make a temporary ossia-type staff to hold the
bf pedal tone.

Any other thoughts?


[image: Inline image 1]

Knute Snortum
(via Gmail)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Centering text in a TextSpanner or OttavaSpanner (or ...?)

[David Nalesnik]

On Tue, Oct 7, 2014 at 3:11 AM, Jacques Menu  wrote:

> Hello David,
>
> Thanks a lot for this solution: it works for me since I have only one bar
> to span over, with LP 2.18.2 by the way.
>
>
Turns out it wasn't too hard to get the ability to span multiple bars.

I kept the same stencil function, but I wrote a new engraver based on the
regression test scheme-text-spanner.ly.

I didn't create a new grob; so you'll need to get used to the idea of using
overrides of MeasureCounter properties and \startMeasureCount,
\stopMeasureCount.  An actual grob could come later.

The way of changing the text could be made a lot more convenient, of course.

Anyway, it's more of a proof-of-concept.

Let me know if you run into any problems with it.

Enjoy!
David
\version "2.19.15"


\header {
  tagline = ##f
}

#(define (test-stencil grob text)
   (let* ((orig (ly:grob-original grob))
  (siblings (ly:spanner-broken-into orig)) ; have we been split?
  (refp (ly:grob-system grob))
  (left-bound (ly:spanner-bound grob LEFT))
  (right-bound (ly:spanner-bound grob RIGHT))
  (elts-L (ly:grob-array->list (ly:grob-object left-bound 'elements)))
  (elts-R (ly:grob-array->list (ly:grob-object right-bound 'elements)))
  (break-alignment-L
   (filter
(lambda (elt) (grob::has-interface elt 'break-alignment-interface))
elts-L))
  (break-alignment-R
   (filter
(lambda (elt) (grob::has-interface elt 'break-alignment-interface))
elts-R))
  (break-alignment-L-ext (ly:grob-extent (car break-alignment-L) refp X))
  (break-alignment-R-ext (ly:grob-extent (car break-alignment-R) refp X))
  (num
   (markup text))
  (num
   (if (or (null? siblings)
   (eq? grob (car siblings)))
   num
   (make-parenthesize-markup num)))
  (num (grob-interpret-markup grob num))
  (num-stil-ext-X (ly:stencil-extent num X))
  (num-stil-ext-Y (ly:stencil-extent num Y))
  (num (ly:stencil-aligned-to num X CENTER))
  (num
   (ly:stencil-translate-axis
num
(+ (interval-length break-alignment-L-ext)
  (* 0.5
(- (car break-alignment-R-ext)
  (cdr break-alignment-L-ext
X))
  (bracket-L
   (markup
#:path
0.1 ; line-thickness
`((moveto 0.5 ,(* 0.5 (interval-length num-stil-ext-Y)))
  (lineto ,(* 0.5
 (- (car break-alignment-R-ext)
   (cdr break-alignment-L-ext)
   (interval-length num-stil-ext-X)))
,(* 0.5 (interval-length num-stil-ext-Y)))
  (closepath)
  (rlineto 0.0
,(if (or (null? siblings) (eq? grob (car siblings)))
 -1.0 0.0)
  (bracket-R
   (markup
#:path
0.1
`((moveto ,(* 0.5
 (- (car break-alignment-R-ext)
   (cdr break-alignment-L-ext)
   (interval-length num-stil-ext-X)))
,(* 0.5 (interval-length num-stil-ext-Y)))
  (lineto 0.5
,(* 0.5 (interval-length num-stil-ext-Y)))
  (closepath)
  (rlineto 0.0
,(if (or (null? siblings) (eq? grob (last siblings)))
 -1.0 0.0)
  (bracket-L (grob-interpret-markup grob bracket-L))
  (bracket-R (grob-interpret-markup grob bracket-R))
  (num (ly:stencil-combine-at-edge num X LEFT bracket-L 0.4))
  (num (ly:stencil-combine-at-edge num X RIGHT bracket-R 0.4)))
 num))

#(define (add-bound-item spanner item)
   (if (null? (ly:spanner-bound spanner LEFT))
   (ly:spanner-set-bound! spanner LEFT item)
   (ly:spanner-set-bound! spanner RIGHT item)))

#(define-public (Measure_attached_spanner_engraver context)
   (let ((span '())
 (finished '())
 (event-start '())
 (event-stop '()))
 (make-engraver
  (listeners ((measure-counter-event engraver event)
  (if (= START (ly:event-property event 'span-direction))
  (set! event-start event)
  (set! event-stop event
  ((process-music trans)
   (if (ly:stream-event? event-stop)
   (if (null? span)
   (ly:warning "You're trying to end a measure-attached spanner but you haven't started one.")
   (begin (set! finished span)
 (ly:engraver-announce-end-grob trans finished event-start)
 (set! span '())
 (set! event-stop '()
   (if (ly:stream-event? event-start)
   (begin (set! span (ly:engraver-make-grob trans 'MeasureCounter event-start))
 (set! event-start '()
  ((st

Re: Using greek letters breaks latin glyphs in markup

[Warp_7]

On Thu, Oct 16, 2014 at 06:18:25AM +0200, Werner LEMBERG wrote:
> 
> > It boils down to this: if I use greek letters in a \markup, the
> > corresponding latin character (alpha -> a, gamma -> g, etc.) is
> > rendered differently – it appears not smooth, but more pixelated.
> > Please see the attached screenshot from Okular in which the greek α,
> > χ and ε have an influence on a, c and e, respectively.
> 
> I think this is a ghostscript issue, fixed in the latest release,
> 9.15.
> 
>   http://bugs.ghostscript.com/show_bug.cgi?id=695259
> 
> Look especially at comment #10.

Great, you are right. I built ghostscript 9.15 and the bug is gone. Thank
you.


Reading that bug page had me encounter a crash in konqueror that I spent
half an hour debugging so I could report it. Sometimes, being a nerd is very
cumbersome.
-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me with any Facebook service.

Feed your children with garlic, then you will find them in the dark.


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

Re: A sign I can't understand ...

[Urs Liska]

Am 16.10.2014 13:59, schrieb Janek Warchoł:

2014-10-16 13:49 GMT+02:00 Son_V :

isn't that indicating that in a second (or later) verse there are two

syllables?

Yes. Sorry ... I've been too stingy. :-)

Here is a larger view:



Note that the "comma" on the right should be a breath


the notation of your image would be wrong

I suppose it too; but what should be the correct way to write this "thing"?
Sorry but when I encounter these strange situations I'm not able to find a
reference in the manual. It seems to me to try to find a needle in an
haystack.

You could either use temporary polyphony, possibly with making second
voice smaller

\new Staff {
   \time 2/4
   f'8 a'
   << { \voiceOne g'4 } \new CueVoice { \voiceTwo g'8 8 } >>
}

or a dashed tie

\new Staff {
   \time 2/4
   f'8 a'
   \tieDashed
   g'8 ~ 8
}

Personally i prefer the second solution, especially that it's easier
to get lyrics to work with it.


The "standard" way is to do it the first way. At least that's what 
publishers of classical and romantic vocal music do.


Urs



best,
Janek

___
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: A sign I can't understand ...

[Larry Kent]

Thanks for the more complete picture.  I don't know how you do this in
Lilypond, but I think the proper notation is to write two eighth notes and
use a dotted tie (indicating that for one verse it's tied (i.e. a quarter
note) and for the other verse, it's two separate eighth notes.

LK

On Thu, Oct 16, 2014 at 7:49 AM, Son_V  wrote:

> > isn't that indicating that in a second (or later) verse there are two
> syllables?
>
> Yes. Sorry ... I've been too stingy. :-)
>
> Here is a larger view:
>
> 
>
> Note that the "comma" on the right should be a breath
>
> > the notation of your image would be wrong
>
> I suppose it too; but what should be the correct way to write this "thing"?
> Sorry but when I encounter these strange situations I'm not able to find a
> reference in the manual. It seems to me to try to find a needle in an
> haystack.
>
> Thanks.
>
>
>
> --
> View this message in context:
> http://lilypond.1069038.n5.nabble.com/A-sign-I-can-t-understand-tp167597p167616.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
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: A sign I can't understand ...

[Phil Holmes]

- Original Message - 
From: "Son_V" 

To: 
Sent: Thursday, October 16, 2014 12:49 PM
Subject: Re: A sign I can't understand ...



isn't that indicating that in a second (or later) verse there are two

syllables?

Yes. Sorry ... I've been too stingy. :-)

Here is a larger view:



Note that the "comma" on the right should be a breath


the notation of your image would be wrong


I suppose it too; but what should be the correct way to write this 
"thing"?

Sorry but when I encounter these strange situations I'm not able to find a
reference in the manual. It seems to me to try to find a needle in an
haystack.

Thanks.


The tricky thing with getting this closer to the original is fitting the 
quaver in while the crochet already fills the bar.  We can do this by 
multiplying the crochet duration by a half.  Then all you need to look up in 
the index is parenthesis and breath.


\relative c'{
\time 2/4
f8 a g4*1/2 \parenthesize g8 \breathe e
}


--
Phil Holmes 



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

Re: A sign I can't understand ...

[Janek Warchoł]

2014-10-16 13:49 GMT+02:00 Son_V :
>> isn't that indicating that in a second (or later) verse there are two
> syllables?
>
> Yes. Sorry ... I've been too stingy. :-)
>
> Here is a larger view:
>
> 
>
> Note that the "comma" on the right should be a breath
>
>> the notation of your image would be wrong
>
> I suppose it too; but what should be the correct way to write this "thing"?
> Sorry but when I encounter these strange situations I'm not able to find a
> reference in the manual. It seems to me to try to find a needle in an
> haystack.

You could either use temporary polyphony, possibly with making second
voice smaller

\new Staff {
  \time 2/4
  f'8 a'
  << { \voiceOne g'4 } \new CueVoice { \voiceTwo g'8 8 } >>
}

or a dashed tie

\new Staff {
  \time 2/4
  f'8 a'
  \tieDashed
  g'8 ~ 8
}

Personally i prefer the second solution, especially that it's easier
to get lyrics to work with it.

best,
Janek

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

Re: A sign I can't understand ...

[Son_V]

> isn't that indicating that in a second (or later) verse there are two
syllables?

Yes. Sorry ... I've been too stingy. :-)

Here is a larger view: 

 

Note that the "comma" on the right should be a breath

> the notation of your image would be wrong

I suppose it too; but what should be the correct way to write this "thing"?
Sorry but when I encounter these strange situations I'm not able to find a
reference in the manual. It seems to me to try to find a needle in an
haystack.

Thanks.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/A-sign-I-can-t-understand-tp167597p167616.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