Re: double slurs within beamed notes

[Carl Sorensen]

From: Lucas Werkmeister 
Date: Wednesday, March 28, 2018 at 4:39 PM
To: 
Subject: double slurs within beamed notes






Does anyone have better ideas? :)

Slur on one note, phrasing slur on the other?



Carl


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

Re: rounded-box vs. box in text markup

[Emilio Millan]

Robert, Federico, and Harm: Thank you so much for your help! All your
suggestions worked very well. I'm playing with them now to decide
which is the best for my document.

Everybody: My apologies for accidentally sending my question to the list twice!

Regards,
Emilio

On Wed, Mar 28, 2018 at 11:36 AM, Thomas Morley
 wrote:
> 2018-03-28 14:23 GMT+02:00 Emilio Millan :
>> Hi all. I'm a fairly new user so I may be missing something obvious.
>>
>> In the following example, is there a way to "snug up" the rounded
>> boxes over the second note so that they are vertically spaced like the
>> boxes over the first note?
>>
>> \version "2.19.80"
>> {
>>   f''2^\markup{\box "1"}^\markup{\box "2"}^\markup{\box "3"}
>>   f''2^\markup{\rounded-box "1"}^\markup{\rounded-box
>> "2"}^\markup{\rounded-box "3"}
>> }
>>
>> I know I can override box-padding to make the rounded boxes smaller,
>> but I don't know how to change the space between them.
>>
>> Regards,
>> Emilio
>
>
>
> Your best bet is probably to use a column-markup (or center-column,
> dir-column ...) and apply the same box-padding for \box and
> \rounded-box (per default it's different).
> Then you could override baseline-skip to fit your needs.
>
> {
>   f''1
> ^\markup
>   \override #'(baseline-skip . 4)
>   \column
> \override #'(box-padding . 0.2)
> \rounded-box { 1 2 3 }
>   f''1
> ^\markup
>   \override #'(baseline-skip . 4)
>   \column
> \override #'(box-padding . 0.2)
> \box { 1 2 3 }
> }
>
> Though, I've no clue why the rounded-boxes are further away from Staff.
>
> I just filed a bug-report about it.
> http://lilypond.1069038.n5.nabble.com/Possible-regression-with-box-markup-rounded-box-markup-td211212.html
>
> HTH,
>   Harm

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

Re: double slurs within beamed notes

[Kieren MacMillan]

Hi Lucas,

> Hm, is this \=1 thing a new feature in the development version? I can’t get 
> it to work on 2.18.2.

Might be. Sorry if you can’t take advantage of it. (Related: I recommend you 
consider using the "unstable" version regularly: I use it exclusively, for 
mission-critical day-to-day work as a professional composer and arranger, and 
have problems so seldom that I can say “never” and kind of mean it!)

> I’m guessing that you’re adding slurs to the individual notes of a chord (and 
> the \=1, \=2 is probably so that you can distinguish which rparen closes 
> which slur), and then you have two objects that can be tweaked individually. 
> Which would be a lot less hacky :)

Precisely so.

> One difference to my horrible hack (I think) is that in this case you’re 
> shifting a slur that was aligned to a beam, not to the note heads, so I 
> assume the slur will not follow the slight upwards slope from the b to the c. 
> (You could probably emulate that with some more tweaks or \shape.)

Actually, the slurs *do* [perhaps surprisingly!] align to the notehead — too 
closely, in fact, as you can see from the untweaked snippet:

%%%  SNIPPET BEGINS
\version "2.19.80"

stuff = {
  16 8
  16 16
  16 8
}

\score {
  \stuff
}
%%%  SNIPPET ENDS

(If you need to, use lilybin.com to see this in the development version.)

Hope this 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: double slurs within beamed notes

[Lucas Werkmeister]

Hi Kieren, thanks for taking a look!

On 29.03.2018 01:52, Kieren MacMillan wrote:
> Hi Lucas,
>
>> I did find one workaround, and I’ll describe it just in case someone else 
>> with the same problem finds this email later, but it is horrible:
> Here’s another… though I’m not sure it’s much less horrible:
>
> %%%  SNIPPET ENDS
> \version "2.19.80"
>
> stuff = {
>    Slur.extra-offset #'(0 . 0.6) \=2 ^(>16 8
>    Slur.extra-offset #'(0 . 0.6) \=2 ^(>16 16
>    Slur.extra-offset #'(0 . 0.6) \=2 ^(>16 8
> }
>
> \score {
>   \stuff
> }
> %%%  SNIPPET BEGINS
>
> Fortunately, this could relatively easily be function-ized… And likely, the 
> offset could be replaced with something automagic (instead of 
> trial-and-error). So maybe it’s a winner after all?
>
> Hope this helps!
> Kieren.
Hm, is this \=1 thing a new feature in the development version? I can’t
get it to work on 2.18.2.

I’m guessing that you’re adding slurs to the individual notes of a chord
(and the \=1, \=2 is probably so that you can distinguish which rparen
closes which slur), and then you have two objects that can be tweaked
individually. Which would be a lot less hacky :)

