convert-ly path for Frescobaldi in Windows?

2018-03-11 Thread Saul Tobin
Hi all,

I recently switched from Linux to Windows 10 and I'm trying to get
convert-ly to work in Frescobaldi 3. The "OK" button is greyed out and "Run
Again" seems not to do anything. What path should I be using for
convert-ly? My Lilypond installations are C:\Program Files\LilyPond\2.xx.x\.

Thanks,

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


RE: that migrating "opus"

2018-03-11 Thread Mark Stephen Mrotek
David,

Again, thank you for your direction/advice.

Mark

-Original Message-
From: David Wright [mailto:lily...@lionunicorn.co.uk] 
Sent: Sunday, March 11, 2018 6:05 PM
To: Mark Stephen Mrotek 
Cc: lilypond-user@gnu.org
Subject: Re: that migrating "opus"

On Sun 11 Mar 2018 at 12:40:35 (-0700), Mark Stephen Mrotek wrote:
> David,
> 
> Your continued effort to address my inquiry is uncommon. Many more 
> esoteric and arcane matters appear on the list with multiple, and 
> often contentious, responses. Yet you are the only one to respond to 
> this simple inquiry and then it is not posted on the list.

The convention on this list appears to be
 to: a person
 cc: the list
so that's what I do. My response is on the list, but some mail systems do
various things like:
 . deliver only one copy of messages (which could explain your case,
   where you received just the personal copy),  . refuse to deliver messages
they recognise as coming from the sender
   (which can lead people to keep reposting a message to a list
   because they think it never arrives).

> Thank you for your kind attention.
> 
> Your courtesy (your snippet is in my repository!) restricts any 
> further comment. Suffice it to say that I have found a simple 
> alternative: put the opus number in the "arranger" field.

Fair enough. There are two things to watch out for:

. the headings are left/right paired, so you can get gaps below them.
  (I use this as a positive feature with Anglican chants, using opus
  for the composer and meter for any necessary annotation, thereby
  ensuring that the composer is close-set and a lengthy annotation
  will not collide with it.)

. There are LP headers that find their way into the PDF metadata, and
  they might end up mislabelled there. Not a worry for most people,
  and there are probably ways to edit such metadata anyway.

Cheers,
David.


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


Re: How to prevent ly:stencil-rotate to modify dimensions

2018-03-11 Thread Andrew Bernard
Hi Torsten,

Thanks for the confirmation. That obviously explains the observed behaviour
very simply.

