Re: Exclude single notes from ChordNames?

[sg2002]

I understand that I can have separate music entity for chord names. I 
was asking for ways to avoid doing that. The most obvious option is 
writing a filter function that would replace everything in the input 
except the proper chords with rests, I mentioned that previously. Just 
decided to ask, maybe there's some other way, like some clever use of 
some ChordName settings.



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

Instructions to install lilypond onto Raspberry Pi

[Vivyan]

Hi

I need to run lilypond on the raspberry pi. I can't finsd any sources that
say how to? I would typically use the command sudo apt-get install .., which
has worked for frescobaldi but not lilypond?

Please may I have instructions to install lilypond onto the raspberrry pi, 

Many thanks




--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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

Re:Preventing a cautionary accidental

[David Sumbler]

-Original Message-
From: Malte Meyn 
Am 17.09.18 um 23:38 schrieb David Sumbler:
> What is the simplest way of preventing the accidental from being
> printed?

\once \omit Accidental



-Original Message-
From: Aaron Hill 
You could change the accidental style temporarily:


   e''8 fs gs a b c d e fs | g8 fs e d c b a \once \accidentalStyle 
forget g fs



Thank you for both of these suggestions.  I certainly should have
thought of '\omit Accidental', but at least now I have a clearer idea
of exactly what '\omit' does, having looked again at NR 5.4.7.

'\once \accidentalStyle forget' is interesting, but I had not
considered that the accidentalStyle could be changed momentarily in
this way.  Nor had I realized that there are so many more accidental
styles available since the last time I looked at NR 1.1.3.

All in all a useful learning experience for me.  Thanks again.

David

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

Re: Instructions to install lilypond onto Raspberry Pi

[Urs Liska]

Am 18.09.2018 um 09:37 schrieb Vivyan:

Hi

I need to run lilypond on the raspberry pi. I can't finsd any sources that
say how to? I would typically use the command sudo apt-get install .., which
has worked for frescobaldi but not lilypond?


