Re: Replacement for "parser"

[Hans Åberg]

> On 30 Jul 2016, at 19:09, Urs Liska  wrote:

>> Looking at the file I am actually using (with SMuFL glyphs), (*parser*)
>> is not needed, but Graham’s file regular.ly has a line
>> retune = #(define-music-function (parser location ET midc m)
>>  (rational? integer? ly:music?) m)
>> 
> 
> That's the old syntax. In current LilyPond you can (must?) leave out the 
> "parser location" variables because they are now transparently passed to the 
> function.
> If you need either of them you can access them through the (* *) calls.


The MIDI microtonality seems OK, though complicated: LilyPond with Graham’s 
regular.ly (as with Scala), sets the tuning note to C as though in E12 with A = 
440 Hz, so when retuned, A will have a different value. When working with a 
recording on a retuned keyboard, I set A = 440 Hz. The difference in E53 is 5.7 
c.



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

Re: Replacement for "parser"

[Hans Åberg]

> On 30 Jul 2016, at 15:47, Malte Meyn  wrote:

> Am 30.07.2016 um 14:53 schrieb Hans Åberg:
>> When using Graham Breed’s regular.ly, one writes a line like
>>  #(ly:parser-set-note-names parser SomePitchNames)
>> which worked in LilyPond 2.19.10. But in 2.19.45, there is an error:
>> error: GUILE signaled an error for the expression beginning here
>> newglyphs = #…
>> Unbound variable: parser
>> 
>> So the variable “parser” does not exist anymore, it seems. What is the 
>> replacement?
> 
> There is none. Just omit it like “parser location” in define-music-function.
> 
> #(ly:parser-set-note-names SomePitchNames)
> 
> This is what convert-ly does ;)

That one, I discovered, but “parser” must be there in another location.


> On 30 Jul 2016, at 16:48, David Kastrup  wrote:
> 
> convert-ly tends to have an answer for most questions like that.


Urs Liska already gave the answer in private email:

Use (*parser*) (and (*location*)).



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

Re: Dynamic with markup text function

[Jacques Menu Muzhic]

Hello Dimitris,

What would you like to align the dynamics with?

JM

> Le 29 juil. 2016 à 20:44, dtsmarin  a écrit :
> 
> Yes!!
> Thanks a lot!
> What about the alignment? Is it configurable like the other default objects?
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://lilypond.1069038.n5.nabble.com/Dynamic-with-markup-text-function-tp193242p193244.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: Replacement for "parser"

[Hans Åberg]

> On 30 Jul 2016, at 19:09, Urs Liska  wrote:

>> Looking at the file I am actually using (with SMuFL glyphs), (*parser*)
>> is not needed, but Graham’s file regular.ly has a line
>> retune = #(define-music-function (parser location ET midc m)
>>   (rational? integer? ly:music?) m)
>> 
> 
> That's the old syntax. In current LilyPond you can (must?) leave out the 
> "parser location" variables because they are now transparently passed to the 
> function.
> If you need either of them you can access them through the (* *) calls.

It compiles both ways, without the (* *), and I generate a MIDI file, though I 
need to check the microtonality.



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

Re: Replacement for "parser"

[David Kastrup]

Malte Meyn  writes:

> Am 30.07.2016 um 18:30 schrieb Hans Åberg:
>>
>>> On 30 Jul 2016, at 18:21, Malte Meyn  wrote:
>>
 That one, I discovered, but “parser” must be there in another location.
>>> Are you sure? input/regression/note-names.ly doesn’t have parser or
>>> (*parser*) anywhere.
>>
>> Looking at the file I am actually using (with SMuFL glyphs), (*parser*) is 
>> not needed, but Graham’s file regular.ly has a line
>>   retune = #(define-music-function (parser location ET midc m)
>> (rational? integer? ly:music?) m)
>
> This won’t work in 2.19.45, it has to be #(define-music-function (ET
> midc m) …

Says who?  It's nicer that way, but the old-style definition will most
certainly work as well.

> I just searched for the file and found it at
> http://x31eq.com/lilypond/ It looks like an older version of lilypond
> was used. But I don’t know which one because the author didn’t include
> a \version statement. This makes updating the code hard because you
> cannot simply use convert-ly.

convert-ly -f 2.18.0 -ed ...

Or any other version known to have worked.

> \version is nice to have. But maybe it should be made mandatory.

Maybe people should not ignore warnings.  A hard error still does not
seem warranted.

-- 
David Kastrup

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

Re: Replacement for "parser"

[Urs Liska]