One difference to my horrible hack (I think) is that in this case you’re
shifting a slur that was aligned to a beam, not to the note heads, so I
assume the slur will not follow the slight upwards slope from the b to
the c. (You could probably emulate that with some more tweaks or \shape.)

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

double slur collisions

[Kieren MacMillan]

Hey all,

Is it a feature or a bug that these slurs are collision-ing?

\version "2.19.80"

stuff = {
  16 8
  16 16
  16 8
}

\score {
  \stuff
}

Cheers,
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: double slurs within beamed notes

[Kieren MacMillan]

Hi Lucas,

> I did find one workaround, and I’ll describe it just in case someone else 
> with the same problem finds this email later, but it is horrible:

Here’s another… though I’m not sure it’s much less horrible:

%%%  SNIPPET ENDS
\version "2.19.80"

stuff = {
  16 8
  16 16
  16 8
}

\score {
  \stuff
}
%%%  SNIPPET BEGINS

Fortunately, this could relatively easily be function-ized… And likely, the 
offset could be replaced with something automagic (instead of trial-and-error). 
So maybe it’s a winner after all?

Hope this 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

double slurs within beamed notes

[Lucas Werkmeister]

Hi everyone!

In a composition I’m transcribing, there are double slurs between some
notes (see attached image, also uploaded at [1]), and the lower slurs
are right next to the note heads, inside the beams – whereas when
typeset by LilyPond, the slurs are outside the beams. I’m wondering what
the best way is to move the slurs inside the beams.

Searching the internet, I found one prior thread for this issue [2] –
but in that case, it turned out that the score actually had a tie and a
slur, not a double slur, and after one slur had been turned into a tie,
the other slur could be tweaked without difficulty. In my case, however,
I’m definitely dealing with a double slur (four different pitches), and
I haven’t found a way to tweak the two slur halves independently – if I
tweak, for instance, the extra-offset, both parts of the double slur
move, which I don’t want.

I did find one workaround, and I’ll describe it just in case someone
else with the same problem finds this email later, but it is horrible:

1. Introduce an auxiliary voice with the << { … } \new Voice { … } >>
construct.
2. Duplicate the notes in both voices.
3. In the main voice, explicitly point the slur away from the beams (up
or down, depending on where the beam is).
4. In the other voice, explicitly point the slur towards the beams (down
or up). We have a double slur, but it’s still outside the beam.
5. Still in the other voice, apply \noBeam to the slurred notes. This
makes the slur attach directly to the note heads. Our slurs are now
where we want them – we just need to get rid of all the auxiliary stuff.
5. \hide the NoteHead in the auxiliary voice. (Don’t \omit it, otherwise
the slur won’t position correctly – in one case I even got LilyPond to
segfault with \omit.)
6. \omit the Stem and Flag in the auxiliary voice. (In this case, \hide
isn’t enough, otherwise the stems in the main voice will be lengthened
in an attempt to reduce collisions with the invisible grobs.)
7. Repeat this for every double slur you have.

This hack is awful enough that, as much as I want to reproduce the
printed score accurately, I’m not yet sure whether I will end up using
it. It’s also not perfect – LilyPond still prints warnings about “too
many clashing note columns” (due to the hidden but not omitted NoteHead,
I guess).

Does anyone have better ideas? :)

Cheers,
Lucas

[1]: https://i.imgur.com/awenjmf.jpg
[2]: https://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00697.html

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

Re: Scratching my head around define-macro and variable evaluation

[Stefano Troncaro]

Hi David,

Thank you for your reply. Yes, I undestood that about macros. I'm trying to
dynamically generate the variable definitions inside a let block from an
alist, but the only way I manage to do that is if I type the alist
manually. I want to achieve that with an alist stored in a variable.
Simplified example:

> \version "2.19.80"
> #(define-macro (custom-let alist . body)
>`(let ,(map (lambda(pair) (list (car pair) (cdr pair))) alist)
>   . ,body))
>
> #(custom-let ((my-key . "my-val") (another-key . "another-val"))
>(pretty-print my-key)
>(pretty-print another-key))%Outputs:
> %"my-val"
> %"another-val"
> #(define my-alist '((my-key . "my-val") (another-key . "another-val")))
>
> #(custom-let my-alist
>(pretty-print my-key)
>(pretty-print another-key))%No applicable method for #< 
> map (0)> in call (map # my-alist)
>
> This is why I wanted to be able to evaluate the contents of the variable
inside the body of the macro. I thought of manually evaluating the
argument, but if I understand correctly it is not possible to do it in the
correct scope (only globally and not locally)? If so, then do you have a
suggestion to solve the problem showed above?

2018-03-28 16:23 GMT-03:00 David Kastrup :

> Stefano Troncaro  writes:
>
> > Hi everyone!
> >
> > I have a question about the following example:
> >
> >> \version "2.19.80"
> >> #(define-macro (why-the-difference obj)
> >>(display (format "~a , " obj))
> >>`(display (format "~a\n" ,obj)))
> >>
> >> #(why-the-difference (list 1 2 3))% => (list 1 2 3) , (1 2 3)
> >> #(define var (list 1 2 3))
> >>
> >> #(why-the-difference var)% => var , (1 2 3)
> >>
> >> So, I assume that the difference is because the macro has access to what
> > is typed, and uses that to produce an expression that is later evaluated.
> > So, in the first example, (list 1 2 3) was typed, so that's shown in the
> > output before the comma. While in the second example, var was typed, so
> the
> > symbol var is shown instead.
> >
> > Is there a way to evaluate the symbol inside the body of the macro?
>
> Not reliably.  It's a rather loosely defined point of time.
>
> > I tried the following to no avail:
> >
> >> \version "2.19.80"
> >> #(use-modules (ice-9 r5rs))
> >>
> >> #(define-macro (my-attempt obj)
> >>(display (format "~a , " (eval 'obj (interaction-environment
> >>`(display (format "~a\n" ,obj)))
>
> Well, that's completely wrong.  (interaction-environment) is a _global_
> environment.  It does not have access to local variables/symbols like
> obj.  So you'd want to write
>
> (eval obj (interaction-environment)) if at all, and even then this will
> only work for global variables.
>
> >> #(define var (list 1 2 3))
> >>
> >> #(my-attempt var)
> >>
> >> This generates the error 'unbound variable: obj'. I don't understand why
> > obj is not considered defined, when if I use obj I get the symbol var (as
> > the first snippet showed). Anyways, I *can* evaluate var:
> >
> >> \version "2.19.80"
> >> #(use-modules (ice-9 r5rs))
> >>
> >> #(define-macro (my-attempt obj)
> >>(display (format "~a , " (eval 'var (interaction-environment
> >>`(display (format "~a\n" ,obj)))
> >>
> >> #(define var (list 1 2 3))
> >>
> >> #(my-attempt var)% => (1 2 3) , (1 2 3)
> >>
> >> Which makes sense. This achieves what I want but it is not useful
> because
> > I need to know the name of the variable before-hand, so it will not work
> > dynamically.
> >
> > Does anyone know of a way around this?
>
> Apparently you don't understand what a macro does.  A macro receives its
> arguments _unevaluated_, and the result is later evaluated in the
> closure where the macro is called.  (eval obj (interaction-environment))
> is exactly equivalent to (eval 'var (interaction-environment)) here.
>
> --
> David Kastrup
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Scratching my head around define-macro and variable evaluation

[David Kastrup]

Stefano Troncaro  writes:

> Hi everyone!
>
> I have a question about the following example:
>
>> \version "2.19.80"
>> #(define-macro (why-the-difference obj)
>>(display (format "~a , " obj))
>>`(display (format "~a\n" ,obj)))
>>
>> #(why-the-difference (list 1 2 3))% => (list 1 2 3) , (1 2 3)
>> #(define var (list 1 2 3))
>>
>> #(why-the-difference var)% => var , (1 2 3)
>>
>> So, I assume that the difference is because the macro has access to what
> is typed, and uses that to produce an expression that is later evaluated.
> So, in the first example, (list 1 2 3) was typed, so that's shown in the
> output before the comma. While in the second example, var was typed, so the
> symbol var is shown instead.
>
> Is there a way to evaluate the symbol inside the body of the macro?

Not reliably.  It's a rather loosely defined point of time.

> I tried the following to no avail:
>
>> \version "2.19.80"
>> #(use-modules (ice-9 r5rs))
>>
>> #(define-macro (my-attempt obj)
>>(display (format "~a , " (eval 'obj (interaction-environment
>>`(display (format "~a\n" ,obj)))

Well, that's completely wrong.  (interaction-environment) is a _global_
environment.  It does not have access to local variables/symbols like
obj.  So you'd want to write

(eval obj (interaction-environment)) if at all, and even then this will
only work for global variables.

>> #(define var (list 1 2 3))
>>
>> #(my-attempt var)
>>
>> This generates the error 'unbound variable: obj'. I don't understand why
> obj is not considered defined, when if I use obj I get the symbol var (as
> the first snippet showed). Anyways, I *can* evaluate var:
>
>> \version "2.19.80"
>> #(use-modules (ice-9 r5rs))
>>
>> #(define-macro (my-attempt obj)
>>(display (format "~a , " (eval 'var (interaction-environment
>>`(display (format "~a\n" ,obj)))
>>
>> #(define var (list 1 2 3))
>>
>> #(my-attempt var)% => (1 2 3) , (1 2 3)
>>
>> Which makes sense. This achieves what I want but it is not useful because
> I need to know the name of the variable before-hand, so it will not work
> dynamically.
>
> Does anyone know of a way around this?

Apparently you don't understand what a macro does.  A macro receives its
arguments _unevaluated_, and the result is later evaluated in the
closure where the macro is called.  (eval obj (interaction-environment))
is exactly equivalent to (eval 'var (interaction-environment)) here.

-- 
David Kastrup

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

Scratching my head around define-macro and variable evaluation

[Stefano Troncaro]

Hi everyone!

I have a question about the following example:

> \version "2.19.80"
> #(define-macro (why-the-difference obj)
>(display (format "~a , " obj))
>`(display (format "~a\n" ,obj)))
>
> #(why-the-difference (list 1 2 3))% => (list 1 2 3) , (1 2 3)
> #(define var (list 1 2 3))
>
> #(why-the-difference var)% => var , (1 2 3)
>
> So, I assume that the difference is because the macro has access to what
is typed, and uses that to produce an expression that is later evaluated.
So, in the first example, (list 1 2 3) was typed, so that's shown in the
output before the comma. While in the second example, var was typed, so the
symbol var is shown instead.

Is there a way to evaluate the symbol inside the body of the macro?

I tried the following to no avail:

> \version "2.19.80"
> #(use-modules (ice-9 r5rs))
>
> #(define-macro (my-attempt obj)
>(display (format "~a , " (eval 'obj (interaction-environment
>`(display (format "~a\n" ,obj)))
>
> #(define var (list 1 2 3))
>
> #(my-attempt var)
>
> This generates the error 'unbound variable: obj'. I don't understand why
obj is not considered defined, when if I use obj I get the symbol var (as
the first snippet showed). Anyways, I *can* evaluate var:

> \version "2.19.80"
> #(use-modules (ice-9 r5rs))
>
> #(define-macro (my-attempt obj)
>(display (format "~a , " (eval 'var (interaction-environment
>`(display (format "~a\n" ,obj)))
>
> #(define var (list 1 2 3))
>
> #(my-attempt var)% => (1 2 3) , (1 2 3)
>
> Which makes sense. This achieves what I want but it is not useful because
I need to know the name of the variable before-hand, so it will not work
dynamically.

Does anyone know of a way around this?

Thank you in advance!
Stéfano
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lyluatex: call for Fedora users

[R. Padraic Springuel]

> On Mar 28, 2018, at 12:06 PM, Federico Bruni  wrote:
> 
> sh: all: command not found"

That's the result of a bug in io.popen that was present in the version of 
LuaTeX which shipped with TeXLive 2017.  The bug was fixed shortly after TL2017 
was released so some other distros may have picked up the fix.  The bug is not 
in TL2016 or the TL2018 pretest. 
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: lyluatex: call for Fedora users

[Federico Bruni]

Il giorno mar 27 mar 2018 alle 19:10, Sam Bivens  
ha scritto:

Hi Federico,

The MWE I compiled a couple weeks ago that *did* work fine now no 
longer does, and now I have the exact problem that you have. Curious. 
I have TeXLive 2016, which was downloaded from the Fedora 
repositories along with LilyPond. I just have the lyluatex files in 
my file's directory.




Glad I'm not alone :-)

I've just made a test on a Fedora 27 container, where I've installed 
TexLive 2017 from this repository:

https://copr.fedorainfracloud.org/coprs/spot/texlive/

Now I'm having different errors.
I don't see why lilypond executable is not found, as it is in the PATH. 
(I've compiled it from source in /usr/local)
I don't understand either ther error "sh: all: command not found". sh 
is installed.


It looks like lualatex cannot see my PATH?



$ lualatex --shell-escape simple.tex
This is LuaTeX, Version 1.0.4 (TeX Live 2017)
system commands enabled.
(./simple.tex
LaTeX2e <2017-04-15>
(using write cache: 
/home/dev/.texlive2017/texmf-var/luatex-cache/generic)(usin
g read cache: /usr/share/texlive/texmf-var/luatex-cache/generic 
/home/dev/.texl

ive2017/texmf-var/luatex-cache/generic)sh: all: command not found

luaotfload | main : initialization completed in 0.258 seconds
Babel <3.9r> and hyphenation patterns for 1 language(s) loaded.
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo(load luc: 
/home/dev/.t

exlive2017/texmf-var/luatex-cache/generic/fonts/otl/lmroman10-regular.luc)))
(./lyluatex.sty
(/usr/share/texlive/texmf-dist/tex/luatex/luatexbase/luatexbase.sty
(/usr/share/texlive/texmf-dist/tex/luatex/ctablestack/ctablestack.sty))
(/usr/share/texlive/texmf-dist/tex/latex/xkeyval/xkeyval.sty
(/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkeyval.tex
(/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkvutils.tex
(/usr/share/texlive/texmf-dist/tex/generic/xkeyval/keyval.tex
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-def/luatex.def
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty
(/usr/share/texlive/texmf-dist/tex/latex/minibox/minibox.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3-code.tex)
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3pdfmode.def)))
(/usr/share/texlive/texmf-dist/tex/latex/environ/environ.sty
(/usr/share/texlive/texmf-dist/tex/latex/trimspaces/trimspaces.sty))
(/usr/share/texlive/texmf-dist/tex/latex/currfile/currfile.sty
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/kvsetkeys.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/etexcmds.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty
(/usr/share/texlive/texmf-dist/tex/latex/filehook/filehook.sty))
(/usr/share/texlive/texmf-dist/tex/latex/pdfpages/pdfpages.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
(/usr/share/texlive/texmf-dist/tex/latex/tools/calc.sty)
(/usr/share/texlive/texmf-dist/tex/latex/eso-pic/eso-pic.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/atbegshi.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty))
(/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)))
(/usr/share/texlive/texmf-dist/tex/latex/pdfpages/ppluatex.def))
(/usr/share/texlive/texmf-dist/tex/latex/metalogo/metalogo.sty
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty))) 
(./simple.aux

) (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/epstopdf-base.sty
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/grfext.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/kvdefinekeys.sty))
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/pdftexcmds.sty)
(/usr/share/texlive/texmf-dist/tex/latex/latexconfig/epstopdf-sys.cfg))
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/pdflscape.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/lscape.sty))(load 
luc: /home/

dev/.texlive2017/texmf-var/luatex-cache/generic/fonts/otl/lmsans10-regular.luc)
(load luc: 
/home/dev/.texlive2017/texmf-var/luatex-cache/generic/fonts/otl/lmmo

no10-regular.luc)sh: all: command not found
/usr/share/texlive/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 7

