Re: \partcombine and decrescendo spanner

[Kieren MacMillan]

Hi Michael,

> The bug report is about simultaneous hairpins.

Well, the name states that… but the actual example cited in 
 demonstrates the 
problem with ending a hairpin on a [multimeasure] rest.

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: \partcombine and decrescendo spanner

[David Kastrup]

Kieren MacMillan  writes:

> Hi Michael,
>
>> Nice.
>
> It's Harm's, if I recall correctly…
>
>> What is \etc ?
>
> A rather brilliant addition by David K. (I believe?),

Well, it's a shortcut for certain kinds of music function definitions.
Nothing that would not be available by more explicit means so I wasn't
really sure it was a good idea.  But when it is applicable, it's sort of
tacky.

> which essentially says "now go back to whatever follows in the 'real'
> code stream". See
> .

Well, I'm apparently not the best writer of documentation: when
describing a feature for hiding complexity, I don't manage to confine
the description's complexity in a similar manner.

-- 
David Kastrup

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

\partcombine and decrescendo spanner

[Michael Käppler]

Hi all,

probably I do not see the wood for the trees here: Why are the 
decrescendos unterminated in the following MWE:


\version "2.19.59"

\score {
\new Staff \partcombine { b2.\> r4\! } { des2.\> r4\! }
}

Regards,

Michael


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

Re: \partcombine and decrescendo spanner

[Michael Käppler]

Thank you for pointing this out. Is there a known workaround?

Michael

Am 06.07.2017 um 20:07 schrieb Kieren MacMillan:

Hi Michael,


Why are the decrescendos unterminated in the following MWE

It's a known bug/issue: 

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: \partcombine and decrescendo spanner

[Michael Käppler]

The bug report is about simultaneous hairpins.
But the following example also shows the same problem:

\score {
\new Staff \partcombine { b2.\> r4\! } { des2. r4 }
}

While

\score {
\new Staff \partcombine { b2.\> a4\! } { des2. r4 }
}

does compile without complaints. Seems it has something to do with 
ending a hairpin on a rest.


Regards,
Michael


Am 06.07.2017 um 20:07 schrieb Kieren MacMillan:


Hi Michael,


Why are the decrescendos unterminated in the following MWE

It's a known bug/issue: 

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: \partcombine and decrescendo spanner

[Kieren MacMillan]

Hi Michael,

> Thank you for pointing this out. Is there a known workaround?

\version "2.19.59"

\markup \bold { "BUG:" }
\score {
\new Staff \partcombine { b2.\> r4\! } { des2.\> r4\! }
}

terminateHairpin =
#(define-music-function (ctx-name mus) (string? ly:music?)
#{ << $mus \context Voice = $ctx-name <>\! >> #})

endI = \terminateHairpin "one" \etc
endII = \terminateHairpin "two" \etc

\markup \vspace #4
\markup \bold { "WORKAROUND:" }
\score {
\new Staff \partcombine { b2.\> \endI r4\! } { des2.\> \endII r4\! }
}

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: \partcombine and decrescendo spanner

[Michael Käppler]

Brillant stuff!



Am 06.07.2017 um 20:31 schrieb Kieren MacMillan:

Hi Michael,


Nice.

It's Harm's, if I recall correctly…


What is \etc ?

A rather brilliant addition by David K. (I believe?), which essentially says "now go back 
to whatever follows in the 'real' code stream". See 
.

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: Broken (?) snippets in openlilylib/snippets

[Graham King]

On Thu, 2017-07-06 at 18:17 +0200, Urs Liska wrote:
> Hi all,
> 
> I'm wrapping up a number of things in openLilyLib, and I came across
> snippets where the example files don't compile (with LilyPond 2.19.60).
> Please go through this list and if you feel responsible for the snippet
> please have a look:
> 
> * notation-snippets/blackmensural-notation

This one is just a copy of Lukas Pietch's code from January 2011 that I
was trying to get to work with a recent lilypond.  The files have been
completely superseded by Lukas' more recent work and may safely be
deleted.

Alas, the more recent version doesn't work either (there is a missing
file).  Full details at
https://lists.gnu.org/archive/html/lilypond-user/2016-05/msg00212.html

-- Graham


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

Re: String Number collision

[Marc Hohl]

Hi Harm,

Am 05.07.2017 um 23:21 schrieb Thomas Morley:

Hi Marc,

2017-07-05 8:13 GMT+02:00 Marc Hohl :

Hi list,

I have the following MWE:

[...]

It causes the string number "5" to appear twice, strangely overlapping.
I tried to move the New_fingering_engraver to Staff, but then I got

