Re: lilyglyphs.sty not found after upgrade to ubuntu 20.04

[bart deruyter]

Thanks for looking into it.

Indeed, I installed it using synaptic.
Browsing in the ubuntu packages on:
https://packages.ubuntu.com/search?suite=focal=any=contents=lilyglyphs.sty
I don't find it either in 'focal', but I do find it in 'eoan'.
https://packages.ubuntu.com/search?suite=eoan=any=contents=lilyglyphs.sty
There I read it should be in the texlive-music package.
Reading the description of 'texlive-music' in synaptic on my current system
(20.04 or focal) lilyglyphs.sty is not mentioned either.

https://esmiltania.be
On Twitter 
On Google+ 


Op do 2 jul. 2020 om 17:13 schreef Urs Liska :

> Am Donnerstag, den 02.07.2020, 17:01 +0200 schrieb Urs Liska:
> > Am Donnerstag, den 02.07.2020, 10:18 +0200 schrieb Urs Liska:
> > > Am 2. Juli 2020 10:00:25 MESZ schrieb bart deruyter <
> > > bart.deruy...@gmail.com>:
> > > > Hi all,
> > > > a bit off topic, but I thought maybe here someone would know
> > > > something.
> > > > I've recently upgraded to ubuntu 20.04 and tried to compile a
> > > > luatex
> > > > file
> > > > containing lilypond material, using lyluatex and lilyglyphs.
> > > >
> > > > Now my system complains about 'lilyglyphs.sty not found'.
> > > > I thought it would have been upgraded too, but it seems like it
> > > > has
> > > > been
> > > > removed from the system and repositories all together. I don't
> > > > find
> > > > anything related to lilyglyphs in the repository.
> > >
> > > Thanks for the report. I don't know anything about it and will
> > > investigate.
> >
> > How did you install LaTeX? I assume you are using TeX Live? The
> > versions from the Ubuntu packages or the downloaded TeX Live?
> >
> > I assume you installed from the Ubuntu packages. If so, which actual
> > packages did you install.
> > https://packages.ubuntu.com/focal/all/texlive-music/filelist
> > indicates
> > lilyglyphs is (still) in the texlive-music collection.
> >
> > Actually I'd be surprised if they had removed it. I'm aware of the
> > possibility of compatibility issues, but I can't imagine they remove
> > packages without warning/asking the maintainers first.
>
> I just had a closer look and found that
> a) lilyglyphs.sty is (now?) placed at tex/lualatex/lilyglyphs
> which is somewhat strange and might xelatex not find it (I'm not sure,
> but if you use lyluatex this can't be the issue anyway.
>
> b)
> I can't find lilyglyphs in the texlive package lists of Ubuntu and
> Debian. I'll ask on the texlive mailing list.
>
> Urs
>
> >
> > BestUrs
> >
> > > Urs
> > >
> > > > thanks,
> > > > Bart
> > > >
> > > > https://esmiltania.be
> > > > On Twitter 
> > > > On Google+ 
> >
> >
>
>

Re: lilyglyphs.sty not found after upgrade to ubuntu 20.04

[Urs Liska]

Am Donnerstag, den 02.07.2020, 17:01 +0200 schrieb Urs Liska:
> Am Donnerstag, den 02.07.2020, 10:18 +0200 schrieb Urs Liska:
> > Am 2. Juli 2020 10:00:25 MESZ schrieb bart deruyter <
> > bart.deruy...@gmail.com>:
> > > Hi all,
> > > a bit off topic, but I thought maybe here someone would know
> > > something.
> > > I've recently upgraded to ubuntu 20.04 and tried to compile a
> > > luatex
> > > file
> > > containing lilypond material, using lyluatex and lilyglyphs.
> > > 
> > > Now my system complains about 'lilyglyphs.sty not found'.
> > > I thought it would have been upgraded too, but it seems like it
> > > has
> > > been
> > > removed from the system and repositories all together. I don't
> > > find
> > > anything related to lilyglyphs in the repository.
> > 
> > Thanks for the report. I don't know anything about it and will
> > investigate.
> 
> How did you install LaTeX? I assume you are using TeX Live? The
> versions from the Ubuntu packages or the downloaded TeX Live?
> 
> I assume you installed from the Ubuntu packages. If so, which actual
> packages did you install.
> https://packages.ubuntu.com/focal/all/texlive-music/filelist
> indicates
> lilyglyphs is (still) in the texlive-music collection.
> 
> Actually I'd be surprised if they had removed it. I'm aware of the
> possibility of compatibility issues, but I can't imagine they remove
> packages without warning/asking the maintainers first.