That means that the exact Linux distribution you are running doesn't 
include the LilyPond package.
But it's still easy to do: just download the distribution from the 
LilyPond website (either http://lilypond.org/unix.html for the "stable" 
release or http://lilypond.org/development.html for the "development" 
release (which is usually preferrable).


If you run the raspberry without graphic interface you can identify the 
download link from the website and download with wget.

Then run the downloaded install script with sh downloaded-file-name.

HTH
Urs



Please may I have instructions to install lilypond onto the raspberrry pi,

Many thanks




--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
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: Shape the angle of a broken hairpin's first part

[Urs Liska]

Hi Harm,

thank you very much!


Am 17.09.2018 um 22:35 schrieb Thomas Morley:

2018-09-17 12:05 GMT+02:00 Thomas Morley :

2018-09-17 11:55 GMT+02:00 Urs Liska :

thanks for this, which gives me a handle to the first part of the hairpin at
least.

But my problem is not solved with the 'height property.

[...]


See my updated example

[...]

I'll have a look in the evening, now I have to run for my regular job ...

Cheers,
   Harm

Hi Urs,

as said before you'll need to go for the 'stencil.
Though, ly:hairpin::print, the default-stencil, is coded in C++. There
the defaults-heights for broken hairpins are set to 1/3 and 2/3 of
'height.
Thus we need a scheme-rewrite of the stencil-procedure to reset them.
Below I slightly extend a coding by David Nalesnik from
https://lists.gnu.org/archive/html/lilypond-user/2018-02/msg00181.html

Btw, the rest of the linked thread is very interesting as well:
Once you have a scheme-rewrite it's possible to add a plethora of
other features...

Back on topic.
Attached you'll find David's coding. My addition is to add a
'broken-heights-property.
Now you can adjust the values and call the scheme-stencil afterwards,
instead of the default-stencil.


This will work for my case - although it's somewhat ridiculous to 
include such a massive file just to fix one graphic issue.
I think this is something that should be user-settable. Maybe a property 
like yours as a native Hairpin property and/or a setting of the maximum 
angle hairpin lines may have. The latter would also be a viable setting 
(as opposed to minimum-length) to prevent those crippled too-short 
hairpins that are often hard to spot. I think I'll post a feature request.


Best
Urs



Cheers,
   Harm



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

Re: Shape the angle of a broken hairpin's first part

[Urs Liska]

Am 18.09.2018 um 11:09 schrieb Urs Liska:

Hi Harm,

thank you very much!


Am 17.09.2018 um 22:35 schrieb Thomas Morley:

2018-09-17 12:05 GMT+02:00 Thomas Morley :

2018-09-17 11:55 GMT+02:00 Urs Liska :
thanks for this, which gives me a handle to the first part of the 
hairpin at

least.

But my problem is not solved with the 'height property.

[...]


See my updated example

[...]

I'll have a look in the evening, now I have to run for my regular 
job ...


Cheers,
   Harm

Hi Urs,

as said before you'll need to go for the 'stencil.
Though, ly:hairpin::print, the default-stencil, is coded in C++. There
the defaults-heights for broken hairpins are set to 1/3 and 2/3 of
'height.
Thus we need a scheme-rewrite of the stencil-procedure to reset them.
Below I slightly extend a coding by David Nalesnik from
https://lists.gnu.org/archive/html/lilypond-user/2018-02/msg00181.html

Btw, the rest of the linked thread is very interesting as well:
Once you have a scheme-rewrite it's possible to add a plethora of
other features...

Back on topic.
Attached you'll find David's coding. My addition is to add a
'broken-heights-property.
Now you can adjust the values and call the scheme-stencil afterwards,
instead of the default-stencil.


This will work for my case - although it's somewhat ridiculous to 
include such a massive file just to fix one graphic issue.
I think this is something that should be user-settable. Maybe a 
property like yours as a native Hairpin property and/or a setting of 
the maximum angle hairpin lines may have. The latter would also be a 
viable setting (as opposed to minimum-length) to prevent those 
crippled too-short hairpins that are often hard to spot. I think I'll 
post a feature request.


Best
Urs


Ah, I forgot to ask one thing: 'broken-heights is overridden with two 
values, but I don't see the second one making any difference. What is 
that about?


Urs





Cheers,
   Harm



___
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: Shape the angle of a broken hairpin's first part

[Thomas Morley]

2018-09-18 11:13 GMT+02:00 Urs Liska :
>
>
> Am 18.09.2018 um 11:09 schrieb Urs Liska:
>>
>> Hi Harm,
>>
>> thank you very much!
>>
>>
>> Am 17.09.2018 um 22:35 schrieb Thomas Morley:
>>>
>>> 2018-09-17 12:05 GMT+02:00 Thomas Morley :

 2018-09-17 11:55 GMT+02:00 Urs Liska :
>
> thanks for this, which gives me a handle to the first part of the
> hairpin at
> least.
>
> But my problem is not solved with the 'height property.

 [...]

> See my updated example

 [...]

 I'll have a look in the evening, now I have to run for my regular job
 ...

 Cheers,
Harm
>>>
>>> Hi Urs,
>>>
>>> as said before you'll need to go for the 'stencil.
>>> Though, ly:hairpin::print, the default-stencil, is coded in C++. There
>>> the defaults-heights for broken hairpins are set to 1/3 and 2/3 of
>>> 'height.
>>> Thus we need a scheme-rewrite of the stencil-procedure to reset them.
>>> Below I slightly extend a coding by David Nalesnik from
>>> https://lists.gnu.org/archive/html/lilypond-user/2018-02/msg00181.html
>>>
>>> Btw, the rest of the linked thread is very interesting as well:
>>> Once you have a scheme-rewrite it's possible to add a plethora of
>>> other features...
>>>
>>> Back on topic.
>>> Attached you'll find David's coding. My addition is to add a
>>> 'broken-heights-property.
>>> Now you can adjust the values and call the scheme-stencil afterwards,
>>> instead of the default-stencil.
>>
>>
>> This will work for my case - although it's somewhat ridiculous to include
>> such a massive file just to fix one graphic issue.
>> I think this is something that should be user-settable. Maybe a property
>> like yours as a native Hairpin property and/or a setting of the maximum
>> angle hairpin lines may have. The latter would also be a viable setting (as
>> opposed to minimum-length) to prevent those crippled too-short hairpins that
>> are often hard to spot. I think I'll post a feature request.
>>
>> Best
>> Urs
>
>
> Ah, I forgot to ask one thing: 'broken-heights is overridden with two
> values, but I don't see the second one making any difference. What is that
> about?
>
> Urs

For decrescendo the first value determines the height for all but the
last broken hairpin-end.
For decrescendo the second value determines the height for all but the
first broken hairpin-start.

For crescendo the first value determines the height for all but first
broken hairpin-start.
For crescendo the second value determines the height for all but last
broken hairpin-end.

Internally these values are multiplied with the 'height-value.

See:
{
  \override Hairpin.broken-heights = #'(0.2 5)
  \override Hairpin.stencil = #hairpin::print-scheme
  c'1\>
  \break
  c'1 \break
  s2 c'\!
}

{
  \override Hairpin.broken-heights = #'(0.2 5)
  \override Hairpin.stencil = #hairpin::print-scheme
  c'1\<
  \break
  c'1 \break
  s2 c'\!
}

Cheers,
  Harm

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

Re: Shape the angle of a broken hairpin's first part

[Urs Liska]

Am 18.09.2018 um 11:49 schrieb Thomas Morley:

2018-09-18 11:13 GMT+02:00 Urs Liska :


Am 18.09.2018 um 11:09 schrieb Urs Liska:

Hi Harm,

thank you very much!


Am 17.09.2018 um 22:35 schrieb Thomas Morley:

2018-09-17 12:05 GMT+02:00 Thomas Morley :

2018-09-17 11:55 GMT+02:00 Urs Liska :

thanks for this, which gives me a handle to the first part of the
hairpin at
least.

But my problem is not solved with the 'height property.

[...]


See my updated example

[...]

I'll have a look in the evening, now I have to run for my regular job
...

Cheers,
Harm

Hi Urs,

as said before you'll need to go for the 'stencil.
Though, ly:hairpin::print, the default-stencil, is coded in C++. There
the defaults-heights for broken hairpins are set to 1/3 and 2/3 of
'height.
Thus we need a scheme-rewrite of the stencil-procedure to reset them.
Below I slightly extend a coding by David Nalesnik from
https://lists.gnu.org/archive/html/lilypond-user/2018-02/msg00181.html

Btw, the rest of the linked thread is very interesting as well:
Once you have a scheme-rewrite it's possible to add a plethora of
other features...

Back on topic.
Attached you'll find David's coding. My addition is to add a
'broken-heights-property.
Now you can adjust the values and call the scheme-stencil afterwards,
instead of the default-stencil.


This will work for my case - although it's somewhat ridiculous to include
such a massive file just to fix one graphic issue.
I think this is something that should be user-settable. Maybe a property
like yours as a native Hairpin property and/or a setting of the maximum
angle hairpin lines may have. The latter would also be a viable setting (as
opposed to minimum-length) to prevent those crippled too-short hairpins that
are often hard to spot. I think I'll post a feature request.

Best
Urs


Ah, I forgot to ask one thing: 'broken-heights is overridden with two
values, but I don't see the second one making any difference. What is that
about?

Urs

For decrescendo the first value determines the height for all but the
last broken hairpin-end.
For decrescendo the second value determines the height for all but the
first broken hairpin-start.

For crescendo the first value determines the height for all but first
broken hairpin-start.
For crescendo the second value determines the height for all but last
broken hairpin-end.

Internally these values are multiplied with the 'height-value.

See:
{
   \override Hairpin.broken-heights = #'(0.2 5)
   \override Hairpin.stencil = #hairpin::print-scheme
   c'1\>
   \break
   c'1 \break
   s2 c'\!
}

{
   \override Hairpin.broken-heights = #'(0.2 5)
   \override Hairpin.stencil = #hairpin::print-scheme
   c'1\<
   \break
   c'1 \break
   s2 c'\!
}

Cheers,
   Harm


Ah, OK. But that didn't take any effect in the earlier example since 
that only applied the override to the first sibling. If I use a 
crescendo instead then only the second value takes effect.


Thanks again
Urs

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

Re: Instructions to install lilypond onto Raspberry Pi

[Federico Bruni]

Il giorno mar 18 set 2018 alle 10:54, Urs Liska  
ha scritto:



Am 18.09.2018 um 09:37 schrieb Vivyan:

Hi

I need to run lilypond on the raspberry pi. I can't finsd any 
sources that
say how to? I would typically use the command sudo apt-get install 
.., which

has worked for frescobaldi but not lilypond?


That means that the exact Linux distribution you are running doesn't 
include the LilyPond package.
But it's still easy to do: just download the distribution from the 
LilyPond website (either http://lilypond.org/unix.html for the 
"stable" release or http://lilypond.org/development.html for the 
"development" release (which is usually preferrable).




I don't think it's going to work, because IIRC Raspberry Pi runs an 
architecture (some kind of arm) for which we do not provide an 
installer.


Recently another user willing to use a development version instead of 
the stable of his debian repository asked how to easily build lilypond 
on Raspberry.





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

Sample document to show music fonts

[Urs Liska]

Hi all,

I'm going to pick up the work on Frescobaldi's "Show available fonts" 
dialog, which I had started giving a fundamental overhaul before the 
holidays.


I'm looking for a nice template document that can be used to demonstrate 
a music font. It should not be too "heavy", and ideally it would show 
off the font at a glance within the space seen in the attached screenshot.


Just like the Score Wizard Preview dialog the space will automatically 
get scroll bars so the document *may* be larger but I'd prefer if one 
can see the essentials at first sight.


I'd be glad about some "community contributions" here.

Best
Urs

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

New

[Bernhard Kleine]

I would like to render the 'molto' in the example from the documentation
in italics. I have looked into the documentation to "New
" but to no avail.

moltoF = #(make-dynamic-script
(markup #:normal-text "molto"
#:dynamic "f"))
\relative c' {
  16 
  2..\moltoF
}

Something like 
legato = #(make-dynamic-script (markup #:normal-text  "legato" )) 
in the header helped to bring in the Dynamics the legato etc. on line with \f 
etc. . 
But now I would like to have the 'legato' in italics.

Obviously I can not deconstruct the instructions to achieve that tool.

Please show me How!
Bernhard

-- 
spitzhalde9
D-79853 lenzkirch
bernhard.kle...@gmx.net
www.b-kleine.com, www.urseetal.net
-
thunderbird mit enigmail
GPG schlüssel: D5257409
fingerprint:
08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09



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

Re: New

[Torsten Hämmerle]

Bernhard Kleine wrote
> Something like 
> legato = #(make-dynamic-script (markup #:normal-text  "legato" )) 
> in the header helped to bring in the Dynamics the legato etc. on line with
> \f etc. . 
> But now I would like to have the 'legato' in italics.
> 
> Obviously I can not deconstruct the instructions to achieve that tool.
> 
> Please show me How!


Hi Bernhard,

All the "#:…." instructions in scheme are just the same as the "\…"
instructions in ordinary markup.
Keeping that in mind, #:normal-text is nothing else but \normal-text and it
is needed to switch back to normal text from the special \dynamic font used
for p, mf, fff, etc.

So, if you want the "legato" in italics, simply add #:italic

  legato = #(make-dynamic-script (markup #:normal-text #:italic "legato" )) 

C'est tout ! 

HTH,
Torsten




--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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

Re: New

[Malte Meyn]

Am 18.09.18 um 13:07 schrieb Bernhard Kleine:
I would like to render the 'molto' in the example from the documentation 
in italics. I have looked into the documentation to "New 
" but to no avail.


moltoF = #(make-dynamic-script
 (markup #:normal-text "molto"
 #:dynamic "f"))


Just add #:italic after #:normal-text. You can also use LilyPond markup 
syntax instead of Scheme markup syntax:



%
\version "2.19.82"

moltoF = #(make-dynamic-script (markup #:normal-text #:italic "molto" 
#:dynamic "f"))


piuFmarkup = \markup { \normal-text \italic "più" \dynamic "f" }
piuF = #(make-dynamic-script piuFmarkup)

Fpossibile = #(make-dynamic-script #{ \markup { \dynamic "f" 
\normal-text \italic "possibile" } #})


\relative c' {
  16 
  2..\moltoF
  16 
  2..\piuF
  16 
  2..\Fpossibile
}



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

Re: New

[Malte Meyn]

Am 18.09.18 um 13:07 schrieb Bernhard Kleine:
I would like to render the 'molto' in the example from the documentation 
in italics. I have looked into the documentation to "New 
" but to no avail.


moltoF = #(make-dynamic-script
 (markup #:normal-text "molto"
 #:dynamic "f"))
\relative c' {
   16 
   2..\moltoF
}


If you need this more often you might consider using 
“easy-custom-dynamics” from openlilylib: 
https://github.com/openlilylib/snippets/tree/master/input-shorthands/easy-custom-dynamics


Then this is as simple as

%
\relative c '{
  16 
  2..\dynamic "molto f"
}
%

Italics are used here automatically.

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

Re: Sample document to show music fonts

[Andrew Bernard]

Hi Urs,

I would like to set the glyph set as per Abraham Lee's foundry website:

https://www.musictypefoundry.com/product/mtf-cadence

Much rather this than a piece of music. Any sample of music will be
irrelevant to some large subset of people. For example, my new complexity
stuff would just annoy people, and I don't want to see a sample of Brahms
(no disrespect to Brahms!!).

Perhaps you could put music examples on a separate website, not in the
program.

Andrew


On Tue, 18 Sep 2018 at 20:52, Urs Liska  wrote:

>
> I'm looking for a nice template document that can be used to demonstrate
> a music font. It should not be too "heavy", and ideally it would show
> off the font at a glance within the space seen in the attached screenshot.
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Instructions to install lilypond onto Raspberry Pi

[Vivyan]

did they have any success building lilypond?



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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

Re: Instructions to install lilypond onto Raspberry Pi

[Karlin High]

On 9/18/2018 7:05 AM, Vivyan wrote:

did they have any success building lilypond?


I don't know if this is the exact thread that Federico Bruni had in 
mind, but it should be close.




There, Peter Engelbert was trying to compile LilyPond from source. 
(Adding him to CC on this post.) He did report that adding the Debian 8 
Jessie repository to his APT sources.list allowed a successful install 
of LilyPond 2.18.2 on Raspberry Pi. Newer Debian repositories were 
missing LilyPond due to a required-version conflict with the Guile package.

--
Karlin High
Missouri, USA

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

Re: Instructions to install lilypond onto Raspberry Pi

[Jamie Ching]

