Re: Dynamics placement

[Kieren MacMillan]

Hi Graham,

> The unwelcome spacing between the 4th and 5th notes goes away if one:

… uses

mpdolce = -\tweak X-extent #empty-interval #(make-dynamic-atr-script "mp" 
"dolce”)

=)

Hope this helps!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: Dynamics placement

[Graham King]

Here is a compilable example.  It is a bit long, but I think it is
pretty close to minimal.

In its defence: the first 32 lines are, effectively, snippet 739
modified to produce "dynamic text" instead of "text dynamic" (in this
case, "mp dolce" instead of, say, "meno f").

The remaining few lines are one part from a very heavily redacted
movement of a quintet.



The unwelcome spacing between the 4th and 5th notes goes away if one:

  * transposes the second bar up an octave; or
  * comments out the key signature; or
  * comments out \new StaffGroup; or
  * uncomments the line containing DynamicLineSpanner.staff-padding

I think I can live with the final option, assuming I can localise the
staff-padding change when I apply it to the big score.  Problem solved;
sorry for the noise.

Here's the code, attached, in case either I'm missing something obvious,
or the modified snippet 739 is useful to someone.

-- Graham
\version "2.19.35"

%% The relevant parts of my modified version of snippet 739 %%
% calculate x-alignment based on attribute text + dynamic text
% this has to be a markup-command to get stencil-extent based on 
(interpret-markup layout props ...)
#(define-markup-command (center-dynatr layout props atr-text dyn)(markup? 
string?)
   "x-align on center of dynamic"
   (let* (
   (text (string-append " " atr-text ))
   (atr-stencil (interpret-markup layout props (markup #:normal-text 
#:italic text)))
   (dyn-stencil (interpret-markup layout props (markup #:dynamic dyn)))
   (atr-x-ext (ly:stencil-extent atr-stencil X))
   (dyn-x-ext (ly:stencil-extent dyn-stencil X))
   (atr-x (- (cdr atr-x-ext)(car atr-x-ext)))
   (dyn-x (- (cdr dyn-x-ext)(car dyn-x-ext)))
   (x-align
(* (-
(/ (/ dyn-x 2) (+ atr-x dyn-x) )
0.5) 2)
)
   )
 (interpret-markup layout props (markup #:halign x-align #:concat 
(#:dynamic dyn #:normal-text #:italic text)))
 ))
% define a 'new' attributed dynamic script
#(define (make-dynamic-atr-script dyn atr)
   (let ((dynamic (make-dynamic-script (markup #:center-dynatr atr dyn
 (ly:music-set-property! dynamic 'tweaks (acons 'X-offset 0 
(ly:music-property dynamic 'tweaks)))
 dynamic))

% define some attributed dynamics
mpdolce = #(make-dynamic-atr-script "mp" "dolce")
%% Modified version of snippet 739 (ends) %%

music = \new Voice {
  \relative {
\clef bass
\key es \major
r2 r8 f8(\mpdolce e f) |
%\override DynamicLineSpanner.staff-padding = #2.5
r2 r8 bes,8(\mpdolce a bes) |
  }
}

\score {
  \new StaffGroup
  \new Staff {
\music
  }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: grace-note spacing and triplets

[Thomas Morley]

2016-03-22 15:10 GMT+01:00 Jan-Peter Voigt :
> Hi all,
>
> I have a problem spacing grace notes under a series of triplets. In the
> example, the grace notes produce a big gap between the tuplets or collide
> with the accidentals.
>
> As this situation is evident a few times, I will probably use extra-offset
> and place either the grace notes or the accidentals aside. So my question
> is, how would you typesetters solve this case?
>
> TIA
> Jan-Peter


Hi Jan-Peter,

some thoughts on a minimal example...

\version "2.18.2"

%% for comparability
%% without any override:
{ \grace { c''16 s4 }  bis'8 }


myLayout = \layout { \override Score.SpacingSpanner.strict-note-spacing = ##t }

%% collision
\score { { \grace { c''16 }  bis'8 } \myLayout }

%% returns:
%% programming error: Cannot determine neighbors for floating column.
%% this was my first thought, no idea what's wrong, never seen this error before
\score { { \grace { c''16 s4 }  bis'8 } \myLayout }

%% not sure why this works
%% textLengthOn is _not_ set
\score { { \grace { c''16-\markup \hspace #3 }  bis'8 } \myLayout }

%% inserting a Rest works
%% r8 is too much r16 to less
%% thus scaling to avoid the dot
\score { { \grace { c''16 \once \omit Rest r16*3/2 }  bis'8 } \myLayout }


HTH a bit,
  Harm

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

Re: Dynamics placement

[Graham King]

Ah yes, a minimal compilable example.  This is going to be tough,
especially as I've just noticed that some
_functionally_indistinguishable_code_ a few bars earlier yields this:


which is precisely the behaviour I'm after.

Nevertheless, I'll try to produce a minimal compilable example.  It
might take a while...
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Winged repeat bar line unique over multiple staves

[Alexis Maleval]

Thank you Simon.

Thomas,
your solution works very well too and it’s seems easier to use.
Thank you very much for your help.

Best regards,
Alexis.

> Le 22 mars 2016 à 23:10, Simon Albrecht  a écrit :
> 
> On 22.03.2016 23:01, Alexis Maleval wrote:
>> Hi Thomas,
>> thanks for your support, unfortunately I wasn’t able to open the two files, 
>> are they encrypted?
> 
> No, they aren’t. I can open them just fine.
> See  
> in case they didn’t arrive properly with you.
> 
> Best, Simon


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

Re: Dynamics placement

[Thomas Morley]

Hi Graham,

you did a nice and good job listing all the links:

2016-03-22 23:41 GMT+01:00 Graham King :

> [...]
> Notes:
> [1] https://lists.gnu.org/archive/html/lilypond-user/2016-03/msg00556.html
> [2] http://lsr.di.unimi.it/LSR/Item?id=739
> [3]
> http://www.lilypond.org/doc/v2.19/Documentation/learning/outside_002dstaff-objects
>

but the one over all important thing is missing.
A compilable, tiny example. ;)
Please understand: conditio sine qua non

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

Re: Dynamics placement

[Simon Albrecht]

Hello Graham,

please give an actual code example, as small as possible, to start with.

Best, Simon

On 22.03.2016 23:41, Graham King wrote:
I've adopted Simon Albrecht's excellent suggestion in an earlier 
thread [1], and am now using code based on snippet 739 [2] to typeset 
some long dynamic markings.  This has solved a host of layout 
problems; however, it has introduced this nasty spacing issue:



r2 r8 bes8(\mfdolce a bes) | g'4-.( f-.)

where \mfdolce is the result of snippet 739's make-dynamic-script.

Since the dynamic applies to the phrase rather than just the first 
note, is there a way to prevent it pushing the second note to the 
right?  I would like it to overlap the second (and, if necessary, 
subsequent) note(s) of this phrase.  I've looked at section 4.4.3 of 
the Learning Manual [3] and things don't appear promising.


Notes:
[1] https://lists.gnu.org/archive/html/lilypond-user/2016-03/msg00556.html
[2] http://lsr.di.unimi.it/LSR/Item?id=739
[3] 
http://www.lilypond.org/doc/v2.19/Documentation/learning/outside_002dstaff-objects 




___
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

Dynamics placement

[Graham King]

I've adopted Simon Albrecht's excellent suggestion in an earlier thread
[1], and am now using code based on snippet 739 [2] to typeset some long
dynamic markings.  This has solved a host of layout problems; however,
it has introduced this nasty spacing issue:



r2 r8 bes8(\mfdolce a bes) | g'4-.( f-.)  

where \mfdolce is the result of snippet 739's make-dynamic-script.

Since the dynamic applies to the phrase rather than just the first note,
is there a way to prevent it pushing the second note to the right?  I
would like it to overlap the second (and, if necessary, subsequent)
note(s) of this phrase.  I've looked at section 4.4.3 of the Learning
Manual [3] and things don't appear promising.

Notes:
[1]
https://lists.gnu.org/archive/html/lilypond-user/2016-03/msg00556.html
[2] http://lsr.di.unimi.it/LSR/Item?id=739
[3]
http://www.lilypond.org/doc/v2.19/Documentation/learning/outside_002dstaff-objects
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Winged repeat bar line unique over multiple staves

[Simon Albrecht]

On 22.03.2016 23:01, Alexis Maleval wrote:

Hi Thomas,
thanks for your support, unfortunately I wasn’t able to open the two files, are 
they encrypted?


No, they aren’t. I can open them just fine.
See 
 
in case they didn’t arrive properly with you.


Best, Simon

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

Re: Winged repeat bar line unique over multiple staves

[Alexis Maleval]

Hi Thomas,
thanks for your support, unfortunately I wasn’t able to open the two files, are 
they encrypted?

Regards,
Alexis.


> Le 22 mars 2016 à 22:19, Thomas Morley  a écrit :
> 
> Type: TEXT/PLAIN;
>   charset=UTF-8
> 
> 2016-03-22 15:57 GMT+01:00 Thomas Morley :
> 
>> Lemme think a bit more about the problem. In the past I tried
>> different methods to solve it, none of it convincing.
>> But maybe I'll get a better or at least new idea soon ...
> 
> 
> 
> Attached best I can do for today.
> Too tired to do more explanation/documentation, some 
> "comme


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

Re: Winged repeat bar line unique over multiple staves

[Alexis Maleval]

Hi Klaus,
thank you so much, it works fine without any heigh adjustment.
Many thanks to Schneidy.
it's really nice to have effective support.

Best regards,
Alexis.


> Le 22 mars 2016 à 21:57, Klaus Blum  a écrit :
> 
> Hi Alexis, 
> 
> Schneidy has created a snippet for that issue:
> http://lsr.di.unimi.it/LSR/Item?id=991
> 
> There's a little drawback: You have to (manually) adjust the bracket height
> to match the staff group height. 
> I've tried a little modification to avoid this: You can add the wings to the
> topmost and lowermost staff in the group: 
> 
> %
> ---
> 
> \version "2.18.2"
> 
> #(define-markup-command (staff-group-bracket-upper layout props
> bracket-height)(number?)
>   "Draw upper wing for StaffGroup bracket."
>   (interpret-markup layout props
> (markup
>  (#:with-dimensions (cons -0.001 0) (cons 0.001 0)
>(#:override (cons (quote filled) #t)
>  (#:path 0.01 `(
>  (moveto  0.00  ,(+ bracket-height 0.35))
>  (curveto  0.00  ,(+ bracket-height 0.43)  0.07 ,(+
> bracket-height 0.42)  0.10 ,(+ bracket-height 0.42))
>  (curveto  0.70  ,(+ bracket-height 0.42)  1.10 ,(+
> bracket-height 0.60)  1.76 ,(+ bracket-height 1.50))
>  (curveto  1.82  ,(+ bracket-height 1.58)  1.89 ,(+
> bracket-height 1.50)  1.85 ,(+ bracket-height 1.45))
>  (curveto  1.14  ,(+ bracket-height 0.40)  0.93 ,(+
> bracket-height 0.18)  0.45 ,bracket-height)
>  (lineto   0.00  ,bracket-height)
>  (closepath)
>  )))
> 
> #(define-markup-command (staff-group-bracket-lower layout props
> bracket-height)(number?)
>   "Draw lower wing for StaffGroup bracket."
>   (interpret-markup layout props
> (markup
>  (#:with-dimensions (cons -0.001 0) (cons 0.001 0)
>(#:override (cons (quote filled) #t)
>  (#:path 0.01 `(
>  (moveto   0.00  ,(* bracket-height -1))
>  (curveto  0.00  ,(+ (* bracket-height -1) -0.43) 
> 0.07 ,(+ (* bracket-height -1) -0.42)  0.10 ,(+ (* bracket-height -1)
> -0.42))
>  (curveto  0.70  ,(+ (* bracket-height -1) -0.42) 
> 1.10 ,(+ (* bracket-height -1) -0.60)  1.76 ,(+ (* bracket-height -1)
> -1.50))
>  (curveto  1.82  ,(+ (* bracket-height -1) -1.58) 
> 1.89 ,(+ (* bracket-height -1) -1.50)  1.85 ,(+ (* bracket-height -1)
> -1.45))
>  (curveto  1.14  ,(+ (* bracket-height -1) -0.40) 
> 0.93 ,(+ (* bracket-height -1) -0.18)  0.45 ,(* bracket-height -1))
>  (closepath
> 
> addUpperWing =
> #(define-music-function
>  (parser location repeat-bar-type)
>  (string?)
>  (cond
>   ((string=? repeat-bar-type "[")
>#{
>  \once \override Staff.BarLine.stencil =
>  #(lambda (grob)
> (ly:stencil-combine-at-edge
>  (ly:bar-line::print grob)
>  X LEFT
>  (grob-interpret-markup grob
>#{
>  \markup
>  % \translate #(cons 0 repeat-bar-translate)
>  \staff-group-bracket-upper #1.8
>#})))
>#})
>   ((string=? repeat-bar-type "]")
>#{
> 
>  \once \override Staff.BarLine.stencil =
>  #(lambda (grob)
> (ly:stencil-combine-at-edge
>  (ly:bar-line::print grob)
>  X RIGHT
>  (grob-interpret-markup grob
>#{
>  \markup
>  \rotate #180
>  % \translate #(cons 0 repeat-bar-translate)
>  \staff-group-bracket-lower #1.8
>#})))
>#})
>   (else
>#{
>  \once \override Staff.BarLine.stencil = #ly:bar-line::print
>#})))
> 
> addLowerWing =
> #(define-music-function
>  (parser location repeat-bar-type)
>  (string?)
>  (cond
>   ((string=? repeat-bar-type "[")
>#{
>  \once \override Staff.BarLine.stencil =
>  #(lambda (grob)
> (ly:stencil-combine-at-edge
>  (ly:bar-line::print grob)
>  X LEFT
>  (grob-interpret-markup grob
>#{
>  \markup
>  \staff-group-bracket-lower #1.8
>#})))
>#})
>   ((string=? repeat-bar-type "]")
>#{
> 
>  \once \override Staff.BarLine.stencil =
>  #(lambda (grob)
> (ly:stencil-combine-at-edge
>  (ly:bar-line::print grob)
>  X RIGHT
>  (grob-interpret-markup grob
>#{
>  \markup
>  \rotate #180
>  \staff-group-bracket-upper #1.8
>#})))
>#})
>   (else
>#{
>  \once \override Staff.BarLine.stencil = #ly:bar-line::print
>#})))
> 
> %%% Test:
> \new StaffGroup <<
>  \new Staff \relative c' {
>c4 d e f
>\repeat volta 2 {
>  \addUpperWing #"["
>  g a b c
>  d e f g
>  

Re: Winged repeat bar line unique over multiple staves

[Thomas Morley]

2016-03-22 15:57 GMT+01:00 Thomas Morley :

> Lemme think a bit more about the problem. In the past I tried
> different methods to solve it, none of it convincing.
> But maybe I'll get a better or at least new idea soon ...



Attached best I can do for today.
Too tired to do more explanation/documentation, some "comments" in file, though.

HTH,
 Harm


tip-bar-line-01.pdf
Description: Adobe PDF document
\version "2.19.38"

\pointAndClickOff

#(define (define-grob-property symbol type? description)
  (if (not (equal? (object-property symbol 'backend-doc) #f))
  (ly:error (_ "symbol ~S redefined") symbol))

  (set-object-property! symbol 'backend-type? type?)
  (set-object-property! symbol 'backend-doc description)
  symbol)

#(for-each
  (lambda (x)
(apply define-grob-property x))
`((tip 
  ,symbol? 
  "Which bracket tip should be printed for certain BarLines. 
Possible settings are @code{'up}, @code{'down} or @code{#f}
If set @code{#f} an automatic procedure takes over choosing the correct BarLine,
Which is not very safe.")))

CertainBracketTipsBarLines =
\override Score.BreakAlignGroup.after-line-breaking =
  #(lambda (grob)
(let* ((elts (ly:grob-object grob 'elements))
   (bar-lines
 (if (null? elts)
 '()
 (filter 
   (lambda (g) (grob::has-interface g 'bar-line-interface)) 
   (ly:grob-array->list elts
   (possible-relevant-bar-lines
 (filter 
   (lambda (b) (not (null? (ly:grob-property b 'tip
   bar-lines)))
  (if (and (>= (length bar-lines) 2)
   (not (null? possible-relevant-bar-lines))
   (member 
 (ly:grob-property (car bar-lines) 'glyph-name)
 '(":..:" ":|." ".|:")))
  (let* ((possible-top-bar-lines 
   (filter 
 (lambda (b) (eq? (ly:grob-property b 'tip) 'up))
 bar-lines))
 (top-bar-lines
   (if (null? possible-top-bar-lines)
   (list (car bar-lines))
   possible-top-bar-lines))
 (bar-lines-list-length (length top-bar-lines))
 (possible-bottom-bar-lines 
   (filter 
 (lambda (b) (eq? (ly:grob-property b 'tip) 'down))
 bar-lines))
 (bottom-bar-lines
   (if (null? possible-bottom-bar-lines)
   (list (last bar-lines))
   possible-bottom-bar-lines))
 (top-stil 
   (ly:grob-property (car top-bar-lines) 'stencil))
 (bottom-stil 
   (ly:grob-property (car bottom-bar-lines) 'stencil))
 (layout (ly:grob-layout grob))
 (props 
   (ly:grob-alist-chain 
 grob 
 (ly:output-def-lookup layout 'text-font-defaults)))
 (font 
   (ly:paper-get-font 
 layout
 (cons '((font-encoding . feta)) props)))
 (tip (ly:font-get-glyph font "brackettips.up"))
 (top-glyph-name 
   (ly:grob-property (car top-bar-lines) 'glyph-name))
 (repeat-type 
   (cond ((string=? top-glyph-name  ":..:")
  'double-repeat)
 ((string=? top-glyph-name ":|.")
  'close-repeat)
 ((string=? top-glyph-name ".|:")
  'open-repeat)
 (else #f)))
  (up-tip
(cond ((eq? repeat-type 'close-repeat)
(ly:stencil-translate-axis
  (ly:stencil-scale tip -1 1)
  (cdr (ly:stencil-extent top-stil X))
  X))
  ((eq? repeat-type 'double-repeat)
(let ((kern 
 (/ (ly:grob-property (car top-bar-lines) 
  'kern) 
10))
  (top-stil-ext (ly:stencil-extent top-stil X)))
  (ly:stencil-translate-axis
(ly:stencil-combine-at-edge
  (ly:stencil-scale tip -1 1)
  X RIGHT
  tip
  kern)
(- (interval-center top-stil-ext) (/ kern 2))
X)))
  (else tip)))
  (down-tip (ly:stencil-scale up-tip 1 -1)))
(for-each
  (lambda (grobb bar-stil dir tip-style)
 

Re: Winged repeat bar line unique over multiple staves

[Klaus Blum]

Hi Alexis, 

Schneidy has created a snippet for that issue:
http://lsr.di.unimi.it/LSR/Item?id=991

There's a little drawback: You have to (manually) adjust the bracket height
to match the staff group height. 
I've tried a little modification to avoid this: You can add the wings to the
topmost and lowermost staff in the group: 

%
---

\version "2.18.2"

#(define-markup-command (staff-group-bracket-upper layout props
bracket-height)(number?)
   "Draw upper wing for StaffGroup bracket."
   (interpret-markup layout props
 (markup
  (#:with-dimensions (cons -0.001 0) (cons 0.001 0)
(#:override (cons (quote filled) #t)
  (#:path 0.01 `(
  (moveto  0.00  ,(+ bracket-height 0.35))
  (curveto  0.00  ,(+ bracket-height 0.43)  0.07 ,(+
bracket-height 0.42)  0.10 ,(+ bracket-height 0.42))
  (curveto  0.70  ,(+ bracket-height 0.42)  1.10 ,(+
bracket-height 0.60)  1.76 ,(+ bracket-height 1.50))
  (curveto  1.82  ,(+ bracket-height 1.58)  1.89 ,(+
bracket-height 1.50)  1.85 ,(+ bracket-height 1.45))
  (curveto  1.14  ,(+ bracket-height 0.40)  0.93 ,(+
bracket-height 0.18)  0.45 ,bracket-height)
  (lineto   0.00  ,bracket-height)
  (closepath)
  )))

#(define-markup-command (staff-group-bracket-lower layout props
bracket-height)(number?)
   "Draw lower wing for StaffGroup bracket."
   (interpret-markup layout props
 (markup
  (#:with-dimensions (cons -0.001 0) (cons 0.001 0)
(#:override (cons (quote filled) #t)
  (#:path 0.01 `(
  (moveto   0.00  ,(* bracket-height -1))
  (curveto  0.00  ,(+ (* bracket-height -1) -0.43) 
0.07 ,(+ (* bracket-height -1) -0.42)  0.10 ,(+ (* bracket-height -1)
-0.42))
  (curveto  0.70  ,(+ (* bracket-height -1) -0.42) 
1.10 ,(+ (* bracket-height -1) -0.60)  1.76 ,(+ (* bracket-height -1)
-1.50))
  (curveto  1.82  ,(+ (* bracket-height -1) -1.58) 
1.89 ,(+ (* bracket-height -1) -1.50)  1.85 ,(+ (* bracket-height -1)
-1.45))
  (curveto  1.14  ,(+ (* bracket-height -1) -0.40) 
0.93 ,(+ (* bracket-height -1) -0.18)  0.45 ,(* bracket-height -1))
  (closepath

addUpperWing =
#(define-music-function
  (parser location repeat-bar-type)
  (string?)
  (cond
   ((string=? repeat-bar-type "[")
#{
  \once \override Staff.BarLine.stencil =
  #(lambda (grob)
 (ly:stencil-combine-at-edge
  (ly:bar-line::print grob)
  X LEFT
  (grob-interpret-markup grob
#{
  \markup
  % \translate #(cons 0 repeat-bar-translate)
  \staff-group-bracket-upper #1.8
#})))
#})
   ((string=? repeat-bar-type "]")
#{

  \once \override Staff.BarLine.stencil =
  #(lambda (grob)
 (ly:stencil-combine-at-edge
  (ly:bar-line::print grob)
  X RIGHT
  (grob-interpret-markup grob
#{
  \markup
  \rotate #180
  % \translate #(cons 0 repeat-bar-translate)
  \staff-group-bracket-lower #1.8
#})))
#})
   (else
#{
  \once \override Staff.BarLine.stencil = #ly:bar-line::print
#})))

addLowerWing =
#(define-music-function
  (parser location repeat-bar-type)
  (string?)
  (cond
   ((string=? repeat-bar-type "[")
#{
  \once \override Staff.BarLine.stencil =
  #(lambda (grob)
 (ly:stencil-combine-at-edge
  (ly:bar-line::print grob)
  X LEFT
  (grob-interpret-markup grob
#{
  \markup
  \staff-group-bracket-lower #1.8
#})))
#})
   ((string=? repeat-bar-type "]")
#{

  \once \override Staff.BarLine.stencil =
  #(lambda (grob)
 (ly:stencil-combine-at-edge
  (ly:bar-line::print grob)
  X RIGHT
  (grob-interpret-markup grob
#{
  \markup
  \rotate #180
  \staff-group-bracket-upper #1.8
#})))
#})
   (else
#{
  \once \override Staff.BarLine.stencil = #ly:bar-line::print
#})))

%%% Test:
\new StaffGroup <<
  \new Staff \relative c' {
c4 d e f
\repeat volta 2 {
  \addUpperWing #"["
  g a b c
  d e f g
  \addUpperWing #"]"
}
s8
  }
  \new Staff \relative c {
\clef F
c4 d e f
\repeat volta 2 {
  g a b c
  d e f g
}
s8
  }
  \new Staff \relative c, {
\clef F
c4 d e f
\repeat volta 2 {
  \addLowerWing #"["
  g a b c
  d e f g
  \addLowerWing #"]"
}
s8
  }
>>

%
---

Cheers, 

Re: grace-note spacing and triplets

[Simon Albrecht]

Hi Jan-Peter,

On 22.03.2016 15:10, Jan-Peter Voigt wrote:

Hi all,

I have a problem spacing grace notes under a series of triplets. In 
the example, the grace notes produce a big gap between the tuplets or 
collide with the accidentals.


It’s an annoying bug that this isn’t handled nicely, and there is no 
nice workaround either. I could only concoct the following hack:


%%%
\version "2.19.38"

pseudograce =
#(define-music-function (parser location music) (ly:music?)
   #{
 \tiny
 \temporary\stemUp
 \temporary\offset length -1 Stem

 $music
 \normalsize
 \revert Stem.direction
 \revert Stem.length
   #})

% triplets played by the flute
flute = \new Staff \with {
  \tupletSpan 8
  beamExceptions = #'((end .
(
  ((1 . 24) . (3 3 3 3 3 3 3 3))
  )))
} \tuplet 3/2 {
  gis'16( f'' e'') d''( c'' b') a'( gis' fis')
}

% sung words with grace notes
melody = \new Staff \new Voice {
  \autoBeamOff
  d''8*6/10 \pseudograce { c''16*4/5( } bis'8*6/10) \pseudograce 
{a'16(}  gis'8)

} \addlyrics { Je -- su, ach! }

% in this score, the grace notes produce gaps between the tuplets
\score {
  <<
\flute
\melody
  >>
}
%%%

v2.19.25 is needed because offsetting Stem length only became possible 
through issue 4516. Thanks David!


HTH, Simon

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

Re: Writing a number in stead of notehead.

[Malte Meyn]

Am 22.03.2016 um 18:23 schrieb Philip Bergwerf:

Hello dear lilypond users!

I am experimenting with rhytmic notation. How can i change a notehead into a
digit? Is there a way to do that. Of course there is! Please tell me and i
did see once a notation with numbers as rhytmic notation but i couldnt find
it. If someone knows please let me know.

Cheers, Philip Bergwerf



Please be more specific: into what sort of number? Only depending on the 
sort of head or on the duration? The duration with or without dots, as 
logarithm or not? How to treat tuplets?


Here a wild guess:

%

\version "2.19.38"

\new RhythmicStaff \with {
  \override NoteHead.stencil =
  #(lambda (grob)
 (let* ((event (event-cause grob))
(durlog (ly:duration-log (ly:event-property event 'duration)))
(durstring (number->string (expt 2 durlog
   (grob-interpret-markup grob durstring)))
} {
  2. 4 4 8 16 32 32 \tuplet 3/2 { 8 8 8 } 8.. 32
}

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

Writing a number in stead of notehead.

[Philip Bergwerf]

Hello dear lilypond users!

I am experimenting with rhytmic notation. How can i change a notehead into a
digit? Is there a way to do that. Of course there is! Please tell me and i
did see once a notation with numbers as rhytmic notation but i couldnt find
it. If someone knows please let me know.

Cheers, Philip Bergwerf



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Writing-a-number-in-stead-of-notehead-tp188824.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: Winged repeat bar line unique over multiple staves

[Marc Hohl]

Am 22.03.2016 um 14:20 schrieb Malte Meyn:



Am 22.03.2016 um 14:03 schrieb Alexis Maleval:

Hi,
I would like to know how to prevent a winged repeat bar line to be
split when it
has to cover 2 staves.


Probably this isn’t possible yet;


Yep. I rewrote the bar line stuff some years ago and stumbled across the 
fact that winged span bars are not possible.


I did not find an easy way to implement them, so I gave up :(

To be honest, the whole span bar creation routine is not really open for 
enhancements IIRC.


Marc



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

Re: Winged repeat bar line unique over multiple staves

[David Kastrup]

Thomas Morley  writes:

> 2016-03-22 15:46 GMT+01:00 David Kastrup :
>
>> And once you cater for that, the output is, uh, creative?
>
>
> lol
>
> http://lilypond.1069038.n5.nabble.com/attachment/58326/1/barlineOmegaBild.png
> shows how it was meant to be

Oh.  But that's all single-staff.  And single-staff _does_ work in a
straightforward manner already like Alexis showed.

-- 
David Kastrup

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

Re: Winged repeat bar line unique over multiple staves

[Thomas Morley]

2016-03-22 15:46 GMT+01:00 David Kastrup :

> And once you cater for that, the output is, uh, creative?


lol

http://lilypond.1069038.n5.nabble.com/attachment/58326/1/barlineOmegaBild.png
shows how it was meant to be

Cheers,
  Harm

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

Re: Winged repeat bar line unique over multiple staves

[Thomas Morley]

2016-03-22 15:25 GMT+01:00 Alexis Maleval :
> Thank you guys your quick answers and explanation.
> Here is attached an actual compilable example.
>
>
>
> By the way I’ve found this
> ttp://lilypond.1069038.n5.nabble.com/repeat-barlines-with-wings-td58324.html
> Unfortunately the suggested solution uses 2.12.3 and throws compilation
> error in 2.18.2. I don’t know if it could solve my problem.



Meanwhile the bar-line-interface was heavily changed.
Making this old code compile with recent lily-version would mean to
entirely rewrite it.

Lemme think a bit more about the problem. In the past I tried
different methods to solve it, none of it convincing.
But maybe I'll get a better or at least new idea soon ...

Btw, please don't use inline images, attach them.  I'm not the only
one always filtering them/reading mails text-only.

Thanks,
  Harm

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

Re: Winged repeat bar line unique over multiple staves

[David Kastrup]

David Kastrup  writes:

> Alexis Maleval  writes:
>
>> Thank you guys your quick answers and explanation.
>> Here is attached an actual compilable example.
>>
>>
>>
>> By the way I’ve found this
>> ttp://lilypond.1069038.n5.nabble.com/repeat-barlines-with-wings-td58324.html 
>> Unfortunately the suggested solution uses 2.12.3 and throws compilation error
>> in 2.18.2. I don’t know if it could solve my problem.
>
> There is convert-ly but it doesn't cater at all for
>
> commit a657051a1f3be6e6b3bee3647857bdba3c0b943e
> Author: Neil Puttock 
> Date:   Thu Aug 18 00:25:14 2011 +0100
>
> Complete removal of unused optarg in ly:stencil-combine-at-edge.
>
> Sigh.

And once you cater for that, the output is, uh, creative?



barlineOmega.pdf
Description: Adobe PDF document

So there obviously would be work involved to bring this up to scratch.

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

Re: Winged repeat bar line unique over multiple staves

[David Kastrup]

Alexis Maleval  writes:

> Thank you guys your quick answers and explanation.
> Here is attached an actual compilable example.
>
>
>
> By the way I’ve found this
> ttp://lilypond.1069038.n5.nabble.com/repeat-barlines-with-wings-td58324.html 
> Unfortunately the suggested solution uses 2.12.3 and throws compilation error
> in 2.18.2. I don’t know if it could solve my problem.

There is convert-ly but it doesn't cater at all for

commit a657051a1f3be6e6b3bee3647857bdba3c0b943e
Author: Neil Puttock 
Date:   Thu Aug 18 00:25:14 2011 +0100

Complete removal of unused optarg in ly:stencil-combine-at-edge.

Sigh.

-- 
David Kastrup

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

Re: Winged repeat bar line unique over multiple staves

[Alexis Maleval]

Thank you guys your quick answers and explanation.Here is attached an actual compilable example.

winged.ly
Description: Binary data
By the way I’ve found this ttp://lilypond.1069038.n5.nabble.com/repeat-barlines-with-wings-td58324.html Unfortunately the suggested solution uses 2.12.3 and throws compilation error in 2.18.2. I don’t know if it could solve my problem.Regards.Alexis.Le 22 mars 2016 à 14:17, David Kastrup  a écrit :Alexis Maleval  writes:Hi,I would like to know how to prevent a winged repeat bar line to be split when it has to cover 2 staves.Currently I'm using the following code :\layout { \context {   \Score   %% Changing the defaults from engraver-init.ly   startRepeatType = #"[|:"   endRepeatType = #":|]"   doubleRepeatType = #":|][|:" }}It gives :Not really since there is no music.  Please create an actual compilableminimal example so that it's reasonably easy for people to make thenecessary changes.-- David Kastrup___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

grace-note spacing and triplets

[Jan-Peter Voigt]

Hi all,

I have a problem spacing grace notes under a series of triplets. In the 
example, the grace notes produce a big gap between the tuplets or 
collide with the accidentals.


As this situation is evident a few times, I will probably use 
extra-offset and place either the grace notes or the accidentals aside. 
So my question is, how would you typesetters solve this case?


TIA
Jan-Peter
\version "2.18.2"

% triplets played by the flute
flute = \new Staff \with {
  \tupletSpan 8
  beamExceptions = #'((end .
(
  ((1 . 24) . (3 3 3 3 3 3 3 3))
  )))
} \tuplet 3/2 {
  gis'16( f'' e'') d''( c'' b') a'( gis' fis')
}

% sung words with grace notes
melody = \new Staff \new Voice {
  \autoBeamOff
  d''8 \grace {c''16(}  bis'8) \grace {a'16(}  gis'8)
} \addlyrics { Je -- su, ach! }

% in this score, the grace notes produce gaps between the tuplets
\score {
  <<
\flute
\melody
  >>
}

% in this score the grace notes collide with the accidentals
\score {
  <<
\flute
\melody
  >>
  \layout {
\context {
  \Score
  proportionalNotationDuration = #(ly:make-moment 1/24)
  \override SpacingSpanner.strict-note-spacing = ##t
}
  }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Winged repeat bar line unique over multiple staves

[David Kastrup]

Alexis Maleval  writes:

> Hi,
> I would like to know how to prevent a winged repeat bar line to be split when 
> it has to cover 2 staves.
>
> Currently I'm using the following code :
>
> \layout {
>   \context {
> \Score
> %% Changing the defaults from engraver-init.ly
> startRepeatType = #"[|:"
> endRepeatType = #":|]"
> doubleRepeatType = #":|][|:"
>   }
> }
>
> It gives :

Not really since there is no music.  Please create an actual compilable
minimal example so that it's reasonably easy for people to make the
necessary changes.

-- 
David Kastrup

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

Re: Winged repeat bar line unique over multiple staves

[Malte Meyn]

Am 22.03.2016 um 14:03 schrieb Alexis Maleval:

Hi,
I would like to know how to prevent a winged repeat bar line to be split when it
has to cover 2 staves.


Probably this isn’t possible yet; a BarLine is put together from the bar 
lines of every single staff plus the SpanBars between the staves. So I 
think one would need the following things:


1. Not only thick bar line with and without wings but also thick bar 
lines with only one wing (top or bottom).

2. A possibility to find out which of these is needed for each staff.
3. Compatibility with \defineBarLine.

Here some code which doesn’t solve your problem but shows 1. the use of 
\defineBarLine and 2. shows the difference between BarLines and SpanBars 
(colors).


%

\version "2.19.38"

\defineBarLine "[|:" #'("|" "[|:" ".|")
\defineBarLine ":|]" #'(":|]" "" " |.")
\defineBarLine ":|][|:" #'(":|]" "[|:" " |..|")

\layout {
  \context {
\Score
startRepeatType = #"[|:"
endRepeatType = #":|]"
doubleRepeatType = #":|][|:"
\override SpanBar.color = #blue
\override BarLine.color = #red
  }
}

\new StaffGroup <<
  \new Staff \relative {
c'1 \repeat volta 2 c \repeat volta 2 c c
  }
  \new Staff \relative {
c'1 \repeat volta 2 c \repeat volta 2 c c
  }
>>

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

Winged repeat bar line unique over multiple staves

[Alexis Maleval]

Hi,
I would like to know how to prevent a winged repeat bar line to be split when 
it has to cover 2 staves.

Currently I'm using the following code :

\layout {
  \context {
\Score
%% Changing the defaults from engraver-init.ly
startRepeatType = #"[|:"
endRepeatType = #":|]"
doubleRepeatType = #":|][|:"
  }
}

It gives :


But what I want is :


With the standard RepeatType the bar is not split but I don’t have the wings.
I would really appreciate if you could give me a hint.

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

Re: Q re LSR snippet 744

[Thomas Morley]

2016-03-19 21:51 GMT+01:00 Thomas Morley :
> 2016-03-19 21:43 GMT+01:00 Michael Gerdau :
>>> Because it's an really old snippet, I rewrote large parts of it,
>>> reflecting functionality being in the source meanwhile.
>>> Please test, if no glitch escaped me, I'll replace the old code with
>>> the one below:
>>
>> All my own use cases behave visually unchanged with the rewritten
>> version.
>>
>> Best wishes,
>> Michael
>
>
>
> Hi Simon and Michael,
>
> thanks a lot for testing.
>
> I'll likely wait a few days more, giving others the chance to comment
> as well, before I change the LSR-snippet.
>
> Best,
>   Harm

Changed now.
http://lsr.di.unimi.it/LSR/Item?id=744

Thanks,
  Harm

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

Re: A big advantage to lilypond

[David Kastrup]

Simon Albrecht  writes:

> Hi Daniel,
>
> On 22.03.2016 01:46, Redwood (Daniel) wrote:
>> But I wonder: why aren’t more lilypond authors posting more of their
>> sources to IMSLP?
>
> personally, I’m often reluctant to do so, because I might want to
> distribute my typesets commercially. In my opinion, _good_ music
> typography is an art and science and worth paying for;

Except that nobody even gets a chance to pay for it because you merely
"might want to distribute your typesets commercially".

Have you considered uploading them with a payment suggestion and
mechanism?  They won't magically market themselves, and the default
workings of the world and your own inertia make it more rather than less
likely that you'll ever get to marketing them, and even then the
question is what you'll be making from it.

Take a look at .  The
Edition Thoeni was founded by Maurice Thöni in 1944 and kept alive until
1980.  Thöni was quite prolific and wrote a lot of original pieces and
arrangements many of the scores in the edition himself.  However, the
current state of the edition is such that his daughter passes most of
the proceeds from the _performances_ into upkeep of the edition (I've
met her and Aegler in Zürich because my main accordion was obviously
built for Maurice Thöni and I was looking for evidence that he actually
played it at some point of time).

Making money from scores is really rather tricky ultimately and the big
editions keep themselves alive by having very streamlined processes and
pretty invasive agreements that tend to last longer than a composer's
life.

But still the prospect of "I might market this at some time for great
returns" keeps back music as well as software: how much "shareware" has
ever turned a profit commensurate of the effort to devise payment
schemes and restrictions?

So I really suggest that you take stock about what you _realistically_
will actually be marketing yourself, and how much you expect to gain
from it, versus how much it is worth to you that the arrangements/scores
actually get played.

I'd add payment suggestions (make it as easy as possible, Paypal and a
suggested sum) to the score.  Don't expect a windfall.  Probably
"enquire when custom arrangements are needed" is likely to provide the
most payback even when the source is readily available: again, you as
the author are probably most likely to turn money into adapted scores.

Particularly when you arrange your scores in a manner where creating
arrangements is mostly trivial.

> also I create an own visual style with my typesets that I don’t want
> others to easily discard. It’s a generous thing to typeset music and
> publish the source, but it’s perfectly valid to not do so and keep it
> private.

Sure.

> There’s also a technical side to it: (nearly) all of the scores I
> typeset rely on my personal stylesheets library, which I also feel
> somewhat protective about, and it’s impractical to include all of it
> in such an upload, or make a specific version containing only that
> which is really needed…

Well, LilyPond needs better schemes to organize personal stylesheets,
just like LaTeX has ways to organize document classes and styles.  But
again the main question is what you are trying to protect your
stylesheets from.  Other people working with them?  If there is actual
money in that, who would people first contact when needing custom work
to be done?

Yes, most of the work done using your scores and library is going to
bypass you.  However, you don't make money from work that is not done at
all either.

Many private people are hogging their "Intellectual Property" since they
see the valuations popular artists get for it.  But you won't get
anything from keeping it unpublished indefinitely.

> And lastly: even if I can obtain a ly source file from somewhere on
> the web, I sometimes have to rework the entire code, before making any
> use of it (and then I wonder if I’d been better off to just input it
> myself). Sometimes the coding is objectively sloppy, convoluted, or
> difficult to read; sometimes it’s just because of different coding
> styles, or approaches to representing the music[1], which can pose
> extremely annoying obstacles in sharing code. And the python-ly
> (Frescobaldi) formatting tools only get you so far (great though for
> doubling durations, or absolute->relative, or the like).  Which is why
> I very much think we need higher standards in that area…

Where will the high standards come from if people are protective about
the good stuff in their personal scores and stylesheets?

It's pretty hard to change your bank accounts with typesetting.  Just
try it seriously for a few years instead of going "I might want to do it
at some point in life" indefinitely.  It's easier to change the world.

All the best,

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org

Re: A big advantage to lilypond

[Simon Albrecht]

Hi Daniel,

On 22.03.2016 01:46, Redwood (Daniel) wrote:

But I wonder: why aren’t more lilypond authors posting more of their sources to 
IMSLP?


personally, I’m often reluctant to do so, because I might want to 
distribute my typesets commercially. In my opinion, _good_ music 
typography is an art and science and worth paying for; also I create an 
own visual style with my typesets that I don’t want others to easily 
discard. It’s a generous thing to typeset music and publish the source, 
but it’s perfectly valid to not do so and keep it private.
There’s also a technical side to it: (nearly) all of the scores I 
typeset rely on my personal stylesheets library, which I also feel 
somewhat protective about, and it’s impractical to include all of it in 
such an upload, or make a specific version containing only that which is 
really needed…



  And is there some way to find the lilypond source files — the pieces that 
have lilypond sources. I found some through their postings on a French site 
(can’t think of the name now), but it’s on about a dozen pieces, none of which 
interest me.


There are a few sources beside IMSLP that may be considered:
Mutopia has already been mentioned.
Nicolas Sceaux’s ‘Nenuvar’ editions  
– that’s likely the one you were referring to.

Nancho Álvarez’ ‘Victoria’ site 
Also, sometimes you find .ly sources on CPDL as well.


Music I’m going to perform, I usually typeset anyway, partly as a way to learn 
the music. But much of what I play is for my enjoyment, and I don’t rescore it. 
Also, much music like Beethoven sonatas are a great deal of trouble to 
score/typeset.


Another point to consider: why would you want to do new typesets? E.g. I 
have no (or very little) understanding for anybody to retypeset works by 
Brahms, since there’s the superb 1927 complete edition, which is not 
only typeset to the highest possible standard, beautiful and legible, 
but also to my knowledge doesn’t have any problems regarding musical 
text. Admittedly often the problem is that you have to choose between 
/either/ good typography in older editions /or/ reliable musical text in 
newer editions, with old editions being error-prone or convoluted with 
additions, and new editions being a typographical nightmare, which I 
find hard to stand as well.

But of course you will know yourself what you want to retypeset, and why.

And lastly: even if I can obtain a ly source file from somewhere on the 
web, I sometimes have to rework the entire code, before making any use 
of it (and then I wonder if I’d been better off to just input it 
myself). Sometimes the coding is objectively sloppy, convoluted, or 
difficult to read; sometimes it’s just because of different coding 
styles, or approaches to representing the music[1], which can pose 
extremely annoying obstacles in sharing code. And the python-ly 
(Frescobaldi) formatting tools only get you so far (great though for 
doubling durations, or absolute->relative, or the like).

Which is why I very much think we need higher standards in that area…

Yours,
Simon

[1] E.g. in ancient (mensural) music: One finds scores with one bar per 
line, and with the splitting of ‘cross-bar’ notes hardcoded into the 
LilyPond source. However, that badly reflects the intent of the original 
notation, and prevents making editions without complete bar lines and 
without splitting notes from the same source. It’s such a fortune that 
we have the Completion_heads_engraver to do exactly that which 
contemporally would have been the way to go from parts (without 
barlines) to scores (with barlines and split durations). And so I have 
been changing thousands of lines of code to use this facility. The ‘one 
bar per line’ approach is sensible for some kinds of music, but it’s 
definitely not sensible for mensural music with such a different notion 
of timing concepts.
Also, it’s often unclear whether to code different sections of a work as 
separate scores or not, with both having different implications for 
titling, instrument names, file structure…


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

Re: A big advantage to lilypond

[Andrew Bernard]

Of course. What I mean is that they strive to comply with copyright law.

Andrew


On 22/03/2016, 20:08, "David Kastrup"  wrote:

Andrew Bernard  writes:

 Hello Daniel,

 IMSLP strictly enforces copyright, and respects that law in all the
 various international jurisdictions.

They don't have standing to enforce copyright, but they most certainly
_heed_ it.  They don't put up scores with incompatible licenses and take
down content when they are notified of the content being improperly
labelled or submitted.

-- 
David Kastrup


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

Re: A big advantage to lilypond

[David Kastrup]

Andrew Bernard  writes:

> Hello Daniel,
>
> IMSLP strictly enforces copyright, and respects that law in all the
> various international jurisdictions.

They don't have standing to enforce copyright, but they most certainly
_heed_ it.  They don't put up scores with incompatible licenses and take
down content when they are notified of the content being improperly
labelled or submitted.

-- 
David Kastrup

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

Re: A big advantage to lilypond

[Andrew Bernard]

Hello Daniel,

IMSLP strictly enforces copyright, and respects that law in all the various 
international jurisdictions.

Andrew


On 22/03/2016, 11:59, "Redwood (Daniel)" 
 wrote:

Maybe, but then putting them on IMSLP?

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

Re: Licence LilyPond Logo?

[Barrios Blue]

The term "Powered by" is already in use for Emacs Org Mode in which the site 
was built, so this might cause confusion too. But I could take a picture of our 
lily pond in the garden and put it on the site with some bars of a score I made 
underneath. This should be different enough to be distinguished from the 
original logo but also similar enough to remember LilyPond as a notation 
typesetting software.

regards Marco



J Martin Rushton  schrieb am 22:51 Sonntag, 
20.März 2016:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

You might care to have a quick look at
https://www.apache.org/foundation/press/kit/#plain-feather-powered-by-ap
ache-logo
for an idea.  Apache are reasonably protective of their logo, but
encourage users to 'proudly display “Powered By Apache” assets on
their Websites, documentation, marketing materials, etc'.

Perhaps you might consider doing something similar?  I'm sure the
project would welcome it; you can't be alone in wanting to do this.

Regards,
Martin

On 20/03/16 21:25, Francisco Vila wrote:
> The original photo of the [single] lilypad is by Krista
> Scott-Dixon (stumptuous.com). Taken at the Van Dusen Botanical
> Garden situated in Vancouver, British Columbia, Canada. Somebody
> made a double lilypad from the photo. Later, saturation and 
> contrast  were improved by another person. John Mandereau provided
> a music snippet for the background. Then I pasted the flower on
> the music. So my share of the rights on the logo needs three
> decimals after the comma to be properly measured. I am positive
> nobody is going to sue you for its use, and it is good for
> eye-catching on any lilypond-related material, yet my advice is 
> that you modify or customize it in some or another way (colors, 
> background etc) so that its official use by us is unmistakenly
> related to us, and otherwise related, unofficial material uses
> another version of the logo to avoid confussion.
> 
> 
> 
> 
> 2016-03-20 22:05 GMT+01:00 Barrios Blue :
>> It's not my intention to confuse or even offend anyone by using
>> the Logo on my tiny tutorial site. Although I make it pretty
>> clear right at the beginning that it has nothing to do with  the
>> offical docs, people may skip this. I probably should go looking
>> for another eye-catcher.
>> 
>> cheers Marco
>> 
>> ___ lilypond-user
>> mailing list lilypond-user@gnu.org 
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJW7xtbAAoJEAF3yXsqtyBlF8cP/AzrAuDznAbttSxQHrabU1gb
n1ERVoPzW/dsJulm4v3T4Fn/a5CkugP2dUCUGsoKWWM5pjrQSZ5xkLMC/fG8Wd8C
IV4tx/mPQzAhMKzN6ITCdJDI5c4X5BniUNqEMyjJsx6MRwE7GzQRAWetADJawWIm
Sly6Yz8c4UbzzX1HzooqRXacAHU2VmRtFXFvwQg8KU3xIQrOOMa7paqM+8JxZShN
EW4iHgofmgYFePbRH/DGhKwxBSLVuP3ADsLpoRu+eV4zqJpXq7lsiGa1Jptl0u73
3frX6dCBvv7n1vMxbSqc4ScEH1e11ORsA0mzFJpMN9UCqPVnt0Co3uJzqzpRCpxj
9rneOv26Jf371IeH4g+2aaRuPV9oyH2amu+oLSrhWV5WMxCg2tgZRQVLeIrKrRqv
+mDNoUSQGSuX8ZjEkAwx4RAOGiEsn/rFbwD0CHemgHKjk+kXcR3ManK4SYHKAvQr
Oqwo8P97YKED5Z1sSCHyL5wPLa42OIPYDUS+BiHLPOiy3J/YNKH1/ApkQlyvsGbP
+bUKHHc7hJKeRHqewl4+yObLLXlly+hipU4x59z0hnglqvCEXUk+4l8TFbz6mv/w
AkOtz4AlieoAqNdCEfJHU6AqKL4+fXzChUbElVRjX098oWyTagwjCGvb0+DPNjQX
N06uCeBDVXOMK2+6KkgP
=qhZw
-END PGP SIGNATURE-


___
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