I just had a closer look and found that
a) lilyglyphs.sty is (now?) placed at tex/lualatex/lilyglyphs
which is somewhat strange and might xelatex not find it (I'm not sure,
but if you use lyluatex this can't be the issue anyway.

b)
I can't find lilyglyphs in the texlive package lists of Ubuntu and
Debian. I'll ask on the texlive mailing list.

Urs

> 
> BestUrs
> 
> > Urs
> > 
> > > thanks,
> > > Bart
> > > 
> > > https://esmiltania.be
> > > On Twitter 
> > > On Google+ 
> 
> 

Re: lilyglyphs.sty not found after upgrade to ubuntu 20.04

[Urs Liska]

Am Donnerstag, den 02.07.2020, 10:18 +0200 schrieb Urs Liska:
> 
> Am 2. Juli 2020 10:00:25 MESZ schrieb bart deruyter <
> bart.deruy...@gmail.com>:
> > Hi all,
> > a bit off topic, but I thought maybe here someone would know
> > something.
> > I've recently upgraded to ubuntu 20.04 and tried to compile a
> > luatex
> > file
> > containing lilypond material, using lyluatex and lilyglyphs.
> > 
> > Now my system complains about 'lilyglyphs.sty not found'.
> > I thought it would have been upgraded too, but it seems like it has
> > been
> > removed from the system and repositories all together. I don't find
> > anything related to lilyglyphs in the repository.
> 
> Thanks for the report. I don't know anything about it and will
> investigate.

How did you install LaTeX? I assume you are using TeX Live? The
versions from the Ubuntu packages or the downloaded TeX Live?

I assume you installed from the Ubuntu packages. If so, which actual
packages did you install.
https://packages.ubuntu.com/focal/all/texlive-music/filelist indicates
lilyglyphs is (still) in the texlive-music collection.

Actually I'd be surprised if they had removed it. I'm aware of the
possibility of compatibility issues, but I can't imagine they remove
packages without warning/asking the maintainers first.

BestUrs

> 
> Urs
> 
> > thanks,
> > Bart
> > 
> > https://esmiltania.be
> > On Twitter 
> > On Google+ 

Re: Circles round fingerings

[Pierre Perol-Schneider]

You're welcome Paul.
Cheers,
Pierre
PS. Be sure to respond to the list.

Le jeu. 2 juil. 2020 à 14:31, Paul McKay  a écrit :