Not intuitive to me. I would have thought the stencil was rotated in this
case about its axis of symmetry. But I guess lily[ond does not really know
the item, just a stencil, is a 'circle' with special geometrical
properties. But once one knows about this, it's all very clear. Indeed. as
I thought, lilypond has not the mathematical nicety of Postscript in this
particular area (indeed, why should it? It is my mistake to think that.).


Andrew



On 12 March 2018 at 02:43, Torsten Hämmerle 
wrote:

>
>
> The bounding box of a circle actually is a square.
> But, after rotation, the resulting markup/stencil will have a new bounding
> box (with vertical height and horizontal width) large enough to contain the
> original bounding box (all objects are considered as boxes, no matter what
> their actual shape may be).
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: that migrating "opus"

2018-03-11 Thread David Wright
On Sun 11 Mar 2018 at 12:40:35 (-0700), Mark Stephen Mrotek wrote:
> David,
> 
> Your continued effort to address my inquiry is uncommon. Many more esoteric
> and arcane matters appear on the list with multiple, and often contentious,
> responses. Yet you are the only one to respond to this simple inquiry and
> then it is not posted on the list.

The convention on this list appears to be
 to: a person
 cc: the list
so that's what I do. My response is on the list, but some mail systems
do various things like:
 . deliver only one copy of messages (which could explain your case,
   where you received just the personal copy),
 . refuse to deliver messages they recognise as coming from the sender
   (which can lead people to keep reposting a message to a list
   because they think it never arrives).

> Thank you for your kind attention.
> 
> Your courtesy (your snippet is in my repository!) restricts any further
> comment. Suffice it to say that I have found a simple alternative: put the
> opus number in the "arranger" field.  

Fair enough. There are two things to watch out for:

. the headings are left/right paired, so you can get gaps below them.
  (I use this as a positive feature with Anglican chants, using opus
  for the composer and meter for any necessary annotation, thereby
  ensuring that the composer is close-set and a lengthy annotation
  will not collide with it.)

. There are LP headers that find their way into the PDF metadata, and
  they might end up mislabelled there. Not a worry for most people,
  and there are probably ways to edit such metadata anyway.

Cheers,
David.

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


Re: My Lilypond 2.18 crashes when combining slur and tie on a note

2018-03-11 Thread David Kastrup
Frank Steinmetzger  writes:

> Dear list,
>
> after a long hiatus, I am now typing another piece for choir. But after I
> had finished the first voice, the document would not compile. I narrowed it
> down to the following MWE. See the comment in the second line with notes:
>
>
> \version "2.18"
> \language "deutsch"
>
> SopranNoten = \relative c'' {
> \dynamicUp
> \time 4/4
> \key d \major
> \clef treble
>
> d=''2 cis4\!\f\< h |
> e\> a,\! d2~( |  % remove either ~ or ( from that d2, and it compiles
> d cis4) h |
> }
>
> \score{
> \SopranNoten
> \layout{}
> }
>
>
> This snippet causes Lilypond to crash on my machines. Both run Gentoo Linux
> with identical versions, namely Lilypoind 2.18.2. I installed 2.18.2 on an
> Ubuntu and an Arch installation. Both of them have no problem. :'-(

You are likely compiling 2.18.2 with a compiler version that is too new
(and optimises out a this == 0 comparison).  There is an issue/patch in
the 2.19 development fixing this but you might find a compiler option
that leaves off this optimization.

-- 
David Kastrup

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


Re: How to prevent ly:stencil-rotate to modify dimensions

2018-03-11 Thread David Kastrup
Torsten Hämmerle  writes:

> Hi Harm,
>
> Thanks for the background information, that'd be a valuable improvement.
>
>
> Thomas Morley-2 wrote
>> Using your code with the following example:
>> 
>> \markup
>>   \override #'(box-padding . 0)
>>   \box
>>   \override #'(slant-angle . 40)
>>   \slanted
>>   \musicglyph #"clefs.G"
>> 
>> results in a not matching boundingbox as well.
>
> Yes, I know, but this code was meant for text in the first place and it's
> quite common for slanted characters to stick out of their bounding boxes to
> the left to the right. Unfortunately, there are no slanted bounding boxes
> (the are always upright"
> But the main reason behind is that 
> \slanted "one two three" 
> should give the same result as 
> \slanted { "one" "two" "three" }

Uh, no?

\slanted "one two three"

should likely give the same result as

\slanted \line { "one" "two" "three" }

but

\slanted { "one" "two" "three" }

is exactly equivalent to

{ \slanted "one" \slanted "two" \slanted "three" }

and is connected with unslanted spaces.

> and when separately applying \slanted to "one", "two", and "three", a
> widened box would lead to a wider spacing.

This _is_ separately applying \slanted to "one", "two", and "three".

-- 
David Kastrup

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


Re: lyluatex, call for pre-beta review

2018-03-11 Thread Craig Dabelstein
Got it to work. Thanks everyone. Now hopefully I can help with the testing.

Craig



On 11 March 2018 at 23:10, Jacques Peron  wrote:

> 2018-03-11 5:34 GMT+01:00 Craig Dabelstein :
>
>>
>> stack traceback:
>>
>> [C]: in function 'error'
>>
>> ...ocal/texlive/2017/texmf-dist/tex/latex/base/ltluatex.lua:109: in
>> function <...ocal/texlive/2017/texmf-dist/tex/latex/base/ltluatex.lua
>> :108>
>>
>> (...tail calls...)
>>
>> ./lyluatex.lua:899: in function 'lilypond_version'
>>
>> ./lyluatex.lua:1114: in function 'run_lilypond'
>>
>> ./lyluatex.lua:1095: in function 'process'
>>
>> [\directlua]:1: in main chunk.
>>
>> \ly@compilescore ...directlua {ly.score:process()}
>>
>
> Just to be sure: did you launch lualatex with the --shell-escape option ?
> As follows:
>
> lualatex --shell-escape DOCUMENT.tex
>



-- 
*Craig Dabelstein*
Maxime's Music
craig.dabelst...@gmail.com
*http://maximesmusic.com *
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: My Lilypond 2.18 crashes when combining slur and tie on a note

2018-03-11 Thread David Wright
On Sun 11 Mar 2018 at 20:34:42 (+0100), Frank Steinmetzger wrote:
> Dear list,
> 
> after a long hiatus, I am now typing another piece for choir. But after I
> had finished the first voice, the document would not compile. I narrowed it
> down to the following MWE. See the comment in the second line with notes:
> 
> 
> \version "2.18"
> \language "deutsch"
> 
> SopranNoten = \relative c'' {
> \dynamicUp
> \time 4/4
> \key d \major
> \clef treble
> 
> d=''2 cis4\!\f\< h |
> e\> a,\! d2~( |  % remove either ~ or ( from that d2, and it compiles
> d cis4) h |
> }
> 
> \score{
> \SopranNoten
> \layout{}
> }
> 
> 
> This snippet causes Lilypond to crash on my machines. Both run Gentoo Linux
> with identical versions, namely Lilypoind 2.18.2. I installed 2.18.2 on an
> Ubuntu and an Arch installation. Both of them have no problem. :'-(

More data points: neither does Debian stretch's 2.18.2, nor downloaded
versions of 2.18.2 and 2.19.80 on stretch and wheezy.

> I was afraid that my own systems are at fault. But what can I do to fix it?
> Based on the backtrace given below, can you take a guess? Perhabs it is some
> underlying library or an incompatibility between libs due to a different gcc
> version?

You could try installing a downloaded copy (I think
http://lilypond.org/downloads/binaries/
is the best place at present) of either 2.18.2 or even 2.19.80 or
higher (or both) and see if they work.

Cheers,
David.

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


My Lilypond 2.18 crashes when combining slur and tie on a note

2018-03-11 Thread Frank Steinmetzger
Dear list,

after a long hiatus, I am now typing another piece for choir. But after I
had finished the first voice, the document would not compile. I narrowed it
down to the following MWE. See the comment in the second line with notes:


\version "2.18"
\language "deutsch"

SopranNoten = \relative c'' {
\dynamicUp
\time 4/4
\key d \major
\clef treble

d=''2 cis4\!\f\< h |
e\> a,\! d2~( |  % remove either ~ or ( from that d2, and it compiles
d cis4) h |
}

\score{
\SopranNoten
\layout{}
}


This snippet causes Lilypond to crash on my machines. Both run Gentoo Linux
with identical versions, namely Lilypoind 2.18.2. I installed 2.18.2 on an
Ubuntu and an Arch installation. Both of them have no problem. :'-(

I was afraid that my own systems are at fault. But what can I do to fix it?
Based on the backtrace given below, can you take a guess? Perhabs it is some
underlying library or an incompatibility between libs due to a different gcc
version?

Many thanks and I hope everyone came back safely from a nice weekend in
Chemnitz. :) I was too exhausted to go this time.



#0  Grob::get_offset (this=this@entry=0x0, a=a@entry=X_AXIS) at grob.cc:397
#1  0x555d17f7 in Grob::relative_coordinate (this=0x0, 
refp=0x560370e0, a=X_AXIS) at grob.cc:338
#2  0x555d181c in Grob::relative_coordinate (this=0x56034270, 
refp=0x560370e0, a=X_AXIS) at grob.cc:342
#3  0x555d181c in Grob::relative_coordinate (this=0x55ecd8b0, 
refp=0x560370e0, a=X_AXIS) at grob.cc:342
#4  0x555d181c in Grob::relative_coordinate (this=0x55ece190, 
refp=0x560370e0, a=X_AXIS) at grob.cc:342
#5  0x555d181c in Grob::relative_coordinate (this=0x55ecdc30, 
refp=0x560370e0, a=X_AXIS) at grob.cc:342
#6  0x555d181c in Grob::relative_coordinate (this=0x55ece2e0, 
refp=0x560370e0, a=X_AXIS) at grob.cc:342
#7  0x555d1852 in Grob::relative_coordinate 
(this=this@entry=0x55ece2e0, refp=, a=a@entry=X_AXIS) at 
grob.cc:345
#8  0x55603398 in Slur_configuration::score_extra_encompass 
(this=0x5603fb20, state=...) at slur-configuration.cc:327
#9  0x55603c1d in Slur_configuration::run_next_scorer 
(this=0x5603fb20, state=...) at slur-configuration.cc:508
#10 0x556bdb98 in Slur_score_state::get_best_curve 
(this=this@entry=0x7fff7550) at slur-scoring.cc:423
#11 0x556bdcf7 in Slur::calc_control_points (smob=) at 
slur-scoring.cc:359
#12 0x77928012 in scm_dapply (proc=0x73ef1970, arg1=0x70ae37a0, 
args=0x404) at eval.c:4895
#13 0x555ca868 in Grob::try_callback_on_alist 
(this=this@entry=0x55ecdce0, alist=alist@entry=0x55ecdd40, 
sym=sym@entry=0x722bae00, proc=proc@entry=0x73ef1970) at 
grob-property.cc:232
#14 0x555cab30 in Grob::internal_get_property 
(this=this@entry=0x55ecdce0, sym=0x722bae00) at grob-property.cc:189
#15 0x556f37ff in Slur::get_curve (me=me@entry=0x55ecdce0) at 
slur.cc:235
#16 0x556f516b in Slur::vertical_skylines (smob=) at 
slur.cc:378
#17 0x77928012 in scm_dapply (proc=0x73f1c4a0, arg1=0x70ae37a0, 
args=0x404) at eval.c:4895
#18 0x555ca868 in Grob::try_callback_on_alist 
(this=this@entry=0x55ecdce0, alist=alist@entry=0x55ecdd40, 
sym=sym@entry=0x7353c4e0, proc=proc@entry=0x73f1c4a0) at 
grob-property.cc:232
#19 0x555cab30 in Grob::internal_get_property 
(this=this@entry=0x55ecdce0, sym=0x7353c4e0) at grob-property.cc:189
#20 0x55705d12 in add_interior_skylines (me=me@entry=0x55ecdce0, 
x_common=x_common@entry=0x56034270, y_common=y_common@entry=0x560370e0, 
skylines=skylines@entry=0x7fff7e70) at axis-group-interface.cc:655
#21 0x557082e2 in Axis_group_interface::skyline_spacing 
(me=0x560370e0) at axis-group-interface.cc:917
#22 0x557084a9 in Axis_group_interface::calc_skylines (smob=) at axis-group-interface.cc:398
#23 0x77928012 in scm_dapply (proc=0x73df7f10, arg1=0x704ce960, 
args=0x404) at eval.c:4895
#24 0x555ca868 in Grob::try_callback_on_alist 
(this=this@entry=0x560370e0, alist=alist@entry=0x56037140, 
sym=sym@entry=0x7353c4e0, proc=proc@entry=0x73df7f10) at 
grob-property.cc:232
#25 0x555cab30 in Grob::internal_get_property 
(this=this@entry=0x560370e0, sym=0x7353c4e0) at grob-property.cc:189
#26 0x55698748 in get_skylines (ret=0x7fff8450, end=, start=, pure=, a=, 
elements=0x7fff8430, me=) at align-interface.cc:86
#27 Align_interface::internal_get_minimum_translations 
(me=me@entry=0x560373a0, all_grobs=std::vector of length 1, capacity 1 = 
{...}, a=a@entry=Y_AXIS, include_fixed_spacing=, 
include_fixed_spacing@entry=false, pure=pure@entry=false, start=,
end=) at align-interface.cc:210
#28 0x55699d47 in 
Align_interface::get_minimum_translations_without_min_dist 