Hi,
Your best bet is to compile from source code itself if the distribution
doesn't have Lilypond. As it sounds like you're using a Debian-based
distribution, check if "sudo apt-get build-dep lilypond" works; if it
doesn't, you will need to install the required development packages via
apt-get. Be wary that one of Lilypond's dependencies, TeX, takes up quite a
bit of space on the microSD card.

There is a set of instructions as to how to compile Lilypond on the
website: http://lilypond.org/doc/v2.18/Documentation/contributor/compiling
Below is a shortcut way to install Lilypond quickly. Refer to the above if
needed.

Standard procedure to install programs from source code:
- download the stable version of the Lilypond source code, extract via "tar
-xvf", and "cd" into the directory of the extracted folder.
- install "build-essential" via apt-get - build-essential is a collection
of libraries, compilers, and other tools used to help compile programs from
source code.
- run "./configure" and do install any missing dependencies (usually marked
with a "-dev" at the end); keep looping until "./configure" finishes
successfully.
- run "make" then "sudo make install"; the processes may take time to
finish, depending on the version of the Raspberry Pi.

Hope that helps. Happy engraving.

Best wishes,
Jamie

P.S. : I've noted that the compiling link is broken here on the source code
page: http://lilypond.org/source.html

On Tue, 18 Sep 2018 at 01:39, Vivyan  wrote:

> Hi
>
> I need to run lilypond on the raspberry pi. I can't finsd any sources that
> say how to? I would typically use the command sudo apt-get install ..,
> which
> has worked for frescobaldi but not lilypond?
>
> Please may I have instructions to install lilypond onto the raspberrry pi,
>
> Many thanks
>
>
>
>
> --
> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
>
> ___
> 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

Example for trio

[Данил Костенков]

Hello!
I need to have a example for 3 instrument which doing using lilypond code. Tell 
me please, where I can find this?
Thank you in advance.
All the best, Danil.

Отправлено с iPhone
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Example for trio

[Malte Meyn]

Am 18.09.18 um 12:40 schrieb Данил Костенков:

Hello!
I need to have a example for 3 instrument which doing using lilypond code. Tell 
me please, where I can find this?
Thank you in advance.
All the best, Danil.


Minimal example:

%%% BEGIN
<<
\new Staff { c' }
\new Staff { c' }
\new Staff { c' }
>>
%%% END

What do you need apart from that?

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

Re: Instructions to install lilypond onto Raspberry Pi

[Federico Bruni]

Il giorno mar 18 set 2018 alle 14:53, Karlin High 
 ha scritto:

On 9/18/2018 7:05 AM, Vivyan wrote:

did they have any success building lilypond?


I don't know if this is the exact thread that Federico Bruni had in 
mind, but it should be close.






Actually, I meant this one (it's an Android tablet, arm processor):
http://lilypond.1069038.n5.nabble.com/How-to-create-an-installer-from-the-Lilypond-build-tree-td215616.html#a215747




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

Lyluatex

[foxfanfare]

Hi all,

I'm beginning my first steps in the world of LaTeX and I'm currently trying
to figure out how Lyluatex works. I'm using TeX Live (and TeXworks for
editing) on Windows.

I made this simple document:

\documentclass{article}
\usepackage{lyluatex}
\begin{document}
Bonjour, j'\'edite en \LaTeX!

\begin{lilypond}
\relative c' { c d e f g a b c }
\end{lilypond}

\end{document}

But when I compile it (either via TeXworks or with the command "lualatex
-shell-escape DOCUMENT.TEX", I get this in the console:

This is LuaTeX, Version 1.07.0 (TeX Live 2018/W32TeX)
 system commands enabled.
(./test.tex
LaTeX2e <2018-04-01> patch level 5
(using cache: C:/texlive/2018/texmf-var/luatex-cache/generic)
luaotfload | main : initialization completed in 0.502 seconds
(c:/texlive/2018/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(c:/texlive/2018/texmf-dist/tex/latex/base/size10.clo(load luc:
C:/texlive/2018
/texmf-var/luatex-cache/generic/fonts/otl/lmroman10-regular.luc)))
(c:/texlive/2018/texmf-dist/tex/luatex/lyluatex/lyluatex.sty
(c:/texlive/2018/texmf-dist/tex/luatex/luatexbase/luatexbase.sty
(c:/texlive/2018/texmf-dist/tex/luatex/ctablestack/ctablestack.sty))
(c:/texlive/2018/texmf-dist/tex/latex/xkeyval/xkeyval.sty
(c:/texlive/2018/texmf-dist/tex/generic/xkeyval/xkeyval.tex
(c:/texlive/2018/texmf-dist/tex/generic/xkeyval/xkvutils.tex
(c:/texlive/2018/texmf-dist/tex/generic/xkeyval/keyval.tex
(c:/texlive/2018/texmf-dist/tex/latex/graphics/graphicx.sty
(c:/texlive/2018/texmf-dist/tex/latex/graphics/graphics.sty
(c:/texlive/2018/texmf-dist/tex/latex/graphics/trig.sty)
(c:/texlive/2018/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)
(c:/texlive/2018/texmf-dist/tex/latex/graphics-def/luatex.def)))
(c:/texlive/2018/texmf-dist/tex/latex/minibox/minibox.sty
(c:/texlive/2018/texmf-dist/tex/latex/l3kernel/expl3.sty
(c:/texlive/2018/texmf-dist/tex/latex/l3kernel/expl3-code.tex)
(c:/texlive/2018/texmf-dist/tex/latex/l3kernel/l3pdfmode.def)))
(c:/texlive/2018/texmf-dist/tex/latex/environ/environ.sty
(c:/texlive/2018/texmf-dist/tex/latex/trimspaces/trimspaces.sty))
(c:/texlive/2018/texmf-dist/tex/latex/currfile/currfile.sty
(c:/texlive/2018/texmf-dist/tex/latex/oberdiek/kvoptions.sty
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/kvsetkeys.sty
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/etexcmds.sty
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/ifluatex.sty
(c:/texlive/2018/texmf-dist/tex/latex/filehook/filehook.sty))
(c:/texlive/2018/texmf-dist/tex/latex/pdfpages/pdfpages.sty
(c:/texlive/2018/texmf-dist/tex/latex/base/ifthen.sty)
(c:/texlive/2018/texmf-dist/tex/latex/tools/calc.sty)
(c:/texlive/2018/texmf-dist/tex/latex/eso-pic/eso-pic.sty
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/atbegshi.sty
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/ifpdf.sty))
(c:/texlive/2018/texmf-dist/tex/latex/xcolor/xcolor.sty
(c:/texlive/2018/texmf-dist/tex/latex/graphics-cfg/color.cfg)))
(c:/texlive/2018/texmf-dist/tex/latex/pdfpages/ppluatex.def))
(c:/texlive/2018/texmf-dist/tex/latex/metalogo/metalogo.sty
(c:/texlive/2018/texmf-dist/tex/generic/ifxetex/ifxetex.sty))) (./test.aux)
(c:/texlive/2018/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
[Loading MPS to PDF converter (version 2006.09.02).]
) (c:/texlive/2018/texmf-dist/tex/latex/oberdiek/epstopdf-base.sty
(c:/texlive/2018/texmf-dist/tex/latex/oberdiek/grfext.sty
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/kvdefinekeys.sty))
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/pdftexcmds.sty)
(c:/texlive/2018/texmf-dist/tex/latex/latexconfig/epstopdf-sys.cfg))
(c:/texlive/2018/texmf-dist/tex/latex/oberdiek/pdflscape.sty
(c:/texlive/2018/texmf-dist/tex/latex/graphics/lscape.sty))(load luc:
C:/texliv
e/2018/texmf-var/luatex-cache/generic/fonts/otl/lmroman7-regular.luc)(load
luc:

C:/texlive/2018/texmf-var/luatex-cache/generic/fonts/otl/lmsans10-regular.luc)
(load luc:
C:/texlive/2018/texmf-var/luatex-cache/generic/fonts/otl/lmmono10-re
gular.luc)'lilypond' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.
c:/texlive/2018/texmf-dist/tex/latex/base/ltluatex.lua:109:
Module lyluatex Error: LilyPond could not be started.
(lyluatex) Please check that LuaLaTeX is started with the
(lyluatex) --shell-escape option, and that 'program'
(lyluatex) points to a valid LilyPond executable.
(lyluatex) on input line 8

stack traceback:
[C]: in function 'error'
c:/texlive/2018/texmf-dist/tex/latex/base/ltluatex.lua:109: in
function 
(...tail calls...)
c:/texlive/2018/texmf-dist/scripts/lyluatex/lyluatex.lua:898: in
function 'lil
ypond_version'
c:/texlive/2018/texmf-dist/scripts/lyluatex/lyluatex.lua:1113: in
function 'ru
n_lilypond'
c:/texli

Re: Lyluatex

[Urs Liska]

Am 18.09.2018 um 15:56 schrieb foxfanfare:

Hi all,

I'm beginning my first steps in the world of LaTeX and I'm currently trying
to figure out how Lyluatex works. I'm using TeX Live (and TeXworks for
editing) on Windows.

I made this simple document:

\documentclass{article}
\usepackage{lyluatex}
\begin{document}
Bonjour, j'\'edite en \LaTeX!

\begin{lilypond}
\relative c' { c d e f g a b c }
\end{lilypond}

\end{document}

But when I compile it (either via TeXworks or with the command "lualatex
-shell-escape DOCUMENT.TEX", I get this in the console:


Did you correctly quote that here? I see -shell-escape instead of 
--shell-escape.




This is LuaTeX, Version 1.07.0 (TeX Live 2018/W32TeX)
  system commands enabled.
...

c:/texlive/2018/texmf-dist/tex/latex/base/ltluatex.lua:109:
Module lyluatex Error: LilyPond could not be started.
(lyluatex) Please check that LuaLaTeX is started with the
(lyluatex) --shell-escape option, and that 'program'
(lyluatex) points to a valid LilyPond executable.
(lyluatex) on input line 8

...


I don't understand why. I also tried to change :
\usepackage[program=C:/Program Files
(x86)/LilyPond/usr/bin/lilypond.exe]{lyluatex} but this didn't solve the
problem.


I'm not sure about the behaviour on Windows, but I'd assume you have to 
wrap a path that includes spaces in curly brackets:


  [program={C:/Program Files (x86)/LilyPond/usr/bin/lilypond.exe}]


Could someone please point me in the right direction to make it work?


Is that the right direction?

HTH
Urs


Thanks!



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
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: Lyluatex

[Malte Meyn]

Am 18.09.18 um 15:56 schrieb foxfanfare:

Bonjour, j'\'edite en \LaTeX!


I think that Urs’s answer could be the right direction and sadly cannot 
help further. But as you’re a LaTeX novice here is an off-topic hint:
Since you use LuaLaTeX you can use utf8 characters in input. So you can 
write j’édite insted of j'\'edite ;)


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

Re: Lyluatex

[foxfanfare]

Urs Liska-3 wrote
> Did you correctly quote that here? I see -shell-escape instead of 
> --shell-escape.

Hi Urs, 
Actually, I just copied what was written in the GitHub documentation:
https://github.com/jperon/lyluatex

I tried with the -- and also with 
\usepackage[program={C:/Program Files
(x86)/LilyPond/usr/bin/lilypond-windows.exe}]{lyluatex}, and yet again:

D:\tex>lualatex --shell-escape test.tex
This is LuaTeX, Version 1.07.0 (TeX Live 2018/W32TeX)
 system commands enabled.
(./test.tex
LaTeX2e <2018-04-01> patch level 5
(using cache: C:/texlive/2018/texmf-var/luatex-cache/generic)
luaotfload | main : initialization completed in 0.263 seconds
(c:/texlive/2018/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(c:/texlive/2018/texmf-dist/tex/latex/base/size10.clo(load luc:
C:/texlive/2018
/texmf-var/luatex-cache/generic/fonts/otl/lmroman10-regular.luc)))
(c:/texlive/2018/texmf-dist/tex/luatex/lyluatex/lyluatex.sty
(c:/texlive/2018/texmf-dist/tex/luatex/luatexbase/luatexbase.sty
(c:/texlive/2018/texmf-dist/tex/luatex/ctablestack/ctablestack.sty))
(c:/texlive/2018/texmf-dist/tex/latex/xkeyval/xkeyval.sty
(c:/texlive/2018/texmf-dist/tex/generic/xkeyval/xkeyval.tex
(c:/texlive/2018/texmf-dist/tex/generic/xkeyval/xkvutils.tex
(c:/texlive/2018/texmf-dist/tex/generic/xkeyval/keyval.tex
(c:/texlive/2018/texmf-dist/tex/latex/graphics/graphicx.sty
(c:/texlive/2018/texmf-dist/tex/latex/graphics/graphics.sty
(c:/texlive/2018/texmf-dist/tex/latex/graphics/trig.sty)
(c:/texlive/2018/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)
(c:/texlive/2018/texmf-dist/tex/latex/graphics-def/luatex.def)))
(c:/texlive/2018/texmf-dist/tex/latex/minibox/minibox.sty
(c:/texlive/2018/texmf-dist/tex/latex/l3kernel/expl3.sty
(c:/texlive/2018/texmf-dist/tex/latex/l3kernel/expl3-code.tex)
(c:/texlive/2018/texmf-dist/tex/latex/l3kernel/l3pdfmode.def)))
(c:/texlive/2018/texmf-dist/tex/latex/environ/environ.sty
(c:/texlive/2018/texmf-dist/tex/latex/trimspaces/trimspaces.sty))
(c:/texlive/2018/texmf-dist/tex/latex/currfile/currfile.sty
(c:/texlive/2018/texmf-dist/tex/latex/oberdiek/kvoptions.sty
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/kvsetkeys.sty
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/etexcmds.sty
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/ifluatex.sty
(c:/texlive/2018/texmf-dist/tex/latex/filehook/filehook.sty))
(c:/texlive/2018/texmf-dist/tex/latex/pdfpages/pdfpages.sty
(c:/texlive/2018/texmf-dist/tex/latex/base/ifthen.sty)
(c:/texlive/2018/texmf-dist/tex/latex/tools/calc.sty)
(c:/texlive/2018/texmf-dist/tex/latex/eso-pic/eso-pic.sty
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/atbegshi.sty
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/ifpdf.sty))
(c:/texlive/2018/texmf-dist/tex/latex/xcolor/xcolor.sty
(c:/texlive/2018/texmf-dist/tex/latex/graphics-cfg/color.cfg)))
(c:/texlive/2018/texmf-dist/tex/latex/pdfpages/ppluatex.def))
(c:/texlive/2018/texmf-dist/tex/latex/metalogo/metalogo.sty
(c:/texlive/2018/texmf-dist/tex/generic/ifxetex/ifxetex.sty))) (./test.aux)
(c:/texlive/2018/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
[Loading MPS to PDF converter (version 2006.09.02).]
) (c:/texlive/2018/texmf-dist/tex/latex/oberdiek/epstopdf-base.sty
(c:/texlive/2018/texmf-dist/tex/latex/oberdiek/grfext.sty
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/kvdefinekeys.sty))
(c:/texlive/2018/texmf-dist/tex/generic/oberdiek/pdftexcmds.sty)
(c:/texlive/2018/texmf-dist/tex/latex/latexconfig/epstopdf-sys.cfg))
(c:/texlive/2018/texmf-dist/tex/latex/oberdiek/pdflscape.sty
(c:/texlive/2018/texmf-dist/tex/latex/graphics/lscape.sty))(load luc:
C:/texliv
e/2018/texmf-var/luatex-cache/generic/fonts/otl/lmroman7-regular.luc)(load
luc:

C:/texlive/2018/texmf-var/luatex-cache/generic/fonts/otl/lmsans10-regular.luc)
(load luc:
C:/texlive/2018/texmf-var/luatex-cache/generic/fonts/otl/lmmono10-re
gular.luc)'C:/Program' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.
c:/texlive/2018/texmf-dist/tex/latex/base/ltluatex.lua:109:
Module lyluatex Error: LilyPond could not be started.
(lyluatex) Please check that LuaLaTeX is started with the
(lyluatex) --shell-escape option, and that 'program'
(lyluatex) points to a valid LilyPond executable.
(lyluatex) on input line 8

stack traceback:
[C]: in function 'error'
c:/texlive/2018/texmf-dist/tex/latex/base/ltluatex.lua:109: in
function 
(...tail calls...)
c:/texlive/2018/texmf-dist/scripts/lyluatex/lyluatex.lua:898: in
function 'lil
ypond_version'
c:/texlive/2018/texmf-dist/scripts/lyluatex/lyluatex.lua:1113: in
function 'ru
n_lilypond'
c:/texlive/2018/texmf-dist/scripts/lyluatex/lyluatex.lua:1094: in
function 'pr
ocess'
[\directlua]:1: in 

Re: Hacklily now supports LilyPond 2.19.82

[Federico Bruni]

Added to the tracker:
https://sourceforge.net/p/testlilyissues/issues/5418/


Il giorno lun 17 set 2018 alle 16:40, Joshua Netterfield 
 ha scritto:

Hi Federico,

I think sharing Hacklily on the Easier Editing page would be great! 
Though never perfect, I feel that it is mature enough to be helpful. 
Let me know if there is anything you would like to see before listing 
it.


Thanks!


Joshua Netterfield



On Mon, Sep 17, 2018 at 9:40 AM -0400, "Federico Bruni" 
 wrote:



Hey Joshua

I had a quick look at hacklily and it seems pretty cool!
When you think the project is mature enough, it may be mentioned 
here:

http://lilypond.org/easier-editing.html



Il giorno lun 17 set 2018 alle 15:19, Joshua Netterfield
 ha scritto:
> Hello all,
>
> Hacklily, an online LilyPond editor, now supports LilyPond 2.19.82.
> To use it, go to https://www.hacklily.org and make sure your song
> includes a 2.19 version statement (e.g., \version "2.19.82"). I
> intend to support the most recent stable and unstable versions 
going

> forward.
>
> As always, please let me know if you have any feedback by replying 
to

> this email, emailing me directly, or creating an issue on GitHub
> (https://github.com/hacklily/hacklily). Patches are also welcome.
>
> Best,
> Joshua Netterfield
> https://www.hacklily.org
>
>
>
> ___
> 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: Lyluatex

[R. Padraic Springuel]

Well, LuaTeX is still having trouble finding the executable, just in this case 
it’s looking for C:\Program.  That, of course, is not a complete path to the 
lilypond executable.  The space in the path is clearly not being escaped 
correctly.  Try adding quotes around the complete path or edit your PATH 
variable so that `lilypond` is recognized without the complete path. 

✝️✝️✝️✝️✝️✝️✝️✝️✝️✝️✝️✝️✝️✝️✝️✝️✝️✝️✝️✝️✝️✝️✝️✝️
Br. Samuel, OSB 
(R. Padraic Springuel)
St. Anselm’s Abbey 
4501 South Dakota Ave, NE
Washington, DC, 20017
202-269-2300
(c) 202-853-7036

PAX ☧ ΧΡΙΣΤΟΣ

> On Sep 18, 2018, at 10:36 AM, foxfanfare  wrote:
> 
> Urs Liska-3 wrote
>> Did you correctly quote that here? I see -shell-escape instead of 
>> --shell-escape.
> 
> Hi Urs, 
> Actually, I just copied what was written in the GitHub documentation:
> https://github.com/jperon/lyluatex
> 
> I tried with the -- and also with 
> \usepackage[program={C:/Program Files
> (x86)/LilyPond/usr/bin/lilypond-windows.exe}]{lyluatex}, and yet again:
> 
> D:\tex>lualatex --shell-escape test.tex
> This is LuaTeX, Version 1.07.0 (TeX Live 2018/W32TeX)
> system commands enabled.
> (./test.tex
> LaTeX2e <2018-04-01> patch level 5
> (using cache: C:/texlive/2018/texmf-var/luatex-cache/generic)
> luaotfload | main : initialization completed in 0.263 seconds
> (c:/texlive/2018/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
> (c:/texlive/2018/texmf-dist/tex/latex/base/size10.clo(load luc:
> C:/texlive/2018
> /texmf-var/luatex-cache/generic/fonts/otl/lmroman10-regular.luc)))
> (c:/texlive/2018/texmf-dist/tex/luatex/lyluatex/lyluatex.sty
> (c:/texlive/2018/texmf-dist/tex/luatex/luatexbase/luatexbase.sty
> (c:/texlive/2018/texmf-dist/tex/luatex/ctablestack/ctablestack.sty))
> (c:/texlive/2018/texmf-dist/tex/latex/xkeyval/xkeyval.sty
> (c:/texlive/2018/texmf-dist/tex/generic/xkeyval/xkeyval.tex
> (c:/texlive/2018/texmf-dist/tex/generic/xkeyval/xkvutils.tex
> (c:/texlive/2018/texmf-dist/tex/generic/xkeyval/keyval.tex
> (c:/texlive/2018/texmf-dist/tex/latex/graphics/graphicx.sty
> (c:/texlive/2018/texmf-dist/tex/latex/graphics/graphics.sty
> (c:/texlive/2018/texmf-dist/tex/latex/graphics/trig.sty)
> (c:/texlive/2018/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)
> (c:/texlive/2018/texmf-dist/tex/latex/graphics-def/luatex.def)))
> (c:/texlive/2018/texmf-dist/tex/latex/minibox/minibox.sty
> (c:/texlive/2018/texmf-dist/tex/latex/l3kernel/expl3.sty
> (c:/texlive/2018/texmf-dist/tex/latex/l3kernel/expl3-code.tex)
> (c:/texlive/2018/texmf-dist/tex/latex/l3kernel/l3pdfmode.def)))
> (c:/texlive/2018/texmf-dist/tex/latex/environ/environ.sty
> (c:/texlive/2018/texmf-dist/tex/latex/trimspaces/trimspaces.sty))
> (c:/texlive/2018/texmf-dist/tex/latex/currfile/currfile.sty
> (c:/texlive/2018/texmf-dist/tex/latex/oberdiek/kvoptions.sty
> (c:/texlive/2018/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)
> (c:/texlive/2018/texmf-dist/tex/generic/oberdiek/kvsetkeys.sty
> (c:/texlive/2018/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
> (c:/texlive/2018/texmf-dist/tex/generic/oberdiek/etexcmds.sty
> (c:/texlive/2018/texmf-dist/tex/generic/oberdiek/ifluatex.sty
> (c:/texlive/2018/texmf-dist/tex/latex/filehook/filehook.sty))
> (c:/texlive/2018/texmf-dist/tex/latex/pdfpages/pdfpages.sty
> (c:/texlive/2018/texmf-dist/tex/latex/base/ifthen.sty)
> (c:/texlive/2018/texmf-dist/tex/latex/tools/calc.sty)
> (c:/texlive/2018/texmf-dist/tex/latex/eso-pic/eso-pic.sty
> (c:/texlive/2018/texmf-dist/tex/generic/oberdiek/atbegshi.sty
> (c:/texlive/2018/texmf-dist/tex/generic/oberdiek/ifpdf.sty))
> (c:/texlive/2018/texmf-dist/tex/latex/xcolor/xcolor.sty
> (c:/texlive/2018/texmf-dist/tex/latex/graphics-cfg/color.cfg)))
> (c:/texlive/2018/texmf-dist/tex/latex/pdfpages/ppluatex.def))
> (c:/texlive/2018/texmf-dist/tex/latex/metalogo/metalogo.sty
> (c:/texlive/2018/texmf-dist/tex/generic/ifxetex/ifxetex.sty))) (./test.aux)
> (c:/texlive/2018/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
> [Loading MPS to PDF converter (version 2006.09.02).]
> ) (c:/texlive/2018/texmf-dist/tex/latex/oberdiek/epstopdf-base.sty
> (c:/texlive/2018/texmf-dist/tex/latex/oberdiek/grfext.sty
> (c:/texlive/2018/texmf-dist/tex/generic/oberdiek/kvdefinekeys.sty))
> (c:/texlive/2018/texmf-dist/tex/generic/oberdiek/pdftexcmds.sty)
> (c:/texlive/2018/texmf-dist/tex/latex/latexconfig/epstopdf-sys.cfg))
> (c:/texlive/2018/texmf-dist/tex/latex/oberdiek/pdflscape.sty
> (c:/texlive/2018/texmf-dist/tex/latex/graphics/lscape.sty))(load luc:
> C:/texliv
> e/2018/texmf-var/luatex-cache/generic/fonts/otl/lmroman7-regular.luc)(load
> luc:
> 
> C:/texlive/2018/texmf-var/luatex-cache/generic/fonts/otl/lmsans10-regular.luc)
> (load luc:
> C:/texlive/2018/texmf-var/luatex-cache/generic/fonts/otl/lmmono10-re
> gular.luc)'C:/Program' n’est pas reconnu en tant que commande interne
> ou externe, un programme exécutable ou un fichier de commandes.
> c:/texlive/2018/texmf-dist/tex/latex/bas

Re: Lyluatex

[foxfanfare]

R. Padraic Springuel wrote
> Well, LuaTeX is still having trouble finding the executable, just in this
> case it’s looking for C:\Program.  That, of course, is not a complete path
> to the lilypond executable.  The space in the path is clearly not being
> escaped correctly.  Try adding quotes around the complete path or edit
> your PATH variable so that `lilypond` is recognized without the complete
> path. 

Hi Padraic,
Thank you for the tip, I could get it to work with:

\usepackage[program={"C:/Program Files
(x86)/LilyPond/usr/bin/lilypond.exe"}]{lyluatex}

A new world is now opening to me :-) This problem could maybe be written in
the GitHub repository for Windows users no?
Also -shell or --shell works the same for me. Do you know how to add this
command in TeXworks if I want to compile with it?


Malte Meyn-3 wrote
> I think that Urs’s answer could be the right direction and sadly cannot 
> help further. But as you’re a LaTeX novice here is an off-topic hint:
> Since you use LuaLaTeX you can use utf8 characters in input. So you can 
> write j’édite insted of j'\'edite ;)

You're right, thanks! I'm currently reading some manual, but most of those I
found were old and never mentioned Lualatex. For french users, they always
seemed to use some specific packages for that...



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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

Re: Lyluatex

[foxfanfare]

foxfanfare wrote
> Do you know how to add this
> command in TeXworks if I want to compile with it?

Don't bother, I found it!




--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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

Re: Example for trio

[Simon Albrecht]

On 18.09.2018 12:40, Данил Костенков wrote:

Hello!
I need to have a example for 3 instrument which doing using lilypond code. Tell 
me please, where I can find this?


For getting started with LilyPond, there really isn’t much of a sensible 
way other than working through the Learning Manual thoroughly, at least 
once.  
If you’ve done that, you’ll hopefully know more about the concepts you 
need for typesetting music for three instruments.


Best, Simon

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

Tempo declaration on different staves

[Bernhard Kleine]

I have the following minimal example (from Frescobaldi with some
eliminations). What I cannot achieve is that the

\tempo 4=96

becomes effective on the organpart. It works only with the global
declaration. Removing this, the other tempo declaration are not visible.
Please show me how to deal with different tempo declarations on
different staves.

Thanks a lot

Bernhard

> \version "2.19.82"
> \language "deutsch"
>
> \header {
>   % Voreingestellte LilyPond-Tagline entfernen
>   tagline = ##f
> }
>
> \paper { #(set-paper-size "a4") }
>
> global = { \key c \major \time 4/4 \tempo 4=96 }
>
> soprano = \relative c'' { \global c^"Solenne" \tempo 4=96 }
>
> alto = \relative c' { \global }
>
> tenor = \relative c' { \global c }
>
> bass = \relative c { \global }
>
> verse = \lyricmode { test }
>
> right = \relative c'' { \global c^"Solenne" \tempo 4=96 }
>
> left = \relative c' { \global c }
>
> pedal = \relative c { \global c }
>
> choirPart = \new ChoirStaff <<
>   \new Staff \with {
>     instrumentName = \markup \center-column { "Sopran" "Alt" }
>   } <<
>     \new Voice = "soprano" { \voiceOne \soprano }
>     \new Voice = "alto" { \voiceTwo \alto }
>   >>
>   \new Lyrics \with {
>     \override VerticalAxisGroup #'staff-affinity = #CENTER
>   } \lyricsto "soprano" \verse
>   \new Staff \with {
>     instrumentName = \markup \center-column { "Tenor" "Bass" }
>   } <<
>     \clef bass
>     \new Voice = "tenor" { \voiceOne \tenor }
>     \new Voice = "bass" { \voiceTwo \bass }
>   >>
> >>
>
> organPart = <<
>   \new PianoStaff \with {
>     instrumentName = "Orgel"
>     shortInstrumentName = "Org."
>   } <<
>     \new Staff = "right" \right
>     \new Staff = "left" { \clef bass \left }
>     \new Staff = "pedal" { \clef bass \pedal }
>   >>
> >>
>
> \score {
>   <<
>     \choirPart
>     \organPart
>   >>
>   \layout { }
> }

-- 
spitzhalde9
D-79853 lenzkirch
bernhard.kle...@gmx.net
www.b-kleine.com, www.urseetal.net
-
thunderbird mit enigmail
GPG schlüssel: D5257409
fingerprint:
08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09




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

Re: Sample document to show music fonts

[Aaron Hill]

On 2018-09-18 4:58 am, Andrew Bernard wrote:

Hi Urs,

I would like to set the glyph set as per Abraham Lee's foundry website:

https://www.musictypefoundry.com/product/mtf-cadence

Much rather this than a piece of music. Any sample of music will be
irrelevant to some large subset of people. For example, my new 
complexity
stuff would just annoy people, and I don't want to see a sample of 
Brahms

(no disrespect to Brahms!!).

Perhaps you could put music examples on a separate website, not in the
program.

On Tue, 18 Sep 2018 at 20:52, Urs Liska  wrote:


I'm looking for a nice template document that can be used to 
demonstrate

a music font. It should not be too "heavy", and ideally it would show
off the font at a glance within the space seen in the attached 
screenshot.


Another idea: make it customizable.  I doubt there is ever going to be a 
one-size-fits-all preview template for fonts.  Of course, it's more work 
to support this, but providing you are shelling out to LilyPond behind 
the scenes to render the preview live, then allowing the end-user to 
provide a custom template would address concerns from folks who work in 
more esoteric branches of notation.



-- Aaron Hill

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

Re: Tempo declaration on different staves

[Kieren MacMillan]

Hi Bernhard,

> Please show me how to deal with different tempo declarations on different 
> staves.

Here’s one way. (Note that I also <<>>'ed the \global variable into each 
*staff* context in the score, rather than into each note variable definition; 
personally, I think that is better coding style, for many reasons.)

Hope this helps!
Kieren.

\version "2.19.80"
\language "deutsch"

\header {
  % Voreingestellte LilyPond-Tagline entfernen
  tagline = ##f
}

\paper { #(set-paper-size "a4") }

global = {
  \key c \major
  \time 4/4
  \tempo 4=96
}

soprano = \relative c'' {
  c
}

alto = \relative c' {
}

tenor = \relative c' {
  c
}

bass = \relative c {
}

verse = \lyricmode { test }

right = \relative c'' {
  c
}

left = \relative c' {
  \clef bass
  c
}

pedal = \relative c {
  \clef bass
  c
}

choirPart = \new ChoirStaff <<
  \new Staff \with {
\consists "Metronome_mark_engraver"
instrumentName = \markup \center-column { "Sopran" "Alt" }
  } <<
\new Voice = "soprano" << \global { \voiceOne \soprano } >>
\new Voice = "alto"<< \global  { \voiceTwo \alto } >>
  >>
  \new Lyrics \with {
\override VerticalAxisGroup #'staff-affinity = #CENTER
  } \lyricsto "soprano" \verse
  \new Staff \with {
instrumentName = \markup \center-column { "Tenor" "Bass" }
  } <<
\clef bass
\new Voice = "tenor" << \global { \voiceOne \tenor } >>
\new Voice = "bass" << \global { \voiceTwo \bass } >>
  >>
>>


organPart = <<
  \new PianoStaff \with {
instrumentName = "Orgel"
shortInstrumentName = "Org."
  } <<
\new Staff = "right" \with { \consists "Metronome_mark_engraver" } << 
\global \right >>
\new Staff = "left" << \global \left >>
\new Staff = "pedal" << \global \pedal >>
  >>
>>


\score {
  <<
\choirPart
\organPart
  >>
  \layout {
\context {
  \Score
  \remove "Metronome_mark_engraver"
}
  }
}


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:variables for specific kinds of markup?

[Flaming Hakama by Elaine]

>
> From: Marc Evanstein 
> To: David Kastrup 
> Cc: lilypond-user@gnu.org
> Date: Mon, 17 Sep 2018 18:14:31 +
> Subject: Re: variables for specific kinds of markup?
> Thanks so much – changing it to define-event-function worked perfectly. Is
> a markup considered an "event" rather than "music"? Was
> define-music-function somehow returning that event attached to empty music
> or something?
>
> At any rate, glad to hear that this is getting simpler in the near future,
> and many thanks for all the help!
>
> September 17, 2018 8:01 AM, "David Kastrup"  wrote:
>
> > "Marc Evanstein (formerly Evans)"  writes:
> >
> >> Hi all,
> >>
> >> I'm trying to create a variable to handle a certain type of markup
> >> text. For instance, I'd like percussion strikings to be in small caps
> >> above the staff, and what I really want is to define some sort of
> >> macro that replaces all instances of "\striking { theText }" with
> >> "^\markup\smallCaps { theText }".
> >>
> >> The following clearly doesn't work (much as I would like it to):
> >>
> >> striking = ^\markup\smallCaps
> >
> > Current master will allow
> >
> > striking = ^\markup \smallCaps \etc
> >
> >> From searching around, it seems like I need to define a function using
> >> scheme. I tried this:
> >>
> >> striking = #(define-music-function (parser location text)
> >> (string?)
> >> #{
> >> ^\markup\smallCaps { #text }
> >> #})
> >>
> >> ... and while the single line "\striking mallet" seems to render the
> >> word mallet as a smallCaps markup above a dummy staff, when I try to
> >> incorporate it into a series of notes, e.g.:
> >>
> >> {c'4 \striking mallet d'4 e'4 f'4 }
> >>
> >> I get an "error: unexpected post-event". What exactly does that mean?
> >
> > Current master would have worked as expected for this use...
> >
> > At any rate, you are pretty close (whether we are talking about 2.18 or
> > 2.19). Just use define-event-function instead of define-music-function
> > .
> >
> > And rejoice that LilyPond will have fewer stumbling blocks in the near
> > future. Or at least will be better at hiding the stumbling blocks so
> > you'll just get hit by them when digging deeper.
> >
> > --
> > David Kastrup
>
>
>
You could also consider writing your function to use
the empty chord construct <> as an anchor for your markup.

That might make it more bulletproof since you avoid having
to care about the data type of the previous element.

\version "2.19.15"

striking = #(define-music-function
(parser location text)
(string?)
#{
 <>^\markup\smallCaps { #text }
#}
)

{c'4 \striking mallet d'4 e'4 f'4 }


HTH,

Elaine Alt
415 . 341 .4954   "*Confusion is
highly underrated*"
ela...@flaminghakama.com
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lyrics and other markup in the wrong order

[Bernhard Kleine]

I have now with the same piece the problem that the lyrics above the
line and the markup text are not as I would like it. the lyrics show
below the markup. When I shuffled the markup upwards the raise the
lyrics did not fall below but were equally raised. How to correct that?

Thanks for your patience!

Bernhard

\version "2.19.82"
\language "deutsch"
\layout {
  \context {
    \Voice
    \consists "Melody_engraver"
    \override Stem #'neutral-direction = #'()
  }
  \context {
    \Staff \RemoveEmptyStaves
    % To use the setting globally, uncomment the following line:
    \override VerticalAxisGroup.remove-first = ##t
  }
}
global = {
  \key d \major
  \time 4/4
  \tempo Grave 4 = 56
  \autoBeamOff
  \partial 8
  \override MultiMeasureRest.staff-position = #0
  \override Rest.staff-position = #0
}

soprano = \relative c'' {
  \dynamicUp
  r8 R1 r2 r4 h~^\markup { \raise #6 {mit schmerzlichem Ausdruck}  }| h8
h h ([a]) g4 r8 g |
}


alto = \relative c'' {
  \dynamicUp
  s8 s1 s2 s4\f h~ | h8 h h ([a]) g4 s8 e |
}

tenor = \relative c' {
  r8 R1 r2 r4 h~ | h8 h h ([a]) g4 r8 h |

}

bass = \relative c' {
  s8 s1 s2 s4 h~\f | h8 h h ([a]) g4 s8 e |
}

sopranoVerse = \lyricmode {
  A -- gnus De -- i, qui tol -- lis
}

altoVerse = \lyricmode {
  A -- gnus De -- i, qui tol -- lis
}

tenorVerse = \lyricmode {
  A -- gnus De -- i, qui tol -- lis
}

bassVerse = \lyricmode {
  A -- gnus De -- i, qui tol -- lis
}

rightOne = \relative c'' {
  8 ( | 4) r8 8 ( 4) r8  ( | 4. ) r8
r2 R1
}

rightTwo = \relative c'' {
  8 ( | 4 ) s8 8 ( 4) s8 8 ( 4.)  s8 s2
| s1 |
}

leftOne = \relative c {
  r8 | R1 r2 2~ | 2. r4|
}

leftTwo = \relative c {
  s8 s1*2
}

pedal = \relative c, {
  r8 | R1 | r2 e2~ | e2. r4

}


choirPart = \new ChoirStaff <<
  \new Staff = "frauen" \with {
    \consists "Metronome_mark_engraver"
    instrumentName = \markup \center-column { "Sopran" "Alt" }
  } <<
    \new Voice = "soprano" << \global { \voiceOne \soprano } >>
    \new Lyrics \with { alignAboveContext = "frauen" } {
  \lyricsto "soprano" {
    \sopranoVerse
  }
    }
    \new Voice = "alto"<< \global  { \voiceTwo \alto } >>
    \addlyrics { \altoVerse }
  >>
  \new Staff = "maenner" \with {
    instrumentName = \markup \center-column { "Tenor" "Bass" }
  } <<
    \clef bass
    \new Voice = "tenor" << \global { \voiceOne \tenor } >>
    \new Lyrics \with { alignAboveContext = "maenner" } {
  \lyricsto "tenor" {
    \tenorVerse
  }
    }
    \new Voice = "bass" << \global { \voiceTwo \bass } >>
    \addlyrics { \bassVerse }
  >>
>>

organPart = <<
  \new PianoStaff \with {
    instrumentName = "Orgel"
    shortInstrumentName = "Org."

  } <<
    \new Staff = "right" \with { \consists "Metronome_mark_engraver" }
<< \global \rightOne \\ \global \rightTwo >>
    \new Staff = "left" { \clef bass << global \leftOne \\ \global
\leftTwo >> }
    \new Staff = "pedal" { \clef bass \global \pedal }

  >>
>>

\score {
  \header {
    title = "Franziskusmesse"
    subtitle = "für Chor und Orgel"
    tagline = "gesetzt von Bernhard Kleine 2018"

    piece = "Agnus Dei"
  }
  <<
    \choirPart
    \organPart
  >>
  \layout {
    \context {
  \Score
  \remove "Metronome_mark_engraver"
    }
  }
}


Am 18.09.2018 um 21:57 schrieb Kieren MacMillan:
> Hi Bernhard,
>
>> Thanks for the  "metronom engraver".
>> How would I have found it in the documentation?
> Searching for "tempo" (and similar) would lead you to 
> .
>  At the bottom of that section, you would find “Internals Reference: 
> MetronomeMark”, with the link leading to 
> . Right 
> at the top of that page, it says "MetronomeMark objects are created by: 
> Metronome_mark_engraver".
>
> Hope that helps!
> Kieren.
> 
>
> Kieren MacMillan, composer
> ‣ website: www.kierenmacmillan.info
> ‣ email: i...@kierenmacmillan.info
>

-- 
spitzhalde9
D-79853 lenzkirch
bernhard.kle...@gmx.net
www.b-kleine.com, www.urseetal.net
-
thunderbird mit enigmail
GPG schlüssel: D5257409
fingerprint:
08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09




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

New to Lilypond, how do i change the left hand clef from bass clef to treble clef right at the beginning of the piece?

[tripleamia]

I'm working in Frescobaldi, so I have the right hand and left hand, and for
the first two measures of the left hand I need to switch from bass to treble
before any notes. I'm having difficulty explaining but you see in the
picture what I'm trying to do. What is the least complicated way to do this?



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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

I'm sorry I feel stupid asking so many questions. How do I make fingering go OUTSIDE of the staff?

[Mia Heaton]

I know you have the note-fingering but when i do this it goes inside the 
staff and it looks crowded and ugly. Is there any way I can make it go 
outside?



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

Re: Example for trio

[Carl Sorensen]

On 9/18/18, 11:09 AM, "Simon Albrecht"  wrote:

On 18.09.2018 12:40, Данил Костенков wrote:
> Hello!
> I need to have a example for 3 instrument which doing using lilypond 
code. Tell me please, where I can find this?

For getting started with LilyPond, there really isn’t much of a sensible 
way other than working through the Learning Manual thoroughly, at least 
once.  
If you’ve done that, you’ll hopefully know more about the concepts you 
need for typesetting music for three instruments.


You could also explore the score wizard in Frescobaldi, which has some 
excellent templates in my opinion.

HTH,

Carl
 

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

Re: New to Lilypond, how do i change the left hand clef from bass clef to treble clef right at the beginning of the piece?

[Aaron Hill]

On 2018-09-18 2:55 pm, tripleamia wrote:


I'm working in Frescobaldi, so I have the right hand and left hand, and 
for
the first two measures of the left hand I need to switch from bass to 
treble

before any notes. I'm having difficulty explaining but you see in the
picture what I'm trying to do. What is the least complicated way to do 
this?


Here is an ugly hack that achieves what you want by inserting a very 
small moment to allow the initial bass clef to not be immediately 
overridden by the treble clef:



\version "2.19.82"
hack = { \cadenzaOn s128 \cadenzaOff }
\new PianoStaff { <<
  \new Staff {
\clef treble \key d \major \time 3/4 \hack
fis''4. e''8 d''4 | a'4. g'8 fis'4 | }
  \new Staff {
\clef bass \key d \major \time 3/4 \hack
\clef treble d''4 a'8 fis' d'4 |
\clef bass d'4 a8 fis d4 | } >> }


That hack in mind, what I would do is not try to duplicate the reference 
engraving exactly and rather just go with the treble clef from the 
beginning.  This would visually simplify the piece and give you back a 
little width in the line as you don't need the otherwise useless bass 
clef.


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

Re: I'm sorry I feel stupid asking so many questions. How do I make fingering go OUTSIDE of the staff?

[Aaron Hill]

On 2018-09-18 3:01 pm, Mia Heaton wrote:

I know you have the note-fingering but when i do this it goes inside
the staff and it looks crowded and ugly. Is there any way I can make
it go outside?


Hi Mia,

You should be able to use either the _ or ^ prefix to request that a 
specific fingering go below or above rather than rely on the default 
behavior.  You can also change the fingeringOrientations to exclusively 
prefer a direction by default.



\version "2.19.82"
{ 4 % g's fingering would prefer to be below
  \set fingeringOrientations = #'(up) 4 }


-- Aaron Hill

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

Re: Sample document to show music fonts

[Urs Liska]

Am 18.09.2018 um 21:08 schrieb Aaron Hill:

On 2018-09-18 4:58 am, Andrew Bernard wrote:

Hi Urs,

I would like to set the glyph set as per Abraham Lee's foundry website:

https://www.musictypefoundry.com/product/mtf-cadence

Much rather this than a piece of music. Any sample of music will be
irrelevant to some large subset of people. For example, my new 
complexity
stuff would just annoy people, and I don't want to see a sample of 
Brahms

(no disrespect to Brahms!!).

Perhaps you could put music examples on a separate website, not in the
program.

On Tue, 18 Sep 2018 at 20:52, Urs Liska  wrote:


I'm looking for a nice template document that can be used to 
demonstrate

a music font. It should not be too "heavy", and ideally it would show
off the font at a glance within the space seen in the attached 
screenshot.


Another idea: make it customizable.  I doubt there is ever going to be 
a one-size-fits-all preview template for fonts.  Of course, it's more 
work to support this, but providing you are shelling out to LilyPond 
behind the scenes to render the preview live, then allowing the 
end-user to provide a custom template would address concerns from 
folks who work in more esoteric branches of notation.


Although compelling I think this would be over the top.
a) if someone wants to see music fonts with specific music they can 
simply use an existing or create a new document and test the fonts with it.
b) These sample documents will usually not be generated live but are 
cached, so in 95% of the cases (except the first time a new font is 
installed) an existing PDF will be loaded.


So I think I'll go with the suggestion to create some sort of "glyph 
matrix", showing the font elements without context.


I think the updated dialog will be used much more regularly than the 
previous one, not only because the available (music but especially text) 
fonts are now nicely listed and displayed, but also because it will 
additionally provide the tools to *select* fonts (i.e. create the 
appropriate LilyPond code).


Urs




-- Aaron Hill

___
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: New to Lilypond, how do i change the left hand clef from bass clef to treble clef right at the beginning of the piece?

[Mark Stephen Mrotek]

Triple,

Why not just start with a treble clef?

Mark

-Original Message-
From: lilypond-user
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
tripleamia
Sent: Tuesday, September 18, 2018 2:56 PM
To: lilypond-user@gnu.org
Subject: New to Lilypond, how do i change the left hand clef from bass clef
to treble clef right at the beginning of the piece?


I'm working in Frescobaldi, so I have the right hand and left hand, and for
the first two measures of the left hand I need to switch from bass to treble
before any notes. I'm having difficulty explaining but you see in the
picture what I'm trying to do. What is the least complicated way to do this?



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
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: Sample document to show music fonts

[Abraham Lee]

Hi, Urs!
On Tue, Sep 18, 2018 at 4:46 PM Urs Liska  wrote:

>
>
> Am 18.09.2018 um 21:08 schrieb Aaron Hill:
> > On 2018-09-18 4:58 am, Andrew Bernard wrote:
> >> Hi Urs,
> >>
> >> I would like to set the glyph set as per Abraham Lee's foundry website:
> >>
> >> https://www.musictypefoundry.com/product/mtf-cadence
> >>
> >> Much rather this than a piece of music. Any sample of music will be
> >> irrelevant to some large subset of people. For example, my new
> >> complexity
> >> stuff would just annoy people, and I don't want to see a sample of
> >> Brahms
> >> (no disrespect to Brahms!!).
> >>
> >> Perhaps you could put music examples on a separate website, not in the
> >> program.
> >>
> >> On Tue, 18 Sep 2018 at 20:52, Urs Liska  wrote:
> >>>
> >>> I'm looking for a nice template document that can be used to
> >>> demonstrate
> >>> a music font. It should not be too "heavy", and ideally it would show
> >>> off the font at a glance within the space seen in the attached
> >>> screenshot.
> >
> > Another idea: make it customizable.  I doubt there is ever going to be
> > a one-size-fits-all preview template for fonts.  Of course, it's more
> > work to support this, but providing you are shelling out to LilyPond
> > behind the scenes to render the preview live, then allowing the
> > end-user to provide a custom template would address concerns from
> > folks who work in more esoteric branches of notation.
>
> Although compelling I think this would be over the top.
> a) if someone wants to see music fonts with specific music they can
> simply use an existing or create a new document and test the fonts with it.
> b) These sample documents will usually not be generated live but are
> cached, so in 95% of the cases (except the first time a new font is
> installed) an existing PDF will be loaded.
>
> So I think I'll go with the suggestion to create some sort of "glyph
> matrix", showing the font elements without context.
>
> I think the updated dialog will be used much more regularly than the
> previous one, not only because the available (music but especially text)
> fonts are now nicely listed and displayed, but also because it will
> additionally provide the tools to *select* fonts (i.e. create the
> appropriate LilyPond code).
>

My 2 cents...

A font preview is a font preview and the best, in my opinion, are those
that show something in a practical context. In this case, an image of a
single or grand staff showing 2-3 bars of a marginally interesting looking
passage would be much more representative of what actual music would look
like than a simple string or matrix of glyphs, though there's nothing wrong
with that either. I agree that trying to make it a "live" preview is not
worth it until LilyPond can be made to run "live".

That's what I would prefer to see. Take that for what it's worth.

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

Re: New to Lilypond, how do i change the left hand clef from bass clef to treble clef right at the beginning of the piece?

[Simon Albrecht]

On 19.09.2018 01:13, Mark Stephen Mrotek wrote:

Triple,

Why not just start with a treble clef?


In piano music, one avoids that because pianists are so used to the 
usual clef combination that other constellations are somewhat likely to 
be overlooked.


Best, Simon

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

Latest lilypond stable release?

[H. S. Teoh]

According to the website (lilypond.org), the latest stable release is
2.18.2, and the unstable release is 2.19.82.

However, I've been using the latest version from git, and it claims to
be version 2.21.0.  So, what happened to 2.20.*?  Why does the git
version claim to be 2.21.0?

More pertinently, what version should I be using on the \version line?


T

-- 
Unix was not designed to stop people from doing stupid things, because that 
would also stop them from doing clever things. -- Doug Gwyn

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

Re: Latest lilypond stable release?

[Simon Albrecht]

On 19.09.2018 01:46, H. S. Teoh wrote:

According to the website (lilypond.org), the latest stable release is
2.18.2, and the unstable release is 2.19.82.

However, I've been using the latest version from git, and it claims to
be version 2.21.0.  So, what happened to 2.20.*?  Why does the git
version claim to be 2.21.0?

More pertinently, what version should I be using on the \version line?


2.19.82 is already a prerelease for 2.20.0, since we’re in the process 
leading up to this next stable release. IIUC, this is why the git 
version is called 2.21.0, because only some of the changes applied now 
will still make it into the stable release and most will be 2.21 material.
It is customary for those who compile from current master to use a 
2.21.0 version statement indeed.


Best, Simon

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

Re: lyrics and other markup in the wrong order

[Kieren MacMillan]

Hi Bernhard,

> When I shuffled the markup upwards the raise the lyrics
> did not fall below but were equally raised. How to correct that?

There may be a way using #'outside-staff-priority, but I was unable to find it.

One (crude) way of solving your problem is:

  r8 R1 r2 r4 h~-\tweak extra-offset #'(0 . 5) ^\markup \with-dimensions-from 
\null { "mit schmerzlichem Ausdruck" }   | h8

Hope that 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: [ANN] LilyQuick 0.95beta - Quick note Lilypond entry using MIDI for Linux

[Chad Linsley]

+1 for a cross-platform of LilyQuick!

In fact, would there be any interest in including it in Denemo or
Frescobaldi? It’s absolutely brilliant and I would love to start using it
(Mac user).

On Sun, Aug 13, 2017 at 11:43 PM Vaughan McAlley 
wrote:

> Greetings,
>
> LilyQuick 0.95beta is now out. The main new features are smart
> articulations ( \fermata or whatever will now be placed after the note when
> the note is at the end of a bar and LilyQuick has already gone to a new
> line), and experimental support for non-US keyboard layouts.
>
> Source: https://github.com/palestrina/lily-q
> Video: https://youtu.be/eh8mgF1CNAo
>
> Once bugs are fixed I think I will release it as version 1.0, and maybe
> begin working on a cross-platform version.
>
> Cheers,
> Vaughan
>
>
> From the README:
>
> LILYQUICK
>
> Welcome to LilyQuick, originally written as a replacement for Speedy Note
> Entry when I moved from Finale to Lilypond, and then much improved. The
> basic idea is to play notes on a MIDI keyboard with your left hand, then
> while they are sounding, press a note on the numeric keypad with your right
> hand corresponding to the duration. For example, to get "f2", play an F on
> the MIDI keyboard, and press number 5 on the numeric keypad. The advantage
> to this approach is excellent speed and accuracy, and you get to hear the
> notes as they are being entered.
>
> VIDEO
>
> I did a demonstration video that you can watch at
> https://youtu.be/eh8mgF1CNAo
>
> NUMERIC KEYPAD LAYOUT
>
> The default key layout is as follows: numeric keypad keys 0-6 produce
> notes in conjunction with the MIDI keyboard.
> 6 - semibreve/whole
> 5 - minim/half
> 4 - crochet/quarter
> 1 - quaver/eighth
> 2 - semiquaver/sixteenth
> 3 - demisemiquaver/thirty-second
> 0 - last note value (useful with repeated dotted notes)
>
> For longer and shorter values, see setting note lengths below.
>
> 7 adds whole measure rests such as R1* , then changes to data entry mode,
> where the numeric keypad behaves as normal. Pressing enter leaves data
> entry mode. The type of rest is from the variable fullRest in LQconfig.lua.
> So to enter 15 measures of rest, you would type 7, 1, 5, enter on the
> numeric keypad.
>
> 8 is for entering tuplets. The 8 key enters \tuplet, then enters data
> entry mode for the numbers. The enter key leaves data entry mode and adds
> the curly bracket " { ", ready for note entry. So for quintuplets you would
> press 8, 5, /, 4, enter; which would type " \tuplet 5/4 {"
>
> If you only ever use triplets, you can add the ratio after the Tuplets
> function:
> ["8"] = { Tuplets, "3/2" },
> (in LQkeyboardEvents.lua)
>
> 9 just adds a right curly bracket " }"
>
> + alternates between entering left and right slurs: " (" and " )"
>
> - adds "\fermata", but can be customised to your own needs
>
> = or / adds a tie "~"
>
> . adds a dot to the rhythm
>
> * changes the previous note enharmonically, for example cis to des. Press
> again to cycle between possibilities.
>
> The Enter key either exits data entry mode, or adds a bar check and
> newline: " |\n".
>
> F8/F15 exits LilyQuick.
>
> F9/F16 sets the key. Press F9, then type the number of sharps or flats on
> the numeric keypad.
> For example, "1" means one sharp, "-3" means three flats, etc.
>
> In C major, LilyQuick will type a chromatic scale as follows: c cis d es e
> f fis g gis a bes b.
>
> SHIFT F9/F16 alternates absolute and relative input modes. The first note
> played after relative mode is selected becomes the reference note (so to
> avoid octave indications on your first note, play it straight away after
> selecting relative mode).
>
> F10/F17 sets the measure length for rhythm counting and full measure
> rests. Type in either a duration (eg. "1", "2." etc) or two numbers like
> "3/4" or "5/8". The plus key on the numeric keypad will enter "\breve".
>
> SHIFT F10/F17 Set note lengths. For notes longer than whole or shorter
> than thirty-seconds you can change the note lengths the keys 1-6 will
> produce. After pressing SHIFT F10/F17, press:
> "2" for \longa - 8
> "3" for \breve - 16
> "5" for 1 - 32
> "6" for 2 - 64
> "0" to duplicate Denemo’s layout (0 = 1, 1 = 2, 2 = 4 ... 6 = 64)
>
> F11/F18 Toggles rhythm counting (see below).
>
> F12/F19 (and any other key on the numeric keypad) can be customized at
> your pleasure.
>
> RHYTHM COUNTING (NEW!)
>
> When rhythm counting is turned on, LilyQuick will keep track of rhythms
> you have entered and automatically enter a bar check ("|") and a newline.
> Enter your measure length with F10/F17.
>
> Pressing Enter on the numeric keypad adds a bar check and new line
> manually, and resets the counting (useful for \partial measures). Pressing
> SHIFT Enter resets the counting without typing anything.
>
> To enter a tie over the barline, enter any note value larger than the
> remaining time left in the bar. For example in 3/4 time, pressing 4 twice
> while holding an F on the midi keyboard will produce:
>
> f4 f
>
> Pressin