Re: rounded-box vs. box in text markup

[Thomas Morley]

2018-03-28 14:23 GMT+02:00 Emilio Millan :
> Hi all. I'm a fairly new user so I may be missing something obvious.
>
> In the following example, is there a way to "snug up" the rounded
> boxes over the second note so that they are vertically spaced like the
> boxes over the first note?
>
> \version "2.19.80"
> {
>   f''2^\markup{\box "1"}^\markup{\box "2"}^\markup{\box "3"}
>   f''2^\markup{\rounded-box "1"}^\markup{\rounded-box
> "2"}^\markup{\rounded-box "3"}
> }
>
> I know I can override box-padding to make the rounded boxes smaller,
> but I don't know how to change the space between them.
>
> Regards,
> Emilio



Your best bet is probably to use a column-markup (or center-column,
dir-column ...) and apply the same box-padding for \box and
\rounded-box (per default it's different).
Then you could override baseline-skip to fit your needs.

{
  f''1
^\markup
  \override #'(baseline-skip . 4)
  \column
\override #'(box-padding . 0.2)
\rounded-box { 1 2 3 }
  f''1
^\markup
  \override #'(baseline-skip . 4)
  \column
\override #'(box-padding . 0.2)
\box { 1 2 3 }
}

Though, I've no clue why the rounded-boxes are further away from Staff.

I just filed a bug-report about it.
http://lilypond.1069038.n5.nabble.com/Possible-regression-with-box-markup-rounded-box-markup-td211212.html

HTH,
  Harm

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

Re: rounded-box vs. box in text markup

[Federico Bruni]

Il giorno mer 28 mar 2018 alle 14:23, Emilio Millan  ha 
scritto:

Hi all. I'm a fairly new user so I may be missing something obvious.

In the following example, is there a way to "snug up" the rounded
boxes over the second note so that they are vertically spaced like the
boxes over the first note?

\version "2.19.80"
{
  f''2^\markup{\box "1"}^\markup{\box "2"}^\markup{\box "3"}
  f''2^\markup{\rounded-box "1"}^\markup{\rounded-box
"2"}^\markup{\rounded-box "3"}
}

I know I can override box-padding to make the rounded boxes smaller,
but I don't know how to change the space between them.




Hi Emilio

What about this?

f''2^\markup {
 \dir-column \rounded-box {
   1
   2
   3
 }
}

See here:
http://lilypond.org/doc/v2.19/Documentation/notation/align






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

Re: Cross-staff stems

[Phil Holmes]

Took me a while, but by reversing the order of the clashing notes with 
force-hshift you can get close.

\layout {
  \context {
\PianoStaff
\consists #Span_stem_engraver
  }
}

{
  \new PianoStaff <<
\new Staff { \relative c'
<<
  \new Voice {
\voiceThree d8 \once \override NoteColumn.force-hshift = #1.0 ces b a
  }
  \new Voice {
\voiceFour \crossStaff { s8 \once \override NoteColumn.force-hshift = 
#-0.0 b s bes }
  }
>>
}
\new Staff {
  \clef bass
  \voiceFour
  ges8 ces ges ces
}
  >>
}

--
Phil Holmes


  - Original Message - 
  From: Andrew Bernard 
  To: lilypond-user Mailinglist 
  Sent: Wednesday, March 28, 2018 2:43 PM
  Subject: Re: Cross-staff stems


  Hi All,


  This is surprisingly tricky, because the b flats don't line up with the bass. 
I think the OP is asking how to achieve that, not the mechanism of cross staff 
stemming.


  I cant figure it out either!


  Andrew




--


  ___
  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: Cross-staff stems

[Thomas Morley]

2018-03-28 15:43 GMT+02:00 Andrew Bernard :
> Hi All,
>
> This is surprisingly tricky, because the b flats don't line up with the
> bass. I think the OP is asking how to achieve that, not the mechanism of
> cross staff stemming.
>
> I cant figure it out either!
>
> Andrew



Hi Bernhard.

as Andrew pointed out it is tricky.

One reason is the typesetting in the image you provided is bad
concerning the order in which the last two notes in the RH are set,
imho
LilyPond does it the other way round by default. So you need to move
one note, if you want to mimic the image.
Additionally the AccidentalPlacement at second 8th is different by
default, not sure whether LilyPond does it correct. (This is not
tweaked below)

Another reason are the not aligning notes which should have the
cross-staff-stem. For this purpose I wrote `pushNC' some time ago.
Using it will result in uneven spacing so moving another NoteColumn
via X-offset is applied.

So here you are:

pushNC =
\once \override NoteColumn.X-offset =
  #(lambda (grob)
(let* ((p-c (ly:grob-parent grob X))
   (p-c-elts (ly:grob-object p-c 'elements))
   (stems
 (if (ly:grob-array? p-c-elts)
 (filter
   (lambda (elt)(grob::has-interface elt 'stem-interface))
   (ly:grob-array->list p-c-elts))
 #f))
   (stems-x-exts
 (if stems
 (map
   (lambda (stem)
 (ly:grob-extent
   stem
   (ly:grob-common-refpoint grob stem X)
   X))
   stems)
 '()))
   (sane-ext
 (filter interval-sane? stems-x-exts))
   (cars (map car sane-ext)))
(if (pair? cars)
(abs (- (apply max cars)  (apply min cars)))
0)))

\layout {
  \context {
\PianoStaff
\consists #Span_stem_engraver
  }
}

\new PianoStaff
<<
  \new Staff <<
\new Voice {
  \voiceOne
  d'8 c'? \once \override Score.NoteColumn.X-offset = 2 b a
}
\new Voice {
  \voiceTwo
  s \crossStaff bes s
  \once \override NoteColumn.force-hshift = 1.5
  \crossStaff bes
}
  >>
  \new Staff {
\clef F
\voiceTwo
fis, \pushNC cis fis, \pushNC cis
  }
>>

HTH,
  Harm

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

Re: calling lilybin (or similar) as a service triggered from a [JavaScript?] form in a web page

[Kieren MacMillan]

Hi Paul,

> I've done something in roughly the same ballpark by creating a version of 
> LilyBin for Clairnote music notation:
> http://lilybin.clairnote.org/
> Not sure if it makes sense for your use case, but check out this blog post 
> for more details.
> http://clairnote.org/blog/2017/06/announcing-lilybin-clairnote/

#whoa

This is literally exactly what I was asking about.
And that’s using 'literally' like it *used* to be defined, not how it’s 
literally been redefined… as 'figuratively'.  ;)

Thanks!
K.



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: Cross-staff stems

[Andrew Bernard]

Hi All,

This is surprisingly tricky, because the b flats don't line up with the
bass. I think the OP is asking how to achieve that, not the mechanism of
cross staff stemming.

I cant figure it out either!

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

RE: Cross-staff stems

[Mark Stephen Mrotek]

Bernard,

Have a look at
http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-key
boards#cross_002dstaff-stems

Mark

-Original Message-
From: lilypond-user
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
Bernard Meylan
Sent: Wednesday, March 28, 2018 12:23 AM
To: lilypond-user@gnu.org
Subject: Cross-staff stems

Hi all!

I can't find a solution for this problem:

 

I try something with 2 voices on RH... but unsuccessfull.

Any idea?

Bernard



--
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: \rounded-box vs. \box in text markup

[Robert Schmaus]

Hi Emilio,

I find this behaviour decidedly un-obvious as well.
But here's a way to have a more controlled spacing:

\version "2.19.80"
{
  f''2^\markup{
\column {
  \rounded-box "1"
  \rounded-box "2"
  \rounded-box "3"
}
  }
  f''2^\markup{
\column {
  \box "1"
  \box "2"
  \box "3"
}
  }
}


Note that this way of stacking the boxes actually makes he simple \box 
constructs move *farther apart* whereas the rounded boxes now are closer 
together. This can be fine-tuned with \vspace commands between the boxes.

Not an ideal solution but this is how it can be done ...

Best,
Robert




Am 28.03.18 um 03:42 schrieb Emilio Millan:

Hi all. I'm a fairly new user so I may be missing something obvious.

In the following example, is there a way to "snug up" the rounded boxes 
over the second note so that they are vertically spaced like the boxes 
over the first note?


\version "2.19.80"
{
   f''2^\markup{\box "1"}^\markup{\box "2"}^\markup{\box "3"}
   f''2^\markup{\rounded-box "1"}^\markup{\rounded-box 
"2"}^\markup{\rounded-box "3"}

}

Regards,
Emilio


___
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: Cross-staff stems

[Ben]

On 3/28/2018 4:43 AM, Bernard Meylan wrote:

Hi all!

I try to find a solution to this typographical music problem:



Trying with the doc page relative to this subject, or trying with 2 voices
on RH, nothing seems to right.

Any idea?

Bernard




Cross staff beaming? Sure.

Could you share some code so we can see what you're working with?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

rounded-box vs. box in text markup

[Emilio Millan]

Hi all. I'm a fairly new user so I may be missing something obvious.

In the following example, is there a way to "snug up" the rounded
boxes over the second note so that they are vertically spaced like the
boxes over the first note?

\version "2.19.80"
{
  f''2^\markup{\box "1"}^\markup{\box "2"}^\markup{\box "3"}
  f''2^\markup{\rounded-box "1"}^\markup{\rounded-box
"2"}^\markup{\rounded-box "3"}
}

I know I can override box-padding to make the rounded boxes smaller,
but I don't know how to change the space between them.

Regards,
Emilio

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

Cross-staff stems

[Bernard Meylan]

Hi all!

I can't find a solution for this problem:

 

I try something with 2 voices on RH... but unsuccessfull.

Any idea?

Bernard



--
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

Cross-staff stems

[Bernard Meylan]

Hi all!

I try to find a solution to this typographical music problem:

 

Trying with the doc page relative to this subject, or trying with 2 voices
on RH, nothing seems to right.

Any idea?

Bernard



--
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

\rounded-box vs. \box in text markup

[Emilio Millan]

Hi all. I'm a fairly new user so I may be missing something obvious.

In the following example, is there a way to "snug up" the rounded boxes
over the second note so that they are vertically spaced like the boxes over
the first note?

\version "2.19.80"
{
  f''2^\markup{\box "1"}^\markup{\box "2"}^\markup{\box "3"}
  f''2^\markup{\rounded-box "1"}^\markup{\rounded-box
"2"}^\markup{\rounded-box "3"}
}

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

Re: Thriple flat/sharp glyphs...

[Karlin High]

On 3/27/2018 3:20 PM, Torsten Hämmerle wrote:

Besides, I just noticed my typo ("Thriple") in the subject line carried over
from mail to mail, this is s embarrassing...


In forums for the DDWRT wifi router firmware, there are important 
must-read threads deliberately given unique, arbitrary names. ("The 
catfish thread," "the peacock thread," and so on.)


In the case we have here, I noticed the typo from the beginning and 
mentally approved of it. There are other threads that mention triple 
flat glyphs. But if in the future someone wants to find this discussion, 
I expect there will be only one that's about THRIPLE flat glyphs.

--
Karlin High
Missouri, USA

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

Re: an open question

[Jan-Peter Voigt]

Hello Jacques,

yes, you are right. Any information without a "first class citizen" will 
not be exported right. One might think of additional properties to give 
an export specific attribute - that is to say: this markup shall 
indicate swing tempo in MusicXML. But before that I want to be able to 
export the major exportable elements. And like Libre Office warns when 
you save an MS Word document that there might be elements that cannot be 
exported as expected this export function should do the same ;-)


Jan-Peter



Am 28.03.2018 um 08:47 schrieb Jacques Menu Muzhic:

Hello Jan-Peter,

Thanks for the information.

Exporting to MusicXML is difficult, also because there are things that 
need to be done in LP with Scheme code since there’s no ‘first class 
citizen’ to do the job.


This leads for example to the use of markup for things such as the swing 
tempo indication:


tempoRelationshipStaffReduce = #-3

tempoRelationship =
#(define-music-function (parser location label parenthesized musicI musicII)
    (string? boolean? ly:music? ly:music?)
    (let* (
            (left-paren (if parenthesized "(" ""))
            (right-paren (if parenthesized ")" ""))
            )
      #{
        \tempo \markup {
          \line \general-align #Y #DOWN {
            % 1st column in line
            $label

            % 2nd column in line

            $left-paren

            \score {
              \new Staff \with {
                % reduce the font size a la cue
                fontSize = #tempoRelationshipStaffReduce
                \override StaffSymbol.staff-space = #(magstep 
tempoRelationshipStaffReduce)

                % hide the staff lines
                \override StaffSymbol.line-count = #0
                % align horizontally
                \override VerticalAxisGroup.Y-extent = #'(-0.85 . 0)
              }

              {
                % \override 
Score.SpacingSpanner.common-shortest-duration = #(ly:make-moment 1/2) % 
super-tight
                % \override 
Score.SpacingSpanner.common-shortest-duration = #(ly:make-moment 1/4) % 
tight
                % \override 
Score.SpacingSpanner.common-shortest-duration = #(ly:make-moment 3/16) % 
even
                \override Score.SpacingSpanner.common-shortest-duration 
= #(ly:make-moment 5/32) % even


                % the left music
                \relative c' { \stemUp $musicI }

                % the equivalence sign
                \once \override Score.TextScript.Y-offset = #-0.4
                s4.^\markup{
                  \halign #-1 "="
                }

                % the right music
                \relative c' { \stemUp $musicII }
              }

              \layout {
                indent = 0
                \context {
                  \Staff
                  \remove "Clef_engraver"
                  \remove "Time_signature_engraver"
                }
              } % layout end
            } % score end

            $right-paren

          } % line end
        } % markup end
      #}))


     \tempoRelationship #"Swing" ##t
     \fixed b' {
       b8 [ b8 ]
     }
     \fixed b' {
       \tuplet 3/2 { b4 b8 }
     }

while they can be described natively in MusicXML:

      
         
           Swing
         
         
           relative-x="26">

             
               eighth
               begin
             
             
               eighth
               end
             
             equals
             
               quarter
               type="start">

                 3
                 2
                 eighth
               
             
             
               eighth
               
                 3
                 2
                 eighth
               
             
           
         
       

I’m not at ease enough currently with the Scheme/Lilypond interaction to 
be of any help, unfortunately.


JM

Le 26 mars 2018 à 07:29, Jan-Peter Voigt > a écrit :


Hello Jacques,

last year I have been working on an export module for lilypond:
https://github.com/jpvoigt/lilypond-export/
This is in an early stage, a proof of concept. I had to put this 
project aside for a while, but it is still on my agenda and hopefully 
it develops further soon.


So if anyone is interested in joining this challenge you may contact 
via the list or private mail.


Jan-Peter


Am 24.03.2018 um 17:47 schrieb Jacques Menu Muzhic:

Hello,
Joe, what do mean exactly by pure data?
Jan-Peter, I’m interested in the MusicXML export from LP, can you 
tell us more?

A nice day!
JM





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

Re: an open question

[Jacques Menu Muzhic]

Hello Jan-Peter,

Thanks for the information. 

Exporting to MusicXML is difficult, also because there are things that need to 
be done in LP with Scheme code since there’s no ‘first class citizen’ to do the 
job.

This leads for example to the use of markup for things such as the swing tempo 
indication:

tempoRelationshipStaffReduce = #-3

tempoRelationship =
#(define-music-function (parser location label parenthesized musicI musicII)
   (string? boolean? ly:music? ly:music?)
   (let* (
   (left-paren (if parenthesized "(" ""))
   (right-paren (if parenthesized ")" ""))
   )
 #{
   \tempo \markup {
 \line \general-align #Y #DOWN {
   % 1st column in line
   $label

   % 2nd column in line

   $left-paren

   \score {
 \new Staff \with {
   % reduce the font size a la cue
   fontSize = #tempoRelationshipStaffReduce
   \override StaffSymbol.staff-space = #(magstep 
tempoRelationshipStaffReduce)
   % hide the staff lines
   \override StaffSymbol.line-count = #0
   % align horizontally
   \override VerticalAxisGroup.Y-extent = #'(-0.85 . 0)
 }

 {
   % \override Score.SpacingSpanner.common-shortest-duration = 
#(ly:make-moment 1/2) % super-tight
   % \override Score.SpacingSpanner.common-shortest-duration = 
#(ly:make-moment 1/4) % tight
   % \override Score.SpacingSpanner.common-shortest-duration = 
#(ly:make-moment 3/16) % even
   \override Score.SpacingSpanner.common-shortest-duration = 
#(ly:make-moment 5/32) % even

   % the left music
   \relative c' { \stemUp $musicI }

   % the equivalence sign
   \once \override Score.TextScript.Y-offset = #-0.4
   s4.^\markup{
 \halign #-1 "="
   }

   % the right music
   \relative c' { \stemUp $musicII }
 }

 \layout {
   indent = 0
   \context {
 \Staff
 \remove "Clef_engraver"
 \remove "Time_signature_engraver"
   }
 } % layout end
   } % score end

   $right-paren

 } % line end
   } % markup end
 #}))


\tempoRelationship #"Swing" ##t
\fixed b' {
  b8 [ b8 ] 
}
\fixed b' {
  \tuplet 3/2 { b4 b8 }
}


while they can be described natively in MusicXML:

 

  Swing


  

  eighth
  begin


  eighth
  end

equals

  quarter
  
3
2
eighth
  


  eighth
  
3
2
eighth
  

  

  

I’m not at ease enough currently with the Scheme/Lilypond interaction to be of 
any help, unfortunately.

JM

> Le 26 mars 2018 à 07:29, Jan-Peter Voigt  a écrit :
> 
> Hello Jacques,
> 
> last year I have been working on an export module for lilypond:
> https://github.com/jpvoigt/lilypond-export/
> This is in an early stage, a proof of concept. I had to put this project 
> aside for a while, but it is still on my agenda and hopefully it develops 
> further soon.
> 
> So if anyone is interested in joining this challenge you may contact via the 
> list or private mail.
> 
> Jan-Peter
> 
> 
> Am 24.03.2018 um 17:47 schrieb Jacques Menu Muzhic:
>> Hello,
>> Joe, what do mean exactly by pure data?
>> Jan-Peter, I’m interested in the MusicXML export from LP, can you tell us 
>> more?
>> A nice day!
>> JM

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