Re: Build error. MergeFonts: Can't find font: feta11.pfb

2018-03-11 Thread Daniel Johnson
In Gentoo it was discovered that there is a buggy version of t1utils which 
segfaults and causes this exact error.

Sent from my iPhone

> On Mar 11, 2018, at 2:18 PM, Werner LEMBERG  wrote:
> 
> 
>> Invoking "t1asm parmesan-noteheads14.pt1 parmesan-noteheads14.pfb"...
>> mf2pt1: You'll need either to install t1utils and rerun mf2pt1 or find
>> another way to convert parmesan-noteheads14.pt1 to
>> parmesan-noteheads14.pfb
>> […]
>> 
>> t1utils (including t1asm) are installed in the correct version, so I
>> don’t know why it doesn’t do its job …
> 
> The perl script `scripts/build/out/mf2pt1' does the following.
> 
>  ...
>  if (!execute_command 0, ("t1asm", $pt1file, $pfbfile)) {
>  die "${progname}: You'll need either to install t1utils \
>and rerun $progname or find another way \
>to convert $pt1file to $pfbfile\n"; 
>exit 1;
>  }
> 
> So: Can you manually execute t1asm?  Does it have the right
> permissions?  Is it in the path used by the lilypond build?
> 
> Can you manually execute mf2pt1?  Have a look into `mf/README' for
> some help how to do it.
> 
> 
>Werner
> ___
> lilypond-devel mailing list
> lilypond-de...@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel

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