> Thanks for this Pierre. I can now do just what I'd hoped. I'm still
> struggling to write the appropriate markup function, but I'll keep going!
> Paul
>
> On Wed, 24 Jun 2020 at 15:23, Pierre Perol-Schneider <
> pierre.schneider.pa...@gmail.com> wrote:
>
>> Hi Paul,
>> How about:
>>
>> \version "2.20.0"
>>
>> customFingering = {
>>   \override Fingering.font-name = "Arial Black"
>>   \override Fingering.font-size = #-1
>>   \override Fingering.color = #(x11-color "DarkRed")
>> }
>>
>> cust =
>>   -\tweak font-name #"Arial Black"
>>   -\tweak font-size #-2
>>   -\tweak color #(x11-color "DarkRed") \etc
>>
>> tune = \relative {
>> %\customFingering
>> c'4 d-2  e\3 % <= optional
>> \cust-\markup\circle "3"
>> g-5 %-\markup {\center-align \draw-circle #1 #.5 ##f }
>> }
>> \score {
>> <<
>> \time 4/4
>> \new Staff \tune
>> >>
>> \layout {
>>   \context {
>> \Score
>> \override Fingering.font-name = "Arial Black"
>> \override Fingering.font-size = #-1
>> \override Fingering.color = #(x11-color "DarkRed")
>> %Optional:
>> \override StringNumber.font-name = "Arial Black"
>> \override StringNumber.font-size = #-2
>> \override StringNumber.color = #(x11-color "DarkRed")
>>   }
>> }
>> }
>>
>> Of course, you could also define a markup function to get a shortcut for
>> the circled fingering...
>> Cheers,
>> Pierre
>>
>>
>> Le mer. 24 juin 2020 à 15:19, Paul McKay  a écrit :
>>
>>> Hi
>>> I'd like to put a circle round occasional fingering marks. I have tried
>>> *\circle*, but seem to have no control of the resulting thickness nor
>>> of the font features. I can find no way to customize the fingering font
>>> within the *\circle: *I always get some error message or other.
>>>
>>> I tried \draw-circle, but that's a kludge and I can't make it overlap.
>>>
>>> What I'd really like is to set up the fingering font attributes at the
>>> Score level so that I don't have to reset them every time I use fingering
>>> in a music expression. Perhaps that would encourage *\circle* to use
>>> them. In the following example, I'd really like to see a fingering on the e
>>> which has a bold red circle around it and properly centred. It would be
>>> good if it could handle tweaks to the Y-offset too because the circle might
>>> collide with other things.
>>>
>>> Thanks
>>> Paul McKay
>>>
>>> Example:
>>> \version "2.20.0"
>>>
>>> customFingering = {
>>> \override Fingering.font-name = "Arial Black"
>>> \override Fingering.font-size = #-1
>>> \override Fingering.color = #(x11-color "DarkRed")
>>> }
>>> tune = \relative {
>>> \customFingering
>>> c'4 d-2  e -\markup {   { \circle \finger  "3" } }
>>> g-5-\tweak Y-offset 5 -\markup {\center-align \draw-circle #1 #.5
>>> ##f }
>>> }
>>> \score {
>>> <<
>>> \time 4/4
>>> \new Staff \tune
>>> >>
>>> \layout {}
>>> }
>>>
>>

Re: Notes switching Voices

[Urs Liska]

Hi Valentin,

this looks very interesting, and I'll definitely have a closer look
because I currently see the need to finally get my head around defining
new and switching between contexts.

Just one remark: You can remove the keepAliveWhile function and replace
it with a simple

  \new Voice = "bottomA" { #(skip-of-length bass) }

BestUrs

Am Donnerstag, den 02.07.2020, 11:52 +0200 schrieb Valentin Petzel:
> Hello,
> 
> I have recently found a way of having notes change context into a
> different 
> voice. This might be useful when you want to do things like
> condensing three 
> voices into two voices in a piano score. This is basically done by
> adding a 
> Notes-Context to the Voice-Context, which allows us the change the
> voice.
> 
> In the appended file there is a chorale condensed to a piano score
> using this 
> way. Note how in measure 5 the alto voice switches to the tenor
> voice.
> 
> This might matter, because it allows us to differentiate stronger
> what the 
> actual music is versus how it is notated, i.e. we can differentiate
> between 
> lilyponds notated voices and the voices that are actually in the
> music.
> 
> I hope some of you can profit from this, and if you like you can also
> put this 
> on LSR. I’m apparently far to stupid to do this, I cannot even
> properly 
> register a user.
> 
> Regards,
> Valentin

Re: Notes switching Voices

[Valentin Petzel]

Hello Harm,

I managed to do it. Apparently LSR didn’t like the login I entered, maybe it 
was already used or something.

Cheers,
Valentin

Am Donnerstag, 2. Juli 2020, 12:26:24 CEST schrieb Thomas Morley:
> Am Do., 2. Juli 2020 um 11:53 Uhr schrieb Valentin Petzel 
:
> > I hope some of you can profit from this, and if you like you can also put
> > this on LSR. I’m apparently far to stupid to do this, I cannot even
> > properly register a user.
> 
> Hi Valentin,
> 
> could you describe what happens if you try?
> 
> Cheers,
>   Harm

signature.asc
Description: This is a digitally signed message part.

Re: Notes switching Voices

[Thomas Morley]

Am Do., 2. Juli 2020 um 11:53 Uhr schrieb Valentin Petzel :

> I hope some of you can profit from this, and if you like you can also put this
> on LSR. I’m apparently far to stupid to do this, I cannot even properly
> register a user.

Hi Valentin,

could you describe what happens if you try?

Cheers,
  Harm

Re: Unapproved LSR-snippet "Generating scores within a function"

[Thomas Morley]

Am Do., 2. Juli 2020 um 12:16 Uhr schrieb Valentin Petzel :
>
> Hello,
>
> While I cannot help you with this, I noticed that this snippet must have been
> done in an older version of lilypond, thus it uses older music function calls.
> I’ve updated the snippet to 2.20, so now it compiles at least locally.
>
> Regards,
> Valentin

Hi Valentin,

the LSR currently runs 2.18.2.
Upgrading it to 2.20.0 is on TODO.

Thanks,
  Harm

Re: Unapproved LSR-snippet "Generating scores within a function"

[Valentin Petzel]

Hello,

While I cannot help you with this, I noticed that this snippet must have been 
done in an older version of lilypond, thus it uses older music function calls. 
I’ve updated the snippet to 2.20, so now it compiles at least locally.

Regards,
Valentin%% LSR originally contributed by Gilles Thibault:
%% https://lists.gnu.org/archive/html/lilypond-user-fr/2011-11/msg00141.html
%% See also http://lsr.di.unimi.it/LSR/Item?id=630
%% and https://lists.gnu.org/archive/html/lilypond-user/2015-04/msg00311.html

\version "2.20"

duo =
#(define-music-function (nr) (number?)
   (let* ((s (number->string nr))
  (h (make-module))
  (m (ly:make-score
  #{<<
\new Staff { \global \clarI }
\new Staff { \global \clarII }
>>
  #})))
 (module-define! h 'piece (markup #:concat ("Duo n." s)))
 (ly:score-set-header! m h)
 (collect-scores-for-book m)
 (make-music 'Music 'void #t)))

%% Duo 1
global = { \key c \major \time 4/4 }
clarI = { e'1}
clarII = { c'1}
\duo #1

%% Duo 2
global = { \key d \minor \time 3/4 }
clarI = { f'2.}
clarII = { d'2.}
\duo #2

%% Duo 3
global = { \key e \minor \time 2/4 }
clarI = { g'2}
clarII = { e'2}
\duo #3

signature.asc
Description: This is a digitally signed message part.

Notes switching Voices

[Valentin Petzel]

Hello,

I have recently found a way of having notes change context into a different 
voice. This might be useful when you want to do things like condensing three 
voices into two voices in a piano score. This is basically done by adding a 
Notes-Context to the Voice-Context, which allows us the change the voice.

In the appended file there is a chorale condensed to a piano score using this 
way. Note how in measure 5 the alto voice switches to the tenor voice.

This might matter, because it allows us to differentiate stronger what the 
actual music is versus how it is notated, i.e. we can differentiate between 
lilyponds notated voices and the voices that are actually in the music.

I hope some of you can profit from this, and if you like you can also put this 
on LSR. I’m apparently far to stupid to do this, I cannot even properly 
register a user.

Regards,
Valentin\version "2.20.0"

\layout {
  \context {
\Voice
\accepts "Notes"
  }
  \context {
\TabVoice
\accepts "Notes"
  }
  \context {
\name "Notes"
\type "Engraver_group"
  }
}

global = {
  \time 3/4 \key g\major \tempo 4=72
}

vOne = \relative g' {
  \repeat volta #2 {
g4 g d' | b4. a8 g4 |
fis e d | e fis g |  a2. | g
  }
  d'4 d d | e2. | b4 c d | d4. c8 b4 | a2. |
  d,4 e fis | g a b | a2. | g
}

vTwo =  \new Notes \relative d' {
  \repeat volta #2 {
d4 e a | g fis e | d c b |
c c b | 
\tag #'piano { \change Voice = "topA" }
d2.
b
  }
  \tag #'piano { \change Voice = "topB" }
  b'4 a b c2. | g4 g a |
  g g g | fis2. |
  g,4
  \tag #'nonvoice c2
  \tag #'voice {c4 c} |
  b4 fis' g-\tag #'nonvoice ~|
  g2-\tag #'voice ( fis4-\tag #'voice) | g2.
}

vThree = \new Notes \relative b {
  \repeat volta #2 {
b4 b d | d d b |
b g g | g a g |
g2(  fis4) | g2.
  }
  g'4 d g | g2. |
  d4 c fis | d e d | d2. |
  \tag #'piano {
\change Voice = "bottomA"
\voiceOne
  }
  \tag #'nonvoice g,2 \tag #'voice { g4 g }
  a4 | g 
  \tag #'nonvoice {d'2~ } \tag #'voice {d4 d4}
  | 2. | b
}

bass = \relative g {
  \repeat volta #2 {
g4 e fis | g d e | b c g |
c a e' | d2. | g,
  }
  g'4 fis g | c,2. | g'4 e d |
  b c g | d'2. |
  \tag #'piano { \voiceTwo }
  b4 c a | e' d g | d2. | g,
  \bar "|."
}

lyrA = \lyricmode {
  \set stanza = "1."
  Lo -- be den Her -- ren, den mäch -- ti -- gen Kö -- nig der Eh -- ren,
}

lyrB = \lyricmode {
  mei -- ne ge -- lie -- be -- te See -- le, das iſt mein Be -- geh -- ren;
  
  kom -- met zu -- hauf, Pſal -- ter und Har -- fe, wacht auf,
  laſ -- ſet den Lob -- ge -- ſang hö -- ren.
}

keepAliveWhile=#(define-music-function (m) (ly:music?)
  (let* ((mlen (moment->fraction (ly:music-length m
(make-music
  'SkipEvent
  'duration
  (ly:make-duration 0 0 (car mlen) (cdr mlen)


\score {
  \header {
piece = "1. Lobe den Herren, den mächtigen König"
poet  = "Joachim Neander"
  }
  <<
\new ChoirStaff <<
  \new Staff << \new Voice = "psop" {\voiceOne \global \clef "treble" \removeWithTag #'(piano nonvoice) \vOne }
\new Voice {\voiceTwo \global \clef "treble" \removeWithTag #'(piano nonvoice) \vTwo }
  >>
  \new Lyrics \with {\override VerticalAxisGroup.staff-affinity = #CENTER } \lyricsto "psop" \lyrA \new Lyrics \with {\override VerticalAxisGroup.staff-affinity = #CENTER } \lyricsto "psop" \lyrB
  \new Staff << { \global \clef "bass" \removeWithTag #'(piano nonvoice) \vThree } \\
{ \global \clef "bass" \removeWithTag #'(piano nonvoice) \bass }
  >>
>>
\new PianoStaff <<
  \new Staff {
\global
<<
  \new Voice = "topA" {
\voiceOne
\removeWithTag #'(voice) \vOne
  }
  \new Voice = "topB" {
\voiceTwo
<< \removeWithTag #'(voice) \vTwo \removeWithTag #'(voice) \vThree >>
  }
>>
  }
  \new Staff {
\clef "bass" \global
<<
  \new Voice = "bottomA" { \keepAliveWhile \bass }
  \new Voice = "bottomB" {
\removeWithTag #'(voice) \bass
  }
>>
  }
>>
  >>
  \layout { }
}


signature.asc
Description: This is a digitally signed message part.

Re: Harmonics in tablature

[Valentin Petzel]

Hello Wol,

That is more or less a different thing, since you want a different 
notation for that, specifying both the fret of the note and of the 
harmonic. When transcribing some Pastorius I defined a little 
function for that which gives such results:


Regards,
Valentin
\version "2.20"

artificialHarmonicTab =
#(define-music-function (fret1 fret2 music)
(number? number? ly:music?)
#{
  \harmonicByFret #(- fret2 fret1) {
\temporary \override TabNoteHead #'stencil =
#(lambda (grob)
  (grob-interpret-markup grob
  #{
   \markup \lower #0.6 \concat {
 #(number->string fret1)
 \override #'(angularity . 2)
 \parenthesize {
   #(number->string fret2)
   }
   }
  #}))
$music
\revert TabNoteHead #'stencil
  }
#})

\new TabStaff {
  \artificialHarmonicTab 2 6 b\5
}

\new Staff {
  \artificialHarmonicTab 2 6 b\5
}

signature.asc
Description: This is a digitally signed message part.

Re: Harmonics in tablature

[Valentin Petzel]

[FORGOT TO REPLY TO THE LIST]

Hi Lukas,

That is a rather typical problem you get with harmonic in relative mode. 
Basically in relative mode the octave of the pitch is saved relative to the 
previous note. So this means that one would have to transpose the first note in 
base pitch+octave, while you would have to transpose the other notes only in 
basepitch. But please be away that you should not use relative mode for these 
thing anyway, since you will also get the same problem with the next entered 
note: The next note would be relative to the previous harmonic pitch, not the 
entered pitch, which will make scores very confusing to read.

But as I said earlier, the best way to handle this would be at engraver level.

Valentin

Am Dienstag, 30. Juni 2020, 11:32:09 CEST schrieben Sie:
> Hi,
> 
> > In Staceys example, I stumbled across the following strange thing
> > where \relative behaves strangely:
> > 
> > mus = \relative c,, { \harmonicByRatio #1/4 2. }
> > 
> > <<
> >   \new TabStaff
> >   {
> > \set Staff.stringTunings = \stringTuning 
> > \tabFullNotation
> > \mus
> >   }
> >   \new Staff \mus
> 
> Just to make this explicit: \harmonicByRatio and \harmonicByFret both
> fail if used for chords in \relative mode. The reason is the behaviour
> of calc-harmonic-pitch that can be seen in the attached file.
> 
> (calc-harmonic-pitch looks like a direct reimplementation of \transpose
> c' #pitch #mus, but it differs from \transpose in that in actually does
> something - and even "the right thing" - for music inside \relative if
> given only _one_ note.)
> 
> So I agree (if I understood your remark correctly) that \harmonicByFret
> and \harmonicByRatio should rather accept single pitches only.
> 
> But you're obviously also right in that the implementation of harmonics
> handling should be reconsidered because of the different ways they have
> to be handled in a) staves, b) tabstaves, c) midi. Maybe I can try
> something in that direction over the next few days, but I know this is
> going to be pushing my understanding of Lilypond and scheme programming
> to its boundaries :-).
> 
> Lukas

signature.asc
Description: This is a digitally signed message part.

Re: lilyglyphs.sty not found after upgrade to ubuntu 20.04

[Urs Liska]

Am 2. Juli 2020 10:00:25 MESZ schrieb bart deruyter :
>Hi all,
>a bit off topic, but I thought maybe here someone would know something.
>I've recently upgraded to ubuntu 20.04 and tried to compile a luatex
>file
>containing lilypond material, using lyluatex and lilyglyphs.
>
>Now my system complains about 'lilyglyphs.sty not found'.
>I thought it would have been upgraded too, but it seems like it has
>been
>removed from the system and repositories all together. I don't find
>anything related to lilyglyphs in the repository.

Thanks for the report. I don't know anything about it and will investigate.

Urs

>
>thanks,
>Bart
>
>https://esmiltania.be
>On Twitter 
>On Google+ 

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

lilyglyphs.sty not found after upgrade to ubuntu 20.04

[bart deruyter]

Hi all,
a bit off topic, but I thought maybe here someone would know something.
I've recently upgraded to ubuntu 20.04 and tried to compile a luatex file
containing lilypond material, using lyluatex and lilyglyphs.

Now my system complains about 'lilyglyphs.sty not found'.
I thought it would have been upgraded too, but it seems like it has been
removed from the system and repositories all together. I don't find
anything related to lilyglyphs in the repository.

thanks,
Bart

https://esmiltania.be
On Twitter 
On Google+