Bare durations as music function argument?

[Simon Albrecht]

Hello,

the bare durations that can now be used to write notes with unspecified 
pitch don’t work as music function arguments:


\version "2.19.32"
\new DrumStaff \with {
  \override StaffSymbol.line-count = 1
} \new DrumVoice {
  4 \slashedGrace 16 4
}
\relative {
  r4 r8 c'' \appoggiatura 4 b2
}

– each yielding ‘error: wrong type for argument 1.  Expecting music, 
found 16’ or similar.


David, is that intentional?

Yours, Simon

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

Noteheads slightly too large

[Gilberto Agostinho]

Hi bug squad,

This one is really nitpicking, but by zooming in on a note located in
between two staff lines, we can notice that the noteheads always extend a
little tiny bit beyond the top staff. See:

 

Elaine Gould, in her book /Behind Bars/, states that "[t]he notehead fills
the space, touching the stave-line on each side of it, but without extending
beyond either line" (p. 10).

Cheers,
Gilberto



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Noteheads-slightly-too-large-tp184659.html
Sent from the Bugs mailing list archive at Nabble.com.

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

Re: Unnecessary bad beam warning

[Palmer Ralph]

On Wed, Dec 9, 2015 at 6:38 PM, Simon Albrecht 
wrote:

> Hello,
>
> maybe Lily should not give a ‘no viable initial configuration found: may
> not find good beam slope’ warning if the user has already taken care of the
> problem through the Beam’s positions property:
>
> \version "2.19.32"
> {
>   \stemUp g'8-\offset positions #'(-1 . .3) [ \stemDown e'']
> }
>
> (Yes, the example doesn’t make much sense.)
> Wishful thinking?


Perhaps, but you won't get it if you don't ask. I (Ralph) do not know how
to discriminate between problems with easy vs. difficult solutions, so I'm
adding this as Issue #4692 :
https://sourceforge.net/p/testlilyissues/issues/4692/
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: \autochange bug

[Palmer Ralph]

On Tue, Dec 1, 2015 at 7:34 PM, Gilberto Agostinho <
gilbertohasn...@googlemail.com> wrote:

> Hello list,
>
> Here is a bizarre little bug I came across today: for some reason, an
> invisible rest on a different Staff seems to affect the kneed beamed stems
> on a PianoStaff when using \autochange
>

Greetings, Gilberto - This has been posted as Issue #4691 :
https://sourceforge.net/p/testlilyissues/issues/4691/

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

Wrong stem direction with beam?

[Simon Albrecht]

Hello,

do you agree that in this example the stems should go up? The majority 
of note heads sits in the lower half of the staff.



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

Re: Noteheads slightly too large

[Urs Liska]

Am 12.12.2015 um 00:02 schrieb Simon Albrecht:
> Thanks for the report.
> 

This *may* be intended, which should be checked - if someone recalls any
discussion.
At least I recall speaking someone from a major publishing house about
how they created their own music font, and specifically made it do what
the OP reported.

Urs

>
> On 11.12.2015 12:37, Gilberto Agostinho wrote:
>> Hi bug squad,
>>
>> This one is really nitpicking, but by zooming in on a note located in
>> between two staff lines, we can notice that the noteheads always
>> extend a
>> little tiny bit beyond the top staff. See:
>>
>> 
>>
>> Elaine Gould, in her book /Behind Bars/, states that "[t]he notehead
>> fills
>> the space, touching the stave-line on each side of it, but without
>> extending
>> beyond either line" (p. 10).
>>
>> Cheers,
>> Gilberto
>>
>>
>>
>> -- 
>> View this message in context:
>> http://lilypond.1069038.n5.nabble.com/Noteheads-slightly-too-large-tp184659.html
>> Sent from the Bugs mailing list archive at Nabble.com.
>>
>> ___
>> bug-lilypond mailing list
>> bug-lilypond@gnu.org
>> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond


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

Re: lilypond-book: "external" fonts and --pdf option problem

[Masamichi HOSODA]

> Thank you for finding this. I'm wondering if there is a more generic way to
> identify third-party fonts rather than hard-coding it like this? Perhaps by
> checking if the font has the LILY, LILC, and LILF subtables? I'm just
> brain-storming...

How about following patch?

In the case of text font, variable `font' is set to #f.
In the case of music font, variable `font' is set to non-#f.


```
diff --git a/scm/framework-ps.scm b/scm/framework-ps.scm
index 60d7bb3..f6d1700 100644
--- a/scm/framework-ps.scm
+++ b/scm/framework-ps.scm
@@ -246,10 +246,15 @@
footer)))
 
 (define (write-preamble paper load-fonts? port)
-  (define (internal-font? file-name)
-(or (string-startswith file-name "Emmentaler")
-(string-startswith file-name "emmentaler")
-))
+  (define (internal-font? font-name-filename)
+(let* ((font (car font-name-filename))
+   (file-name (caddr font-name-filename))
+   (font-file-name (ly:find-file (format #f "~a.otf" file-name
+  (and font
+   (cff-font? font)
+   font-file-name
+   (string-contains font-file-name
+(ly:get-option 'datadir)
 
   (define (load-font-via-GS font-name-filename)
 (define (ps-load-file file-name)
@@ -272,7 +277,7 @@
 (if (mac-font? bare-file-name)
 (handle-mac-font name bare-file-name)
 (cond
- ((internal-font? file-name)
+ ((and font (cff-font? font))
   (ps-load-file (ly:find-file
  (format #f "~a.otf" file-name
  ((string? bare-file-name)
@@ -402,7 +407,7 @@
 ((ly:get-option 'gs-load-lily-fonts)
  (if (or (string-contains (caddr name)
   (ly:get-option 'datadir))
- (internal-font? (caddr name)))
+ (internal-font? name))
  (load-font-via-GS name)
  (load-font name)))
 (else
```

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

Re: Bare durations as music function argument?

[David Kastrup]

Simon Albrecht  writes:

> Hello,
>
> the bare durations that can now be used to write notes with
> unspecified pitch don’t work as music function arguments:
>
> \version "2.19.32"
> \new DrumStaff \with {
>   \override StaffSymbol.line-count = 1
> } \new DrumVoice {
>   4 \slashedGrace 16 4
> }
> \relative {
>   r4 r8 c'' \appoggiatura 4 b2
> }
>
> – each yielding ‘error: wrong type for argument 1.  Expecting music,
> found 16’ or similar.
>
> David, is that intentional?

Quite so.  From lilypond-changes.info:

   • Isolated durations in music sequences now stand for unpitched
 notes.  This may be useful for specifying rhythms to music or
 scheme functions.

"Isolated durations in music sequences".  You can place { } to make a
sequence.  Telling different types of music function arguments apart is
tricky enough as it stands.

Would \tuplet 3/2 4 2 be a quarter triole followed by a half note, or a
half triole to be grouped in groups of quarter length?

-- 
David Kastrup

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