RE: that migrating "opus"

2018-03-11 Thread Mark Stephen Mrotek
David,

Your continued effort to address my inquiry is uncommon. Many more esoteric
and arcane matters appear on the list with multiple, and often contentious,
responses. Yet you are the only one to respond to this simple inquiry and
then it is not posted on the list.

Thank you for your kind attention.

Your courtesy (your snippet is in my repository!) restricts any further
comment. Suffice it to say that I have found a simple alternative: put the
opus number in the "arranger" field.  

Mark

-Original Message-
From: David Wright [mailto:lily...@lionunicorn.co.uk] 
Sent: Saturday, March 10, 2018 8:05 PM
To: Mark Stephen Mrotek 
Cc: lilypond-user@gnu.org
Subject: Re: that migrating "opus"

On Sat 10 Mar 2018 at 13:28:20 (-0800), Mark Stephen Mrotek wrote:
> David,
> 
> Thank you for your pointed reply.
> Yes, I did take away something from your explanation.
> I have used it on the previously referenced score.
> My basic question, more operational than technical (I really don't get all
of the \scoreTitlemarkup stuff!).
> 
> Why is it that "piece" and "opus" are the only ones beatified to migrate?

Because a musical work "typically" has one title at the top (cf a novel) and
one composer (cf author), whereas each movement (particularly where they're
often performed separately) will be numbered (cf chapters) and sometimed
titled (like children's stories).

> The process you provide seems a little kludgy to get "opus" behave as it
would on a normal score with multiple movements.

I think the example (which BTW I didn't write) was designed to give you a
lot of flexibility without using the \fromproperty method.
If your music is very conventional as just described, then the default
scheme may work for you, as attached (modified from that example cited).

Cheers,
David.


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


Re: MIDI assignment: two staffs to same channel

2018-03-11 Thread Giampaolo Orrigo
Thank you Torsten!
That worked perfectly. 

Handling stops can be done in the same way, thanks to the fact that in 
Hauptwerk you can assign them to different channels. It needs a bit if 
experimentation, but I’ll leave it for another day. 

Giampaolo

> On Mar 11, 2018, at 14:11, Torsten Hämmerle  wrote:
> 
> Giampaolo Orrigo wrote
>> is there a way to assign two staves to the same MIDI channel when creating
>> MIDI in Lilypond?
> 
> Hi Giampaolo,
> 
> As you wrote, by default, a separate MIDI channel will be assigned to each
> staff.
> But this default can be changed, see
> 3.5.7 MIDI channel mapping
>   
> 
> For driving Hauptwerk, 'voice will only make it worse, but probably you
> could make use of 'instrument:
> That way, everything played with the same midiInstrument will be mapped to
> the same MIDI channel:
> 
>  \midi {
>\context {
>  \Score
>  midiChannelMapping = #'instrument
>}
>  }
> 
> I don't know how to handle Hauptwerk stops via MIDI at all (LilyPond's
> standard GM instruments will not make any sense, of course). So, probably,
> setting midiChannelMapping to #'instrument might solve your problem.
> 
> All the best,
> 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

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


Re: Build error. MergeFonts: Can't find font: feta11.pfb

2018-03-11 Thread Werner LEMBERG

> Invoking "t1asm parmesan-noteheads14.pt1 parmesan-noteheads14.pfb"...
> mf2pt1: You'll need either to install t1utils and rerun mf2pt1 or find
> another way to convert parmesan-noteheads14.pt1 to
> parmesan-noteheads14.pfb
> […]
> 
> t1utils (including t1asm) are installed in the correct version, so I
> don’t know why it doesn’t do its job …

The perl script `scripts/build/out/mf2pt1' does the following.

  ...
  if (!execute_command 0, ("t1asm", $pt1file, $pfbfile)) {
  die "${progname}: You'll need either to install t1utils \
and rerun $progname or find another way \
to convert $pt1file to $pfbfile\n"; 
exit 1;
  }

So: Can you manually execute t1asm?  Does it have the right
permissions?  Is it in the path used by the lilypond build?

Can you manually execute mf2pt1?  Have a look into `mf/README' for
some help how to do it.


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


Re: MIDI assignment: two staffs to same channel

2018-03-11 Thread Torsten Hämmerle
Giampaolo Orrigo wrote
> is there a way to assign two staves to the same MIDI channel when creating
> MIDI in Lilypond?

Hi Giampaolo,

As you wrote, by default, a separate MIDI channel will be assigned to each
staff.
But this default can be changed, see
3.5.7 MIDI channel mapping
  

For driving Hauptwerk, 'voice will only make it worse, but probably you
could make use of 'instrument:
That way, everything played with the same midiInstrument will be mapped to
the same MIDI channel:

  \midi {
\context {
  \Score
  midiChannelMapping = #'instrument
}
  }

I don't know how to handle Hauptwerk stops via MIDI at all (LilyPond's
standard GM instruments will not make any sense, of course). So, probably,
setting midiChannelMapping to #'instrument might solve your problem.