Am 30. Juli 2016 18:30:57 MESZ, schrieb "Hans Åberg" :
>
>> On 30 Jul 2016, at 18:21, Malte Meyn  wrote:
>
>>> That one, I discovered, but “parser” must be there in another
>location.
>> Are you sure? input/regression/note-names.ly doesn’t have parser or
>(*parser*) anywhere.
>
>Looking at the file I am actually using (with SMuFL glyphs), (*parser*)
>is not needed, but Graham’s file regular.ly has a line
>  retune = #(define-music-function (parser location ET midc m)
>(rational? integer? ly:music?) m)
>

That's the old syntax. In current LilyPond you can (must?) leave out the 
"parser location" variables because they are now transparently passed to the 
function.
If you need either of them you can access them through the (* *) calls.

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

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

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

Re: Replacement for "parser"

[David Kastrup]

Hans Åberg  writes:

>> On 30 Jul 2016, at 18:21, Malte Meyn  wrote:
>
>>> That one, I discovered, but “parser” must be there in another location.
>> Are you sure? input/regression/note-names.ly doesn’t have parser or
>> (*parser*) anywhere.
>
> Looking at the file I am actually using (with SMuFL glyphs), (*parser*) is 
> not needed, but Graham’s file regular.ly has a line
>   retune = #(define-music-function (parser location ET midc m)
> (rational? integer? ly:music?) m)

Which works perfectly as-is since parser here is a function parameter
and define-music-function will accept this definition.  It also works
perfectly after using convert-ly (which will actually remove the
parser/location arguments).

I do not understand what the problem with running convert-ly and then
reporting any _actual_ remaining problems is.

-- 
David Kastrup

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

Re: Replacement for "parser"

[Malte Meyn]

Am 30.07.2016 um 18:30 schrieb Hans Åberg:



On 30 Jul 2016, at 18:21, Malte Meyn  wrote:



That one, I discovered, but “parser” must be there in another location.

Are you sure? input/regression/note-names.ly doesn’t have parser or (*parser*) 
anywhere.


Looking at the file I am actually using (with SMuFL glyphs), (*parser*) is not 
needed, but Graham’s file regular.ly has a line
  retune = #(define-music-function (parser location ET midc m)
(rational? integer? ly:music?) m)


This won’t work in 2.19.45, it has to be #(define-music-function (ET 
midc m) …


I just searched for the file and found it at http://x31eq.com/lilypond/ 
It looks like an older version of lilypond was used. But I don’t know 
which one because the author didn’t include a \version statement. This 
makes updating the code hard because you cannot simply use convert-ly.


\version is nice to have. But maybe it should be made mandatory.

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

Re: Replacement for "parser"

[Hans Åberg]

> On 30 Jul 2016, at 18:21, Malte Meyn  wrote:

>> That one, I discovered, but “parser” must be there in another location.
> Are you sure? input/regression/note-names.ly doesn’t have parser or 
> (*parser*) anywhere.

Looking at the file I am actually using (with SMuFL glyphs), (*parser*) is not 
needed, but Graham’s file regular.ly has a line
  retune = #(define-music-function (parser location ET midc m)
(rational? integer? ly:music?) m)



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

Solved (Re: How to set the beam positions manually?)

[Peter Terpstra]

Andrew Bernard wrote:

> Provide a minimal working example we can see.

Thank you so much for your interest in this problem, finally i could solve it 
like this.

\once\override Beam.positions = #'(-1 . -2.8) d16 [g,]
\once\override Beam.positions = #'(1 . -1)\stemUp g8\stemDown d' |
\once\override Beam.positions = #'(-1 . -2.8) e16 [g,]
\once\override Beam.positions = #'(1 . -1)\stemUp g8\stemDown e'

Kindly,

   Peter






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

Re: Replacement for "parser"

[Malte Meyn]

Am 30.07.2016 um 18:06 schrieb Hans Åberg:



On 30 Jul 2016, at 15:47, Malte Meyn  wrote:



Am 30.07.2016 um 14:53 schrieb Hans Åberg:

When using Graham Breed’s regular.ly, one writes a line like
 #(ly:parser-set-note-names parser SomePitchNames)
which worked in LilyPond 2.19.10. But in 2.19.45, there is an error:
error: GUILE signaled an error for the expression beginning here
newglyphs = #…
Unbound variable: parser

So the variable “parser” does not exist anymore, it seems. What is the 
replacement?


There is none. Just omit it like “parser location” in define-music-function.

#(ly:parser-set-note-names SomePitchNames)

This is what convert-ly does ;)


That one, I discovered, but “parser” must be there in another location.
Are you sure? input/regression/note-names.ly doesn’t have parser or 
(*parser*) anywhere.


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

Re: Replacement for "parser"

[David Kastrup]

Hans Åberg  writes:

> When using Graham Breed’s regular.ly, one writes a line like
>   #(ly:parser-set-note-names parser SomePitchNames)
> which worked in LilyPond 2.19.10. But in 2.19.45, there is an error:
> error: GUILE signaled an error for the expression beginning here
> newglyphs = #…
> Unbound variable: parser
>
> So the variable “parser” does not exist anymore, it seems. What is the
> replacement?