side-axis not set for grob StringNumber.


Not sure what you expected, I didn't explore the programming error, though.


Well, I hoped that lilypond discardes one of two identical string-number 
events automatically.



I assume that I have to create an engraver similar to the
Merge_rests_engraver that does this job? Or is there another way apart from

\once\hide StringNumber

all the way across the file?




You could do:

#(define (suicide-duplicate-text-grobs grob-lst)
"Walks through the sorted @var{grob-lst}, suiciding grobs with duplicate text"
   (if (null? (cdr grob-lst))
   #f
   (suicide-duplicate-text-grobs
 (if (string=? (ly:grob-property (car grob-lst) 'text)
   (ly:grob-property (cadr grob-lst) 'text))
 (begin
   (ly:grob-suicide! (car grob-lst))
   (cdr grob-lst))
 (cdr grob-lst)

#(define reduce-string-numbers
   (lambda (grob)
"Gets the PaperColumn-grob, filters for StringNumber-grobs, sorts this grobs
with @code{stringlist (ly:grob-object paper-column 'elements
(sorted-strgs
  (sort
strgs
(lambda (p q)
  (string8 ~ e''2. }

down = {  ~ c'2. }

\score {
   <<
   \new Staff
   <<
  \new Voice \with { \deleteDuplicateStrings } { \voiceOne \up }
  \new Voice  { \voiceTwo \down }
   >>
   \new TabStaff
   <<
  \new TabVoice { \voiceOne \up }
  \new TabVoice  { \voiceTwo \down }
   >>
   >>
}


Though, I think an engraver would probably do the job cheaper. (Not tested)


Okay, thanks a lot for your solution! I'll check how it fits in my project.

Regards,

Marc




HTH,
   Harm




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

Broken (?) snippets in openlilylib/snippets

[Urs Liska]

Hi all,

I'm wrapping up a number of things in openLilyLib, and I came across
snippets where the example files don't compile (with LilyPond 2.19.60).
Please go through this list and if you feel responsible for the snippet
please have a look:

* notation-snippets/align-lyrics-on-vowels
  (warning: ignored infinite X-offset)
* notation-snippets/alternating-time-signatures
  (well, that's me, I'll keep it as a reference)
* notation-snippets/blackmensural-notation
* notation-snippets.lyric-syllable-magnetic-snap
* notation-snippets.metric-mod
* notation-snippets.scale-vertical-spacing
* notation-snippets/shaping-bezier-curves/slur-attachments-example.ly

* editorial-tools/git-commands
  (me again)
* input-shorthands/easy-octaves
* specific-solutions/xelatex-markup-list
* templates/predefined-instruments

* notation-snippets.scaling-stencils
  Is this a snippet or an example?

* is input-shorthands/sizeContext still necessary or has this been
included in Lilypond in the meantime?


Maybe this isn't all that has to be done, I also realized that this
repository is very inconsistent in style and quality. However, I want
the snippets repository to become a member of the openLilyLib package
family, which means that - in addition to the existing style of
including the "definitions.ily" files of a directory the stuff can be
loaded as "modules".

Currently this relies on snippets on the "make-modules" branch and
oll-core on the "config" branch, but I intend to merge both in the next
days.

This will result in input code like for example

\include "oll-core/package.ily"
\loadPackage page-layout
\loadPackage \with {
  modules = arrows.frames
}
analysis
\loadModule snippets.notation-snippets.compound-slurs
\loadModules snippets
#'((notation-snippets compound-slurs)
(input-shorthands easy-custom-dynamics))

An overview of this mechanism can be found on
https://github.com/openlilylib/oll-core/wiki

Going through most of the directory structure made me realize that I
would really like to move and rename many modules. For example
"easy-custom-dynamics" should not be accessible through
snippets.input-shorthands.easy-custom-dynamics
but through
snippets.notation.custom-dynamics
Also there are many verbose directory names that should be shortened:
snippets.notation-snippets => snippets.notation etc.

The problem is that such a reorganization and renaming would of course
break lots of existing files ...

Best for now
Urs

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


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

Re: \partcombine and decrescendo spanner

[Michael Käppler]

Nice. What is \etc ?

terminateHairpin =
#(define-music-function (ctx-name mus) (string? ly:music?)
#{ << $mus \context Voice = $ctx-name <>\! >> #})

endI = \terminateHairpin "one" \etc
endII = \terminateHairpin "two" \etc

\markup \vspace #4
\markup \bold { "WORKAROUND:" }
\score {
 \new Staff \partcombine { b2.\> \endI r4\! } { des2.\> \endII r4\! }
}

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: Broken (?) snippets in openlilylib/snippets

[Urs Liska]

One more thing: I realize that there are quite a lot open branches in
the repo (from numerous contributors), which may cause an additional set
of hiccups. So these should be considered as well ...


Am 06.07.2017 um 18:17 schrieb Urs Liska:
> Hi all,
>
> I'm wrapping up a number of things in openLilyLib, and I came across
> snippets where the example files don't compile (with LilyPond 2.19.60).
> Please go through this list and if you feel responsible for the snippet
> please have a look:
>
> * notation-snippets/align-lyrics-on-vowels
>   (warning: ignored infinite X-offset)
> * notation-snippets/alternating-time-signatures
>   (well, that's me, I'll keep it as a reference)
> * notation-snippets/blackmensural-notation
> * notation-snippets.lyric-syllable-magnetic-snap
> * notation-snippets.metric-mod
> * notation-snippets.scale-vertical-spacing
> * notation-snippets/shaping-bezier-curves/slur-attachments-example.ly
>
> * editorial-tools/git-commands
>   (me again)
> * input-shorthands/easy-octaves
> * specific-solutions/xelatex-markup-list
> * templates/predefined-instruments
>
> * notation-snippets.scaling-stencils
>   Is this a snippet or an example?
>
> * is input-shorthands/sizeContext still necessary or has this been
> included in Lilypond in the meantime?
>
>
> Maybe this isn't all that has to be done, I also realized that this
> repository is very inconsistent in style and quality. However, I want
> the snippets repository to become a member of the openLilyLib package
> family, which means that - in addition to the existing style of
> including the "definitions.ily" files of a directory the stuff can be
> loaded as "modules".
>
> Currently this relies on snippets on the "make-modules" branch and
> oll-core on the "config" branch, but I intend to merge both in the next
> days.
>
> This will result in input code like for example
>
> \include "oll-core/package.ily"
> \loadPackage page-layout
> \loadPackage \with {
>   modules = arrows.frames
> }
> analysis
> \loadModule snippets.notation-snippets.compound-slurs
> \loadModules snippets
> #'((notation-snippets compound-slurs)
> (input-shorthands easy-custom-dynamics))
>
> An overview of this mechanism can be found on
> https://github.com/openlilylib/oll-core/wiki
>
> Going through most of the directory structure made me realize that I
> would really like to move and rename many modules. For example
> "easy-custom-dynamics" should not be accessible through
> snippets.input-shorthands.easy-custom-dynamics
> but through
> snippets.notation.custom-dynamics
> Also there are many verbose directory names that should be shortened:
> snippets.notation-snippets => snippets.notation etc.
>
> The problem is that such a reorganization and renaming would of course
> break lots of existing files ...
>
> Best for now
> Urs
>

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


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

Re: \partcombine and decrescendo spanner

[Kieren MacMillan]

Hi Michael,

> Why are the decrescendos unterminated in the following MWE

It's a known bug/issue: 

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: \partcombine and decrescendo spanner

[Kieren MacMillan]

Hi Michael,

> Nice.

It's Harm's, if I recall correctly…

> What is \etc ?

A rather brilliant addition by David K. (I believe?), which essentially says 
"now go back to whatever follows in the 'real' code stream". See 
.

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.94beta - Quick note Lilypond entry using MIDI for Linux

[Vaughan McAlley]

On 29 June 2017 at 21:59, Johan Vromans  wrote:

>
> Since I usually do note input with Denemo, I tried to change the key
> definitions to match Denemo ( 0 = whole, 1 = half, 2 = quart, ...  ).
> I changed the definitions in LQkeyboardEvents.lua but this doesn't seem to
> work. Reading the code in LilyQuick.lua (lines 664 ...) doesn't make clear
> how this is supposed to work.
>
> Can you explain?
>
> Also, it may be a good idea to make the keystrokes match Denemo by default.
>
>
Hi Johan,

I’ve put version 0.941beta up which fixes the issue of custom layouts not
working and adds a Denemo layout option.

https://github.com/palestrina/lily-q

I developed the layout myself using the Finale Speedy Note Entry as a base,
which was:

8 - \breve
7 - 1
6 - 2
5 - 4
4 - 8
3 - 16
2 - 32
1 - 64

I always found the 1 key representing a note I never used a bit annoying,
and also lots of alternating between 8 and 16 required jumping between 4
and 3. So I made a circular sort of layout where adjacent note values are
always next to each other. But the latest patch allows you to do whatever
you like :-)

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