All the best,
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: Build error. MergeFonts: Can't find font: feta11.pfb

2018-03-11 Thread Malte Meyn



Am 11.03.2018 um 01:01 schrieb Lucas Werkmeister:

Hi everyone,

I’m getting the following error message when trying to build LilyPond 
from git (specifically, building the AUR lilypond-git package).


[…]

The requested file, feta11.pfb, does not exist


I have a similar problem after installing a new system (Manjaro, which 
uses the AUR too) on my laptop:


[…]
Invoking "t1asm parmesan-noteheads14.pt1 parmesan-noteheads14.pfb"...
mf2pt1: You'll need either to install t1utils and rerun mf2pt1 or find 
another way to convert parmesan-noteheads14.pt1 to parmesan-noteheads14.pfb

[…]

t1utils (including t1asm) are installed in the correct version, so I 
don’t know why it doesn’t do its job …


Forwarding this to the developer list.

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


Re: Frescobaldi -> loopMIDI -> Hauptwerk

2018-03-11 Thread Giampaolo Orrigo
Clever one! Lol!
But I finally managed to do it using LoopMIDI.
Now I just have to figure out how to create a MIDI in Lilypond with all the
staves assigned to the same midi channel.



On Sat, Mar 10, 2018 at 10:37 PM, Andrew Bernard 
wrote:

> Hi Giampaolo,
>
> Perhaps Frescobaldi is heeding Wittgenstein. [:-)]
>
> Andrew
>
>
>
> On 11 March 2018 at 14:17, Giampaolo Orrigo  wrote:
>
>> Anybody tried to do the same?
>> I connected everything together but no sound comes out from Frescobaldi.
>>
>> Thanks!
>>
>> Giampaolo Orrigo, MBA
>>
>> "*Whereof one cannot speak, thereof one must be silent"*
>>
>> (L. Wittgenstein, *Tractatus Logico-Philosophicus, *Proposition 7)
>>
>>
>>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


MIDI assignment: two staffs to same channel

2018-03-11 Thread Giampaolo Orrigo
Hello list,

is there a way to assign two staves to the same MIDI channel when creating
MIDI in Lilypond?
I am trying to redirect frescobaldi MIDI output to the organ sim sw
Hauptwerk and while I have been finally successful, still the fact that the
two organ staves are assigned to two different channels make the msuic only
partially playable.

Thanks,


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


Re: How to prevent ly:stencil-rotate to modify dimensions

2018-03-11 Thread Torsten Hämmerle
Hi Harm,

Thanks for the background information, that'd be a valuable improvement.


Thomas Morley-2 wrote
> Using your code with the following example:
> 
> \markup
>   \override #'(box-padding . 0)
>   \box
>   \override #'(slant-angle . 40)
>   \slanted
>   \musicglyph #"clefs.G"
> 
> results in a not matching boundingbox as well.