convert-ly tends to have an answer for most questions like that.

-- 
David Kastrup

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

Re: Replacement for "parser"

[Malte Meyn]

Am 30.07.2016 um 14:53 schrieb Hans Åberg:

When using Graham Breed’s regular.ly, one writes a line like
  #(ly:parser-set-note-names parser SomePitchNames)
which worked in LilyPond 2.19.10. But in 2.19.45, there is an error:
error: GUILE signaled an error for the expression beginning here
newglyphs = #…
Unbound variable: parser

So the variable “parser” does not exist anymore, it seems. What is the 
replacement?


There is none. Just omit it like “parser location” in define-music-function.

#(ly:parser-set-note-names SomePitchNames)

This is what convert-ly does ;)

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

Replacement for "parser"

[Hans Åberg]

When using Graham Breed’s regular.ly, one writes a line like
  #(ly:parser-set-note-names parser SomePitchNames)
which worked in LilyPond 2.19.10. But in 2.19.45, there is an error:
error: GUILE signaled an error for the expression beginning here
newglyphs = #…
Unbound variable: parser

So the variable “parser” does not exist anymore, it seems. What is the 
replacement?



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

Re: Adding a tempo indication in the middle of multiple voices mode

[David Kastrup]

Stephen Cox  writes:

> I want to add a tempo indication in the middle of some code that is in 
> multiple voices mode.
>
> For instance, using the example on page 48 of the “Learning” document, I 
> might want to add the indication “Faster” at the beginning of bar 2. The code 
> below in a file try.ly  gives the error 
>
> try.ly:5:22: error: markup outside of text script or \lyricmode
>r4 g g4. a8 | 
>  \markup{Faster}

I very much doubt that this is as written in "Learning" (all of the
examples actually compile).

At any rate, anything wrong with \tempo "Faster" here?

-- 
David Kastrup

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

Re: Adding a tempo indication in the middle of multiple voices mode

[Wols Lists]

On 30/07/16 10:36, Stephen Cox wrote:
> I want to add a tempo indication in the middle of some code that is in
> multiple voices mode.
> 
> For instance, using the example on page 48 of the “Learning” document, I
> might want to add the indication “Faster” at the beginning of bar 2. The
> code below in a file try.ly  gives the error 
> 
> try.ly :5:22: error: markup outside of text script or
> \lyricmode
>r4 g g4. a8 | 
>  \markup{Faster}
> 
> 
> This is surely a fairly common requirement and must be easy to do, but
> so far it has stumped me.
> 
What about "\tempo \markup { Faster }"?

Cheers,
Wol


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

Re: Adding a tempo indication in the middle of multiple voices mode

[Phil Holmes]

r4 g g4. a8 ^\markup{Faster} | 

--
Phil Holmes


  - Original Message - 
  From: Stephen Cox 
  To: lilypond-user@gnu.org 
  Sent: Saturday, July 30, 2016 10:36 AM
  Subject: Adding a tempo indication in the middle of multiple voices mode


  I want to add a tempo indication in the middle of some code that is in 
multiple voices mode.


  For instance, using the example on page 48 of the “Learning” document, I 
might want to add the indication “Faster” at the beginning of bar 2. The code 
below in a file try.ly gives the error 


  try.ly:5:22: error: markup outside of text script or \lyricmode
 r4 g g4. a8 | 
   \markup{Faster}




  This is surely a fairly common requirement and must be easy to do, but so far 
it has stumped me.


  Stephen




 \version “2.18.2" \key d \minor << {
   % Voice "1"
   r4 g g4. a8 | \markup{Faster}
   bes4 bes c bes |
   a2. r4 |
 } \\ {
   % Voice "2"
   d,2 d4 g |
   g4 g g8( a) g4 |
   fis2. s4 |
} >> 



--


  ___
  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

Adding a tempo indication in the middle of multiple voices mode

[Stephen Cox]

I want to add a tempo indication in the middle of some code that is in multiple 
voices mode.

For instance, using the example on page 48 of the “Learning” document, I might 
want to add the indication “Faster” at the beginning of bar 2. The code below 
in a file try.ly  gives the error 

try.ly:5:22: error: markup outside of text script or \lyricmode
   r4 g g4. a8 | 
 \markup{Faster}


This is surely a fairly common requirement and must be easy to do, but so far 
it has stumped me.

Stephen


 \version “2.18.2"
 \key d \minor
 << {
   % Voice "1"
   r4 g g4. a8 | \markup{Faster}
   bes4 bes c bes |
   a2. r4 |
 } \\ {
   % Voice "2"
   d,2 d4 g |
   g4 g g8( a) g4 |
   fis2. s4 |
} >> ___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user