Re: Warnings when omitting fingering with overridden orientation

[Thomas Morley]

2016-09-02 21:36 GMT+02:00 Thomas Morley :

> Warrants a ticket I'd say.

It's now:
Issue 4964 fingeringOrientations don't deal properly with omitted
Fingering-stencils
https://sourceforge.net/p/testlilyissues/issues/4964/

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

Re: Warnings when omitting fingering with overridden orientation

[Thomas Morley]

2016-09-02 18:27 GMT+02:00 David Kastrup :
> Thomas Morley  writes:
>
>> 2016-09-02 16:44 GMT+02:00 Hinrik Örn Sigurðsson :
>>> If I want to omit the fingering instructions for some part of a score or the
>>> entire thing, I put "\omit Fingering" in the appopriate place. However, it
>>> results in warnings ("programming error: Infinity or NaN encountered") if
>>> "\set fingeringOrientations = #'(left)" has been previously done. The PDF
>>> output is still correct though.
>>>
>>> Test case:
>>>
>>> \version "2.19.47"
>>>
>>> \relative c' {
>>>   \clef treble
>>>   \key d \major
>>>   \set fingeringOrientations = #'(left)
>>>   2 4 d |
>>>   \omit Fingering
>>>   8 g' g4 cis,2 |
>>> }
>>
>>
>> Try:
>>
>> \relative c' {
>>   \clef treble
>>   \key d \major
>>   \set fingeringOrientations = #'(left)
>>   2 4 d |
>>   \omit Fingering
>>   \unset fingeringOrientations
>>   8 g' g4 cis,2 |
>> }
>>
>> Obviously the context-property `fingeringOrientations' needs a stencil
>> to deal with, thus unset it.
>
> Arguably, that would be a condition worth detecting and silently
> ignoring.
>
> --
> David Kastrup

Hmm, might be a bit more complicated:

\relative c' {
  \set fingeringOrientations = #'(left)
  1
  \omit Fingering
  1
}

\relative c' {
  \set fingeringOrientations = #'(left)
  1
  \omit Fingering
  1
}

No complaints about the first example. Warrants a ticket I'd say.

Cheers,
  Harm

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

Re: Warnings when omitting fingering with overridden orientation

[David Kastrup]

Thomas Morley  writes:

> 2016-09-02 16:44 GMT+02:00 Hinrik Örn Sigurðsson :
>> If I want to omit the fingering instructions for some part of a score or the
>> entire thing, I put "\omit Fingering" in the appopriate place. However, it
>> results in warnings ("programming error: Infinity or NaN encountered") if
>> "\set fingeringOrientations = #'(left)" has been previously done. The PDF
>> output is still correct though.
>>
>> Test case:
>>
>> \version "2.19.47"
>>
>> \relative c' {
>>   \clef treble
>>   \key d \major
>>   \set fingeringOrientations = #'(left)
>>   2 4 d |
>>   \omit Fingering
>>   8 g' g4 cis,2 |
>> }
>
>
> Try:
>
> \relative c' {
>   \clef treble
>   \key d \major
>   \set fingeringOrientations = #'(left)
>   2 4 d |
>   \omit Fingering
>   \unset fingeringOrientations
>   8 g' g4 cis,2 |
> }
>
> Obviously the context-property `fingeringOrientations' needs a stencil
> to deal with, thus unset it.

Arguably, that would be a condition worth detecting and silently
ignoring.

-- 
David Kastrup

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

Re: Horizontal positioning of rests

[Karen Billings]

Thank you so much for your help - using R1 instead of r1 did the trick.
I don't know how, in a year's worth of reading documentation, the sentence 
"Whole measure rests, centered in the middle of the measure, must be entered as 
multi-measure rests." in section 1.2.2 of the Notation Reference never fully 
sank in... I never skipped over to the section entitled "Whole Measure Rests" 
except when I was trying to deal with multiple measures of rests.
Thanks again!
Karen 

On Friday, September 2, 2016 2:10 AM, David Kastrup  wrote:
 

 David Wright  writes:

> On Fri 02 Sep 2016 at 06:55:31 (+0200), Remy CLAVERIE wrote:
>> Hi David,
>> What is the book that you named 'NM' ?
>
> Sorry,... The Notation Manual for LilyPond.

The "official" abbreviation for that is actually NR (as in "Notation
Reference", the proper title of the manual).

-- 
David Kastrup

___
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: Warnings when omitting fingering with overridden orientation

[Thomas Morley]

2016-09-02 16:44 GMT+02:00 Hinrik Örn Sigurðsson :
> If I want to omit the fingering instructions for some part of a score or the
> entire thing, I put "\omit Fingering" in the appopriate place. However, it
> results in warnings ("programming error: Infinity or NaN encountered") if
> "\set fingeringOrientations = #'(left)" has been previously done. The PDF
> output is still correct though.
>
> Test case:
>
> \version "2.19.47"
>
> \relative c' {
>   \clef treble
>   \key d \major
>   \set fingeringOrientations = #'(left)
>   2 4 d |
>   \omit Fingering
>   8 g' g4 cis,2 |
> }


Try:

\relative c' {
  \clef treble
  \key d \major
  \set fingeringOrientations = #'(left)
  2 4 d |
  \omit Fingering
  \unset fingeringOrientations
  8 g' g4 cis,2 |
}