Yes, I know, but this code was meant for text in the first place and it's
quite common for slanted characters to stick out of their bounding boxes to
the left to the right. Unfortunately, there are no slanted bounding boxes
(the are always upright"
But the main reason behind is that 
\slanted "one two three" 
should give the same result as 
\slanted { "one" "two" "three" }
and when separately applying \slanted to "one", "two", and "three", a
widened box would lead to a wider spacing.



Thomas Morley-2 wrote
> With '(slant-angle . 70) it produces an error:

Yes, this is due to a mathematical problem (slant-angle must be less than
45°).
I didn't catch the exception and a slant angle beyond 20° seems questionable
from a typographical point of view, anyway.
Moreover, typographically, these automated and artificial font manipulations
are getting worse as the effect increases.

Slant angles above 45°, can be achieved by an extended version that calls
the code twice for a smaller angle.
The trigonometric functions are used here the keep proportions right (same
width, same height after slanting) - in most other situations one may get
away without this kind of calculations. 

Probably it'd be a good idea to provide a handy new markup command that can
shear an arbitrary graphical object by any angle (approaching 90° will
result in an infinite width, though) that also adapts the bounding box...

All the best,
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


An empirical tip from the Fresco/Lily problem saga (not strictly Lily)

2018-03-11 Thread peter.gentry
I have had endless troubles with Network not showing all the machines on my
LAN. 

 

However subsequent to removing the onedrive program (comments passim) I
deleted the onedrive folder in each c:\users\USER1\...  data. 

 

Then as if by magic all the computers appeared in the list of Network
computers.

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


Re: How to prevent ly:stencil-rotate to modify dimensions

2018-03-11 Thread Thomas Morley
2018-03-11 15:27 GMT+01:00 Torsten Hämmerle :
> Hi Harm,
>
> David is right - it's the bounding box being rotated. As bounding boxes can
> only have heights and widths in vertical and horizontal direction (there
> isn't even such a thing as an italic slant in LilyPond), the resulting new
> bounding box's height and width increases.
>
> I usually solve this problem by calculating the desired X-extent and
> Y-extent and set the stencil dimensions.
> In scheme, I use (ly:stencil-outline stencil point-stencil) to rotate
> stencil using the dimensions of point-stencil so that the bounding box isn't
> distorted .
>
> *Example:* I've created a fake slanted markup command by combining rotate,
> scale, rotate back, scale (because there is no shearing) that keeps the
> original stencil extent.
> Without stencil extent manipulations (using point-stencil dimensions etc.)
> the resulting bounding box would be ridiculously high and totally unusable.
>
> %%%
>
> \version "2.19.81"
>
> #(define-markup-command
>   (slanted layout props arg)
>   (markup?)
>   #:category font
>   #:properties ((slant-angle 12))
>   "Fake a slanted font"
>   (let* ((alpha-rad (* 0.5 (acos (tan (* (/ PI -180) slant-angle)
>   (alpha-deg (* (/ 180 PI) alpha-rad))
>   (stencil (if (markup? arg) (interpret-markup layout props arg)
> empty-stencil))
>   )
> (ly:stencil-outline
>   (ly:stencil-scale
>(ly:stencil-rotate
> (ly:stencil-scale
>  (ly:stencil-rotate (ly:stencil-outline stencil point-stencil) 45 0
> 0)
>  1 (* (tan alpha-rad)))
> (* (- alpha-deg)) 0 0)
>(* (sqrt 2) (cos alpha-rad)) (/ 0.5 (sqrt 0.5) (sin alpha-rad)))
>  stencil)))
>
>
> \markup \override #'(box-padding . 0) \box \slanted "Poor man’s slanted
> Text"
>
> poor-mans-slanted.png
> 
>
> This is a simple case just keeping the original extents, but in the end, the
> desired new bounding box (i.e. stencil extent) has to be calculated
> explicitly depending on the desired output, I couldn't find an automatic
> solution either.
> Simple trigonometric functions are all you need - it could be worse... ;)
>
> All the best,
> Torsten

Hi Torsten,

yep, David's explanation sounds very reasonable.

To give a bit background:
Currently we have several line-styles to print solid, dashed, and
dotted lines, as well as zigzag-, trill- and squiggle-lines.
They are available via setting the style-property for grobs supporting
a line-style or via different markup-commands.
Additionally not long ago David Nalesnik wrote ly:line-interface.

Though, there are two disadvantages:
Some line-styles may visible end too short because there is no room to
add another item like a dot-, dash-, trillelement, without any
possibility to scale the line-elements accordingly. This holds
especially for the lines predefined in C++.
There is no other possibility for a user to create a new line-style
than doing it all from scratch.

So my thought was to write a scheme-line-interface with the
possibility to scale line-elements (if desired) and to provide a
simple method to create a new line-style.
This could be done by a user-provided init stencil (and probably
padding if wished) and let do the procedure all the rest.

Attached you'll find some exmple-images for a trill- and a clef-style-line.
With the clef-style-line the boundindbox-problem is very prominent.

Having a look at your code, I don't like all the trigonometrics. Guile
and LilyPond doesn't work nicely with them in special cases, so I
always try to avoid them in scheme. I was beaten by this before.
We nowadays have ly:angle, ly:directed and ly:length which serve me well.

Using your code with the following example:

\markup
  \override #'(box-padding . 0)
  \box
  \override #'(slant-angle . 40)
  \slanted
  \musicglyph #"clefs.G"

results in a not matching boundingbox as well.

With '(slant-angle . 70) it produces an error:

item-lines.ly:258:10: In procedure ly:stencil-scale in expression
(ly:stencil-scale (ly:stencil-rotate # 45 ...) 1 ...):
item-lines.ly:258:10: Wrong type (expecting real number):
7.00808368402012e-17-1.46441350735015i

Though, thanks a lot for your code!
It made me see that I need to find a method to reset the boundingboxes.

Something at the lines of
(ly:make-stencil
  whatever-stencil
  x-extent
  y-extent)

Where the challenge will be to get accurate values for x/y-extent,
ofcourse this was clear right from the start lol

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


Re: How to prevent ly:stencil-rotate to modify dimensions

2018-03-11 Thread Torsten Hämmerle
Hi Andrew,

The bounding box of a circle actually is a square.
But, after rotation, the resulting markup/stencil will have a new bounding
box (with vertical height and horizontal width) large enough to contain the
original bounding box (all objects are considered as boxes, no matter what
their actual shape may be).

I've attached an image that demonstrates the growth of boxes: a circle with
square bounding box being rotated by 30 degrees and back, showing all the
bounding boxes involved (in colour).

Without outline/skyline analysis of the actual shape, LilyPond just sees
everything as boxes, exactly the way TeX does it and how it was done in hot
metal typesetting.

bb-rotation.png
  

All the best,
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


Frescobaldi Travails

2018-03-11 Thread peter.gentry
It may or may not be significant but today I removed onedrive from both
machines. Frescobaldi and Lilypond have behaved perfectly. 

 

This is not a scientific observation but so far it works for me.

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


Re: How to prevent ly:stencil-rotate to modify dimensions

2018-03-11 Thread Andrew Bernard
Hi Torsten,

I think Harm and I would assume the bounding box for a circle is a square,
which is the root of the confusion. Why is it a rectangle for a circle?

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


Re: How to prevent ly:stencil-rotate to modify dimensions

2018-03-11 Thread Torsten Hämmerle
Hi Harm,

David is right - it's the bounding box being rotated. As bounding boxes can
only have heights and widths in vertical and horizontal direction (there
isn't even such a thing as an italic slant in LilyPond), the resulting new
bounding box's height and width increases.

I usually solve this problem by calculating the desired X-extent and
Y-extent and set the stencil dimensions.
In scheme, I use (ly:stencil-outline stencil point-stencil) to rotate
stencil using the dimensions of point-stencil so that the bounding box isn't
distorted .

*Example:* I've created a fake slanted markup command by combining rotate,
scale, rotate back, scale (because there is no shearing) that keeps the
original stencil extent. 
Without stencil extent manipulations (using point-stencil dimensions etc.)
the resulting bounding box would be ridiculously high and totally unusable.

%%%

\version "2.19.81"

#(define-markup-command
  (slanted layout props arg)
  (markup?)
  #:category font
  #:properties ((slant-angle 12))
  "Fake a slanted font"
  (let* ((alpha-rad (* 0.5 (acos (tan (* (/ PI -180) slant-angle)
  (alpha-deg (* (/ 180 PI) alpha-rad))
  (stencil (if (markup? arg) (interpret-markup layout props arg)
empty-stencil))
  )
(ly:stencil-outline
  (ly:stencil-scale
   (ly:stencil-rotate
(ly:stencil-scale
 (ly:stencil-rotate (ly:stencil-outline stencil point-stencil) 45 0
0)
 1 (* (tan alpha-rad)))
(* (- alpha-deg)) 0 0)
   (* (sqrt 2) (cos alpha-rad)) (/ 0.5 (sqrt 0.5) (sin alpha-rad)))
 stencil)))


\markup \override #'(box-padding . 0) \box \slanted "Poor man’s slanted
Text"

poor-mans-slanted.png
  

This is a simple case just keeping the original extents, but in the end, the
desired new bounding box (i.e. stencil extent) has to be calculated
explicitly depending on the desired output, I couldn't find an automatic
solution either.
Simple trigonometric functions are all you need - it could be worse... ;)

All the best,
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: How to prevent ly:stencil-rotate to modify dimensions

2018-03-11 Thread David Kastrup
Thomas Morley  writes:

> Hi all,
>
> let's say I've a stencil, which I want to rotate around it's center.
> For the example below I choosed make-circle-stencil, because a circle
> center-rotated _should_ always look equal.
> Though, applying ly:stencil-rotate modifies the dimensions of said
> circle for degrees not equal to (* 90 n).
> (Made visible by boxing it)
>
> Why?

Because it is the rectangular bounding box that is getting rotated?  So
typically the covered area will increase unless you are rotating by
multiples of 90 degrees where the box covers the full bounding box after
rotation again.

> How to prevent?

No way that I know of.

> \markup
>   \override #'(box-padding . 0)
>   \box {
> \stencil
> #(make-circle-stencil 0.5 0.1 #f)
> \stencil
> #(ly:stencil-rotate (make-circle-stencil 0.5 0.1 #f) 10 0 0)
>   }

-- 
David Kastrup

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


Re: How to prevent ly:stencil-rotate to modify dimensions

2018-03-11 Thread Andrew Bernard
Hi Harm,

It's interesting to observe how the bounding box increases in size as you
increase the angle and then decreases again as you go to 90 degrees.

Clearly lilypond does not display the mathematical nicety of Postscript. As
to 'why?' - isn't this a bug or defect?

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


How to prevent ly:stencil-rotate to modify dimensions

2018-03-11 Thread Thomas Morley
Hi all,

let's say I've a stencil, which I want to rotate around it's center.
For the example below I choosed make-circle-stencil, because a circle
center-rotated _should_ always look equal.
Though, applying ly:stencil-rotate modifies the dimensions of said
circle for degrees not equal to (* 90 n).
(Made visible by boxing it)

Why?
How to prevent?

\markup
  \override #'(box-padding . 0)
  \box {
\stencil
#(make-circle-stencil 0.5 0.1 #f)
\stencil
#(ly:stencil-rotate (make-circle-stencil 0.5 0.1 #f) 10 0 0)
  }


Cheers,
  Harm

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


Re: lyluatex, call for pre-beta review

2018-03-11 Thread Jacques Peron
2018-03-11 5:34 GMT+01:00 Craig Dabelstein :

>
> stack traceback:
>
> [C]: in function 'error'
>
> ...ocal/texlive/2017/texmf-dist/tex/latex/base/ltluatex.lua:109: in
> function <...ocal/texlive/2017/texmf-dist/tex/latex/base/ltluatex.lua:108>
>
> (...tail calls...)
>
> ./lyluatex.lua:899: in function 'lilypond_version'
>
> ./lyluatex.lua:1114: in function 'run_lilypond'
>
> ./lyluatex.lua:1095: in function 'process'
>
> [\directlua]:1: in main chunk.
>
> \ly@compilescore ...directlua {ly.score:process()}
>

Just to be sure: did you launch lualatex with the --shell-escape option ?
As follows:

lualatex --shell-escape DOCUMENT.tex
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Modify a NoteEvent to RestEvent

2018-03-11 Thread David Kastrup
paolo prete  writes:

> 2018-03-11 8:26 GMT+01:00 David Kastrup :
>
>> paolo prete  writes:
>>
>> > Hello.
>> > Do you know how to modify a NoteEvent so that it becomes a RestEvent, or
>> > (vice-versa) in Scheme?
>>
>> You can't.
>>
>
> Why do you say that I can't, if changing the 'name property did the job
> (look at the snippet below)?
> Do you mean that this is sort of a  hack?

You don't change the definition in the unmodifiable properties.  Stuff
is free to break.

-- 
David Kastrup

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


Re: Modify a NoteEvent to RestEvent

2018-03-11 Thread paolo prete
2018-03-11 8:26 GMT+01:00 David Kastrup :

> paolo prete  writes:
>
> > Hello.
> > Do you know how to modify a NoteEvent so that it becomes a RestEvent, or
> > (vice-versa) in Scheme?
>
> You can't.
>

Why do you say that I can't, if changing the 'name property did the job
(look at the snippet below)?
Do you mean that this is sort of a  hack?
Thanks

%%

foo = #(define-music-function (parser location music1) (ly:music? )
(begin
   (map
  (lambda (x)
(if (music-is-of-type? x 'rest-event)
  (begin
(ly:music-set-property! x 'name  'NoteEvent)
(ly:music-set-property! x 'pitch (ly:make-pitch 0 3))
  )
  ;else
  (begin
(ly:music-set-property! x 'name 'RestEvent)
(ly:music-set-property! x 'pitch '())
  )
)
  )
  (ly:music-property music1 'elements)
   )
#{ $music1 #}))


{ \displayMusic \foo { f'4 r } }

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


Re: c#(+6 2)

2018-03-11 Thread David Kastrup
Gianmaria Lari  writes:

> Just to understand how does it work the relation between scheme and
> lilypond. Why this does not work?
>
> \version "2.19.81"
> { c#(+6 2) }
>
> I would expect this compile to
>
> \version "2.19.81"
> { c8 }

So much wrong with this...  First, (+6 2) calls 6 as function on 2.
That doesn't work.  You need (+ 6 2) here.

Then Scheme expressions written using # in the middle of music are
expected to be music expressions.  If you want to insert an actual
duration, you need to write it preceded with $ so that it can have
different type (and trigger different syntactic rules).

But $8 is not a duration.  $(ly:make-duration 3 0) would be a duration.

-- 
David Kastrup

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


c#(+6 2)

2018-03-11 Thread Gianmaria Lari
Just to understand how does it work the relation between scheme and
lilypond. Why this does not work?

\version "2.19.81"
{ c#(+6 2) }

I would expect this compile to

\version "2.19.81"
{ c8 }


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


Re: fisisis impossible?

2018-03-11 Thread Marc Hohl

Am 10.03.2018 um 21:20 schrieb bart deruyter:

Hi all,

got in a situation, trying to describe the bis augmented chord in second 
inversion, which would contain fisisis in a slashed chord name.


Lilypond returns an error, unexpected symbol, expecting tonicname pitch, 
which makes me believe that lilypond does not know triple sharps (isisis).


Am I right? Are there solutions for this?


This is on the issue tracker:

https://sourceforge.net/p/testlilyissues/issues/3356/

Marc

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