Obviously the context-property `fingeringOrientations' needs a stencil
to deal with, thus unset it.

Cheers,
  Harm

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

Warnings when omitting fingering with overridden orientation

[Hinrik Örn Sigurðsson]

If I want to omit the fingering instructions for some part of a score or
the entire thing, I put "\omit Fingering" in the appopriate place. However,
it results in warnings ("programming error: Infinity or NaN encountered")
if "\set fingeringOrientations = #'(left)" has been previously done. The
PDF output is still correct though.

Test case:

\version "2.19.47"

\relative c' {
  \clef treble
  \key d \major
  \set fingeringOrientations = #'(left)
  2 4 d |
  \omit Fingering
  8 g' g4 cis,2 |
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Mystery Solved - Thanks

[Jacques Menu Muzhic]

Hello Pastor,

I wish all the musicians I’m playing with had bar numbers though, that would 
prevent a huge amount of time being lost during work sessions, when people 
count forward and/or backward to get at the right measure…

JM

> Le 1 sept. 2016 à 17:27, Simon Albrecht  a écrit :
> 
> On 25.08.2016 23:02, Pastor Neubauer wrote:
>> 
>> I am looking to get rid of the numbers that are automatically put above the 
>> staff as the start of each line when Lilypondauto breakslines. What are they 
>> called and can they be removed.
>> 
> 
> They are bar numbers, and you can remove them by inserting this in your file 
> at top level:
> 
> \layout {
>  \context {
>\Score
>\omit BarNumber
>  }
> }
> 
> HTH, Simon
> 
> ___
> 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: guitar scale diagram - change root

[David Kastrup]

bart deruyter  writes:

> It's strange to say, but lilypond is so good that most often scheme is
> not needed, which makes the actual use of scheme rare (for me at
> least), which in turn does not let me train it :-) .

That is sort of an intentional consequence of a lot of post 2.12 work.
There is an example for how to program in Scheme in some of the manuals,
and it had to be changed a few times until ending up basically with a
premise of "let's pretend we could not perfectly well do this in
LilyPond already without reverting to Scheme".  And when one has to
revert to Scheme, things map more directly to LilyPond than they used
to.

So you need Scheme less than previously, but when you do, it is not as
hard as it was once.

-- 
David Kastrup

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

Re: Horizontal positioning of rests

[David Kastrup]

David Wright  writes:

> On Fri 02 Sep 2016 at 06:55:31 (+0200), Remy CLAVERIE wrote:
>> Hi David,
>> What is the book that you named 'NM' ?
>
> Sorry,... The Notation Manual for LilyPond.

The "official" abbreviation for that is actually NR (as in "Notation
Reference", the proper title of the manual).

-- 
David Kastrup

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

Re: guitar scale diagram - change root

[bart deruyter]

Hey,

thanks for the help and I think I understand the explanation about Lisp.

I thought it would be something like this though, the error message made me
think that scheme wasn't able to read the variable,  I only did not know
why, now I do :-) .

Another problem for me is having usecases to learn scheme. I mean, I can
read other code and learn from it, but it doesn't let you think in a
'problem-solving' way because the solution already is there.

I learn best by having something concrete, like the above and ponder about
it to add new things. That way, I won't forget the solution because of the
effort I've put into it and because of the research I've put into it.
It's not productive at all to begin, but it does train your mind to think
as a computer, which in my experience does make it productive in the end.

It's strange to say, but lilypond is so good that most often scheme is not
needed, which makes the actual use of scheme rare (for me at least), which
in turn does not let me train it :-) .

Now I'll (lily)ponder on :-)

grtz,
Bart

http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 

2016-09-01 21:16 GMT+02:00 David Kastrup :

> bart deruyter  writes:
>
> > #(define-markup-command (scale-diagramm layout props arg1 arg2 start arg3
> > arg4) (list? integer? integer? number? integer?)
> >
> > (interpret-markup layout props
> >
> > (markup
> >
> >  (#:override (cons 'size arg3 )
> >
> > (#:override '(fret-diagram-details
> > . (
> >(finger-code . in-dot)
> >(number-type . arabic)
> >(label-dir   . -1)
> >(orientation . landscape)
> >(dot-radius  . 0.4)
> >(fret-count . arg4 )
> >(top-fret-thickness . 4)))
> >  #:fret-diagram-verbose
> > (fret-from-list arg1 '() arg2 start ))
> >
> > but then I get this error:
> >
> > Preprocessing graphical objects...fret-diagrams.scm <0>: In procedure >
> in
> > expression (> maxfret my-fret-count):
> >
> > fret-diagrams.scm <1>: Wrong type argument in position 2: arg4
> >
> >
> > Clearly it's an issue of 'type argument'. When I change fret-count to the
> > actual integer 12 instead of the variable arg4, it works. It is probably
> > something schemy I don't get...
>
> arg4 is a symbol in a quoted list, just like landscape, arabic, in-dot
> are.  If you replace the quote ' after #:override with a "quasiquote",
> namely the backward tick ` then you can "unquote" inside of the
> expression by preceding something with , the unquote character.  When
> an expression is unquoted, it is evaluated as normal and placed in the
> quoted list.  So you'd have
> (#:override `(fret-diagram-details
>   [...]
>   (fret-count . ,arg4)
>   [...]
>
> Lisp (and Scheme) do not actually have a program syntax.  Instead you
> enter the parse tree as a data structure, a nested list.  Every start of
> a list is a function call, every symbol is looked up as a variable
> (functions are just special variable values) and the remaining list
> elements are the argument of the function call, evaluated before
> calling.  Or, in case we are talking about a macro (or special form)
> instead of a function, passed unevaluated to the macro and the result of
> the macro call is then evaluated.
>
> That sounds awfully complex, but that's all there is to Scheme program
> structure.  The only "syntax" you have to deal with is actually for data
> entry, most of which consists of lists.
>
> Once you realise that Scheme does not have a program syntax, just a
> program _structure_ and that the syntax is only for data entry, it
> becomes obvious
> a) why Scheme feels so different from other languages
> b) why it is so great for macro/program manipulation
>
> --
> David Kastrup
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user